Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam!
Prepare and test your skills
Prepare and test your skills
Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.
Keep the momentum going with these hand-picked practice scenarios
Want more questions like this?
Get a free certification question every week.
Last updated
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?
Establish an official deprecation period with a scheduled shutdown date, deploy an adapter layer to transition dependent services to the new catalog API, export historical records to secure archival storage with retention policies, and decommission the legacy infrastructure.
Immediately shut down and delete the legacy service virtual machines and databases to eliminate critical security exposures, and instruct dependent application owners to point their integrations to Dataplex Universal Catalog.
Rehost the legacy service unchanged into an isolated Virtual Private Cloud (VPC) network, disable agent reporting alerts to avoid noise, and grant direct database read access to dependent services.
Refactor the legacy application code to eliminate technical debt, patch the unsupported agent packages manually in-place, and configure the compute instances to auto-scale to zero during idle periods.
Establish an official deprecation period with a scheduled shutdown date, deploy an adapter layer to transition dependent services to the new catalog API, export historical records to secure archival storage with retention policies, and decommission the legacy infrastructure.
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.
Immediately shut down and delete the legacy service virtual machines and databases to eliminate critical security exposures, and instruct dependent application owners to point their integrations to Dataplex Universal Catalog.
Rehost the legacy service unchanged into an isolated Virtual Private Cloud (VPC) network, disable agent reporting alerts to avoid noise, and grant direct database read access to dependent services.
Refactor the legacy application code to eliminate technical debt, patch the unsupported agent packages manually in-place, and configure the compute instances to auto-scale to zero during idle periods.