Search the practice set
126 questions, 454 terms and 400 topics in 20 areas.
60 results for “Application Portfolio Management”
Application Portfolio Management
Maintaining an inventory of every application with its owner, cost, business value and technical health, and using it to decide what to invest in, replace or retire.
Application Discovery
Establishing what applications exist, what they depend on, who owns them and whether anyone uses them — the step whose absence makes every later step a guess.
Application Performance Monitoring
Instrumentation inside the application that attributes latency and errors to specific code paths, queries and dependencies.
Consent Management
Capturing, storing, honouring and evidencing a data subject's permissions for specific processing purposes, including withdrawal.
Global Traffic Management
The layer that decides which region a given user reaches, using DNS, anycast or an edge network, and that performs regional failover.
Identity and Access Management
The system of record for principals, credentials and permissions, and the policy engine that decides what each principal may do.
Offset Management
How a consumer records its position in a stream, and the decision that determines whether processing is at-least-once or at-most-once.
Secrets Management
Storing, distributing, rotating and auditing credentials so that they never live in code, images or configuration files.
Web Application Firewall
A filter in front of an application that inspects HTTP requests and blocks those matching known attack patterns — useful as a layer, dangerous as a substitute.
Blameless Postmortem
An incident review that seeks the systemic conditions that made a failure possible, explicitly excluding individual fault.
Blue-Green Database Schema
The constraint that makes fast rollback actually work — both application versions must be able to run against one schema at the same time.
Capability Map
A structured view of everything a business does, used as the stable frame for mapping applications, investment, ownership and gaps.
Change Data Capture
Publishing a stream of a database's row-level changes by reading its replication log, without modifying the application that owns it.
Connection Pool
A fixed set of reusable database connections shared by an application's requests, and one of the most common hidden capacity ceilings.
Dynamic Secrets
Credentials generated on demand for a specific consumer with a short lease, rather than stored, shared and rotated periodically.
Envelope Encryption
Encrypting data with a locally-generated data key, then encrypting that key with a master key held in a key management service, and storing the wrapped key alongside the ciphertext.
Field-Level Encryption
Encrypting specific sensitive fields in the application before they reach the datastore, so the store never holds plaintext.
Foreign Key Constraint
A database-enforced rule that a referencing value must exist in the referenced table — referential integrity that no application bug can violate.
Hardware Security Module
A tamper-resistant device that generates and stores keys and performs cryptographic operations without the key material ever being extractable.
Incident Command
Assigning explicit roles during an incident — commander, operations lead, communications lead, scribe — so coordination does not compete with diagnosis.
Key Rotation
Periodically replacing a cryptographic key with a new one while retaining the old for decrypting existing data, so exposure from any single key is bounded.
Kubernetes Operator
A custom controller that encodes operational knowledge for a specific application, reconciling a custom resource towards a desired state the same way built-in controllers do.
Layered Architecture
Organising code into horizontal layers — presentation, application, domain, data — where each layer may only call the one beneath it.
Log-Based CDC
Capturing changes by reading the database's own write-ahead log, which sees every change with no load on the source and no application involvement.
Microservices
An architectural style where an application is a set of independently deployable services, each owning its data and aligned to a business capability.
OAuth 2.0
An authorisation framework that lets an application obtain scoped, delegated access to a resource without handling the user's credentials.
OWASP Top Ten
A periodically updated consensus list of the most critical web application security risks, useful as a design-review checklist.
Operational vs Analytical Store
The separation between the store serving the application's transactions and the one serving reporting and analysis, and the mechanism connecting them.
Permission Boundary
A policy limiting the maximum permissions an identity can have, used so that the ability to create roles does not become the ability to grant unlimited privilege.
Prompt Registry
A versioned store of production prompts with their model bindings, parameters and evaluation results, so a prompt change is a reviewable, traceable, reversible deployment.
Replatform
Migrating an application largely as-is while making targeted changes to exploit the target platform — usually the best return per unit of effort.
Secret Zero
The credential a workload needs in order to authenticate to the secret manager — the one secret that cannot itself be stored in the secret manager.
Service Mesh
An infrastructure layer of sidecar proxies that handles service-to-service networking — mTLS, retries, timeouts, routing, telemetry — outside the application.
Severity Levels
A predefined scale of incident impact that determines who is woken, how fast, and what process applies.
Shopify's Pods and Modular Monolith
Shopify handles Black Friday scale with isolated pods — complete stacks each serving a subset of merchants — while keeping the application itself a deliberately modular monolith.
Design the network layout for a three-tier application in one cloud region. What are the decisions you cannot easily change later?
What the interviewer is testing Whether you know which network decisions are cheap and which are effectively permanent. This is a knowledge question with a clea
One availability zone becomes unavailable. Walk through what happens to a typical three-tier application and what you would have changed.
What survives and what does not Load balancer — regional, survives, and stops routing to targets in the failed zone once health checks fail. Note the detection
An LLM feature that worked last week now gives worse answers. Nothing was deployed. How do you find out what changed, and what should have been in place?
What the interviewer is testing Whether you treat an AI feature as a system with configuration and dependencies, or as a black box that mysteriously drifts. Wha
An estate has database passwords in environment variables across 200 services. Design the migration to a secrets manager.
Sequence it by risk, not by convenience Phase 0 — stop the bleeding. Secret scanning in CI and on the existing repositories, blocking new commits containing cre
Equifax was breached in 2017 through a vulnerability with a patch available two months earlier. Beyond "patch faster", what architectural and governance failures does that imply?
The case, as publicly reported Apache Struts vulnerability CVE 2017 5638 was disclosed in March 2017 with a patch available. An internet facing dispute portal a
Application Portfolio Management
Inventory, ownership, cost and health for every application.
Application Architecture
The application estate as a designed portfolio rather than an accumulation.
AI Cost Management
Token accounting, routing, caching and the context-window budget.
Application Decomposition
Finding seams in a monolith, starting from the data.
Application Performance Monitoring
Attributing latency to code paths, queries and dependencies.
Application Rationalisation
Retire, consolidate, replatform — and why retirement is under-applied.
Identity & Access Management
Workload identity, roles, permission boundaries and usage-based review.
Incident Management
Command roles, severity levels and mitigation before diagnosis.
Key Management
Rotation, separation of duty, envelope encryption and crypto-shredding.
LLM Application Architecture
The shape of a production system with a model in the request path.
Log Management
Aggregation, retention tiering, search and the cost of keeping everything.
Portfolio Prioritisation
Choosing between investments with incomparable benefits.
Prompt & Version Management
Prompts as reviewed, versioned, evaluated production configuration.
Secrets Management
Runtime injection, dynamic credentials and rotation applications survive.
Cloud Migration
Per-application disposition, sequencing and the capability change underneath.
EA Domains
Business, application, data and technology architecture as viewpoints.
Encryption
At rest, in transit, and at the application layer — three different threats.
Enterprise Architecture
General material on architecture at portfolio and estate scale.
Multi-Cloud
Best-of-breed, portfolio and portable — three very different costs.