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 online retail enterprise is evaluating whether to modernize its on-premises monolithic checkout application to a multi-region deployment on Google Cloud. Executive leadership requires a data-driven decision framework that balances business risks, infrastructure costs, and technical performance before approving the migration budget.
The application experiences severe performance bottlenecks and occasional downtime during seasonal sales events, directly resulting in lost revenue and degraded customer satisfaction.
Which strategy should the Cloud Architect recommend to assess the risks and justify the architectural investment?
This option establishes an inflexible policy of zero downtime (100% availability) across every system component and overprovisions multi-region redundant resources regardless of cost.
A catastrophic system failure carried irreversible life-critical safety implications where financial optimization is legally irrelevant.
Error budgets provide a deliberate safety margin that allows teams to balance stability with rapid innovation, preventing excessive operational spending on unnecessary overprovisioning.
This option relies solely on a basic infrastructure-level pricing calculation using tools like the Google Cloud Pricing Calculator to pick the configuration with the lowest immediate upfront cost.
The workload were an internal, non-critical batch processing task with no availability requirements and zero financial impact during downtime.
A comprehensive architectural evaluation must look beyond component list prices and incorporate holistic Total Cost of Ownership (TCO) and risk tolerance into infrastructure decisions.
This option immediately splits the production workload across multiple cloud service providers in an active-active multicloud configuration to prevent vendor lock-in and avoid single-provider outages.
Strict national data sovereignty regulations or explicit contractual requirements legally mandated hosting copies of data across independent providers.
Multicloud architectures should never be implemented as a default solution for reliability without conducting a rigorous cost-benefit and capability parity assessment.
This approach uses a structured, data-driven evaluation methodology that combines quantitative reliability metrics (Service Level Indicators and Service Level Objectives), financial analysis (Total Cost of Ownership and unit costing), and iterative technical validation through a Proof of Concept (POC).
Balancing architectural investments requires analyzing both the cost of resilience and the business cost of failure. Defining explicit SLOs and conducting a POC enables leadership to objectively determine if multi-region redundancy delivers positive ROI compared to simpler deployment topologies.
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 Validated