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 e-commerce retailer is migrating its core digital storefront and checkout application to Google Cloud. Executive leadership wants to establish an observability and performance measurement framework that directly bridges technical infrastructure metrics with business outcomes, such as transaction completion rates, user engagement, and revenue protection.
Which strategy should the cloud architect implement to align technical key performance indicators (KPIs) with organizational business goals?
This option focuses monitoring exclusively on lower-level infrastructure consumption metrics across Compute Engine virtual machines, tracking baseline resource utilization such as CPU percentage, memory usage, and disk I/O operations.
While tracking resource utilization is a standard operational practice, infrastructure metrics alone fail to bridge technical performance with business outcomes. An application can show low CPU and memory utilization while still failing user transactions due to application bugs, third-party payment gateway timeouts, or misconfigured database connections. Relying solely on infrastructure health indicators leaves leadership blind to actual user engagement, transaction throughput, and checkout completion rates.
The primary requirement were simply right-sizing virtual machine instances or configuring infrastructure auto-scaling triggers based on compute resource thresholds.
Infrastructure metrics are necessary operational inputs, but they should complement, rather than substitute for, application-level SLIs/SLOs and business KPIs.
This option relies on running synthetic stress and load testing directly in the live production environment during peak business hours to push the infrastructure to its functional limits and observe system breakpoints.
Continuous, uncontrolled stress testing during peak traffic hours introduces severe operational risk and can degrade or crash production services for actual paying customers. Furthermore, stress testing measures maximum theoretical breaking capacity rather than providing a continuous observability baseline of actual user transactions, business KPIs, and live system availability.
The team were conducting pre-launch operational readiness and capacity planning in a dedicated staging environment or during scheduled maintenance windows to identify infrastructure scale limits.
Performance and load testing should be scheduled in non-production environments or during controlled testing windows to validate architecture scalability, alongside continuous passive observability of live user traffic.
Defining Service Level Indicators (SLIs) and Service Level Objectives (SLOs) tied to critical user journeys establishes a measurable, standardized framework within Google Cloud Observability to quantify performance against agreed-upon business and user experience standards. By formulating these targets using the SMART criteria (Specific, Measurable, Achievable, Relevant, and Time-bound), organizations ensure that engineering targets directly reflect business priorities.
This approach aligns with Google Cloud architecture best practices by elevating raw infrastructure telemetry into meaningful business KPIs. It provides continuous visibility into application health, user satisfaction, and business transaction throughput.
This approach uses Cloud Billing data exported to BigQuery to analyze month-end financial costs and resource expenditures, using financial spend trends as the primary proxy for system efficiency and customer satisfaction.
Billing reports are retrospective financial tools that provide zero real-time visibility into technical performance, system availability, latency, or transaction throughput. A drop in monthly cloud spend might indicate improved architectural efficiency, or it could signify an unnoticed service outage that drove customers away. Financial reporting cannot provide the granular, real-time indicators needed to safeguard business goals and maintain high-performing user experiences.
The objective were focused on cloud financial governance, chargeback accounting, or FinOps cost optimization across departmental billing accounts.
Cost optimization and ROI calculations are vital components of cloud architecture, but they must be paired with real-time technical telemetry to ensure cost reductions do not compromise service performance or reliability.
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