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 organization is architecting a globally distributed e-commerce API backend on Google Cloud. To ensure a resilient, low-latency user experience during high-traffic events, the architecture team must define non-functional requirements for performance and availability.
The requirements are as follows:
Which approach should the cloud architect implement to establish these requirements and thresholds?
This option tracks the raw number of concurrent client connections over time windows, defines a fixed 365-day compliance measurement window, and sizes infrastructure backend capacity to run at 100% utilization during peak load.
The goal was to monitor long-term socket exhaustion on stateful gateway proxy servers rather than validating low-latency API response performance.
This option measures network reachability at Layer 3 using ICMP ping response times between internal compute nodes, tracks storage subsystem disk I/O via Cloud Monitoring, and uses project quota limits to dictate scaling behavior.
The scenario required monitoring private network link connectivity and underlying block storage saturation across internal data center interconnects.
This solution establishes a formal Site Reliability Engineering (SRE) framework using Service Level Indicators (SLIs), Service Level Objectives (SLOs), and error budgets implemented via Google Cloud Observability and structured capacity planning.

100% - SLO Goal) to govern deployment freezes and architectural remediation.This approach directly targets the non-functional performance requirements by coupling quantifiable quality attributes (latency and availability) with empirical threshold testing, ensuring global system resilience without over-provisioning infrastructure.
This option attempts to enforce a contractual Service Level Agreement (SLA) of 100% availability while relying on host-level hardware utilization metrics (such as CPU consumption) in Cloud Logging and destructive stress testing to identify system failure limits.
The objective was to establish legal compensation terms for external enterprise clients and determine the absolute hardware failure boundaries of unmanaged virtual machine instances.
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