Professional Cloud Architect Practice Test

What this test covers

One concept per question, across the topics Professional Cloud Architect draws on.

• The four golden signals describe service health from the user's perspective
• Cache keys determine what counts as the same request
• Commit to the baseline, absorb variability with flexible capacity
• IAM is additive and inherits downward; lower levels cannot subtract an inherited grant
• Pass-through load balancing preserves the client source address and supports UDP
• Billing accounts control invoicing; the resource hierarchy and labels provide cost attribution
• Sole tenancy provides dedicated physical hardware for licensing and compliance
• Organisation policy is a preventative control that binds even project administrators
• Autopilot removes node management in exchange for reduced configurability
• Edge caching reduces both origin load and egress cost simultaneously
• Zones are independent failure domains within a region
• Workload identity federation eliminates long-lived service account keys
• Global HTTP(S) traffic with one anycast address means the global Application Load Balancer
• Shared VPC centralises network control while devolving resource management
• Separation of duties prevents a single identity holding conflicting powers
• Data access logs record reads and must be enabled deliberately
• Spot capacity suits fault-tolerant, interruptible work
• Local SSD trades durability for maximum performance
• Shared read-write access with file semantics requires network file storage
• Spanner is the option combining horizontal scale with strong global consistency
• Bigtable targets very high throughput key lookups over very large datasets
• Partitioning is what actually reduces bytes scanned in BigQuery
• Data residency needs both correct placement and a preventative guardrail
• A locked retention policy is immutable and binds even administrators
• VPC peering is non-transitive by design
• Scale to zero suits spiky traffic with a small operations team
• Kubernetes provides a consistent deployment target across environments
• Cloud NAT provides outbound-only internet access for instances without public addresses
• Minimum storage duration makes cold classes expensive for short-lived data
• Alert on symptoms users experience, not on causes that may be harmless
• Match storage class to actual access frequency, not to a general sense of importance
• Authorised views let someone query derived results without access to the source
• Controlling the key is what enables cryptographic revocation of access
• RPO is data loss tolerance; RTO is downtime tolerance
• Organisation policy provides preventative guardrails that inherit down the hierarchy
• Workload Identity removes long-lived credentials from the cluster
• Streaming ingestion through a message queue is the standard near-real-time analytics path