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: The legacy service runs on unmaintained agent software that has passed its planned decommission date and no longer receives security bug fixes. Business value has steadily declined as most analytics teams have migrated to Dataplex Universal Catalog, though a few downstream reporting services still depend on the legacy API. Regulatory compliance policies require that all historical metadata audit records generated by the legacy system be preserved and protected for seven years. 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.: ### What a structured workload deprecation and retirement strategy is 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. ### How it meets the requirements - **Technical Debt and Security Risks:** Formally scheduling the decommission of the legacy catalog eliminates the security vulnerabilities inherent in unmaintained, end-of-life agents and removes ongoing maintenance overhead. - **Seamless Service Transition:** Deploying a compatibility or adapter layer allows dependent downstream reporting services to redirect their queries to modern services (such as Dataplex Universal Catalog) without breaking existing workflows or requiring abrupt code refactoring. - **Regulatory Data Archival:** Exporting historical audit records to cold, durable cloud storage configured with **Bucket Lock** and retention rules satisfies 7-year regulatory compliance requirements while significantly reducing storage costs. ### Key advantages and capabilities - **Predictable Milestones:** Providing a defined deprecation window and shutdown date allows dependent teams sufficient lead time to test and adapt their systems. - **Zero Service Disruption:** Decouples the retirement of backend infrastructure from client dependencies via transitional proxy or translation interfaces. - **Cost Optimization:** Completely removes compute and management overhead for end-of-life workloads once decommissioning is finalized. - **Guaranteed Compliance:** Ensures data immutability and long-term retention off the primary compute tier. ### Why this is optimal 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.

StudyCerts

Legacy Workload Deprecation Data Archival Transition | 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! | StudyCerts

Professional Cloud Architect

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!

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Intermediate

Prepare and test your skills

Track Readiness

Set Exam Goal

Legacy Workload Deprecation Data Archival Transition

Section: Workload disposition strategies (e.g., build, buy, modify, or deprecate)

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.

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:

The legacy service runs on unmaintained agent software that has passed its planned decommission date and no longer receives security bug fixes.
Business value has steadily declined as most analytics teams have migrated to Dataplex Universal Catalog, though a few downstream reporting services still depend on the legacy API.
Regulatory compliance policies require that all historical metadata audit records generated by the legacy system be preserved and protected for seven years.

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.

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.

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.

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.

Professional Cloud Architect

Legacy Workload Deprecation Data Archival Transition

Related questions