Search the practice set
126 questions, 454 terms and 400 topics in 20 areas.
38 results for “Application Rationalisation”
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.
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.
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.
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.
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.
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.
Replatform
Migrating an application largely as-is while making targeted changes to exploit the target platform — usually the best return per unit of effort.
Service Mesh
An infrastructure layer of sidecar proxies that handles service-to-service networking — mTLS, retries, timeouts, routing, telemetry — outside the application.
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.
Sidecar
Deploying a helper process alongside the main application in the same unit, to supply cross-cutting behaviour without changing the application.
Six Rs of Migration
The standard menu of options for each application in a migration — rehost, replatform, refactor, repurchase, retire, retain.
TCP/IP
The layered protocol suite underneath essentially all application traffic — IP routes packets, TCP turns them into a reliable ordered stream.
TOGAF
An enterprise architecture framework whose central element is the ADM, an iterative cycle from vision through business, data, application and technology architecture to implementa…
Tool Calling
Giving a model a set of typed function definitions it can request to invoke, with the application executing the call and returning the result.
Warm Pool
Pre-initialised instances held in a stopped or standby state so that scaling out skips boot and application warm-up.
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
You inherit an estate of roughly 400 applications, no reliable inventory, and a mandate to reduce cost and risk. What do you do in the first ninety days?
What the interviewer is testing Whether you can sequence work at portfolio scale, and whether you go for evidence before strategy. This is the enterprise archit
Application Rationalisation
Retire, consolidate, replatform — and why retirement is under-applied.
Application Architecture
The application estate as a designed portfolio rather than an accumulation.
Application Decomposition
Finding seams in a monolith, starting from the data.
Application Performance Monitoring
Attributing latency to code paths, queries and dependencies.
Application Portfolio Management
Inventory, ownership, cost and health for every application.
LLM Application Architecture
The shape of a production system with a model in the request path.
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.
The Six Rs
Rehost, replatform, refactor, repurchase, retire, retain — per application.