Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
An enterprise is reviewing its cloud footprint to optimize infrastructure costs and reduce technical debt. During the review, the architecture team evaluates a legacy metadata catalog service and identifies several concerns:
You need to define a workload disposition strategy to deprecate and retire this legacy service while ensuring service continuity and regulatory compliance.
Which strategy should you implement?
In-place refactoring involves investing engineering effort into modifying the legacy codebase, attempting to maintain unpatched or custom agent forks, and applying cloud-native scaling configurations (like scaling to zero) to lower compute costs while keeping the workload active.
The legacy catalog provided unique, irreplaceable business logic that could not be satisfied by modern platforms and had critical, high-volume operational demand.
A workload deprecation strategy is a formal architectural lifecycle process for identifying, phasing out, and safely decommissioning software components, services, or infrastructure that have declining business value, high technical debt, or unmanageable security risks. It establishes clear milestones—including an announcement date, transition period, and final shutdown date—to ensure orderly migration and data preservation.

This approach directly mirrors standard enterprise cloud lifecycle policies. Rather than leaving high-risk, unpatched systems running or abruptly breaking downstream workloads, it pairs proactive transition management with compliant, cost-effective data archival.
Immediate shutdown is an abrupt termination pattern where legacy virtual machines, containers, and database instances are stopped and deleted immediately without a formal deprecation period or transitional grace window.
The system were confirmed to have zero external dependencies, held no regulated data requiring archival, and posed an active, zero-day threat requiring emergency isolation.
This approach uses a lift-and-shift pattern into an isolated VPC network, suppresses monitoring alerts generated by deprecated agents, and exposes the underlying database schema directly to external client microservices.
The goal was temporary disaster recovery isolation during an active incident while keeping core legacy database queries functional for a short triage window.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated