Google Cloud Professional Cloud Architect - Fact Sheet¶
Quick Reference¶
Exam Code: Professional Cloud Architect Duration: 120 minutes (2 hours) Questions: 50-60 questions Passing Score: ~70% (not officially published) Cost: $200 USD Validity: 2 years Difficulty: βββββ (Most challenging GCP certification) Prerequisites: Recommended 3+ years of industry experience, including 1+ year designing GCP solutions
Exam Domains¶
| Domain | Weight | Key Focus |
|---|---|---|
| Designing and planning a cloud solution architecture | 24% | Business requirements, application design, infrastructure design |
| Managing and provisioning solution infrastructure | 15% | Network topology, storage, compute resources |
| Designing for security and compliance | 18% | Identity and access, data protection, separation of duties |
| Analyzing and optimizing technical and business processes | 17% | Technical analysis, business analysis, procedures |
| Managing implementation | 10% | Advising development teams, managing changes |
| Ensuring solution and operations reliability | 16% | Monitoring, logging, incident response, supporting product launches |
Core Architecture Principles¶
Well-Architected Framework¶
π Google Cloud Architecture Framework - Complete architecture framework
Five Pillars: 1. Operational Excellence - Efficient operations and monitoring 2. Security, Privacy, and Compliance - Protection and governance 3. Reliability - Availability and fault tolerance 4. Cost Optimization - Resource efficiency and financial governance 5. Performance Optimization - Efficient resource use and scaling
Key Resources: - π Architecture Center - Reference architectures and diagrams - π Best Practices - Enterprise design patterns - π Cloud Architecture Patterns - System design patterns - π Decision Trees - Architecture decision guides
Compute Services - Architecture Deep Dive¶
Compute Engine¶
Strategic Use Cases: - Legacy application migrations (lift-and-shift) - Custom operating systems or kernels - GPU/TPU workloads requiring specific configurations - Per-second billing with sustained use discounts - π Compute Engine Overview - Architecture guide - π Machine Families - Choosing the right machine type - π Instance Templates - Configuration management - π Managed Instance Groups - Auto-scaling and load balancing - π Sole-Tenant Nodes - Dedicated hardware for compliance
Advanced Features: - Custom Machine Types - Precise resource allocation - Preemptible VMs - Up to 80% cost savings for fault-tolerant workloads - Spot VMs - More flexible than preemptible with longer runtime - Committed Use Discounts - 1 or 3 year commitments for 57% savings - Shielded VMs - Secure boot, vTPM, integrity monitoring - π Live Migration - Zero-downtime maintenance - π Persistent Disk Performance - Storage optimization
Google Kubernetes Engine (GKE)¶
Enterprise Architecture: - Autopilot - Fully managed, pay-per-pod, optimal configurations - Standard - Node-level control, custom configurations - GKE Enterprise - Multi-cluster management with Anthos - π GKE Architecture - Complete overview - π Cluster Architecture - Control plane and nodes - π Multi-Cluster Ingress - Global load balancing - π Binary Authorization - Deploy-time security controls - π GKE Networking - VPC-native clusters
Advanced Patterns: - Workload Identity - Pod-to-GCP service authentication without keys - Config Connector - Manage GCP resources via Kubernetes - Node Auto-Provisioning - Automatic node pool creation - Vertical Pod Autoscaling - Right-size container resources - Multi-cluster Services - Service discovery across clusters - π GKE Best Practices - Production guidelines - π Security Hardening - Security best practices
Cloud Run¶
Serverless Container Architecture: - Fully managed compute platform for containers - Scales to zero, pay only for actual usage - Auto-scales based on concurrent requests - π Cloud Run Documentation - Complete guide - π Service Identity - IAM integration - π VPC Connectivity - Direct VPC egress - π Cloud Run Jobs - Batch workloads
Architecture Decisions: - vs App Engine - More flexibility, custom containers - vs GKE - Simpler operations, less control - vs Cloud Functions - Longer execution time, more memory
App Engine¶
Platform as a Service: - Standard Environment - Rapid scaling, sandbox runtime, free tier - Flexible Environment - Docker containers, SSH access, custom runtimes - π App Engine Architecture - Environment comparison - π Scaling Types - Automatic, basic, manual scaling - π Traffic Splitting - A/B testing and canary - π Migration to Standard 2nd Gen - Modern runtimes
Cloud Functions¶
Event-Driven Serverless: - 2nd Generation - Built on Cloud Run, better performance, longer execution - Event sources: Cloud Storage, Pub/Sub, HTTP, Firestore, Firebase - π Cloud Functions Architecture - Concepts and patterns - π Eventarc Integration - Unified eventing - π Security Best Practices - Function security
Storage Architecture¶
Cloud Storage¶
Global Object Storage: - Storage Classes Decision Matrix: - Standard - Hot data, frequent access - Nearline - < 1/month access, 30-day minimum - Coldline - < 1/quarter access, 90-day minimum - Archive - < 1/year access, 365-day minimum - π Storage Classes - Detailed comparison - π Object Lifecycle Management - Automated tiering - π Bucket Locations - Regional, dual-region, multi-region - π Object Versioning - Version control - π Retention Policies - Compliance and data governance - π Customer-Managed Encryption Keys - CMEK integration
Advanced Features: - Requester Pays - Transfer costs to downloader - Object Holds - Legal and temporary holds - Dual-region - 99.95% SLA with geo-redundancy - Turbo Replication - < 15 minute RPO between regions - π Performance Optimization - Request rate best practices
Persistent Disks and Filestore¶
Block and File Storage: - Persistent Disk Types: - Standard (pd-standard) - HDD, sequential workloads - Balanced (pd-balanced) - SSD, balanced price/performance - SSD (pd-ssd) - High-performance SSD - Extreme (pd-extreme) - Highest performance, configurable IOPS - π Disk Types Comparison - Performance and pricing - π Regional Persistent Disks - Synchronous replication - π Disk Snapshots - Incremental backups - π Filestore - Managed NFS file server - π Filestore Instances - Basic, High Scale, Enterprise tiers
Database Architecture¶
Cloud SQL¶
Managed Relational Databases: - Supports MySQL, PostgreSQL, SQL Server - High Availability Configuration: - Regional HA with synchronous replication - Automatic failover (typically 60-120 seconds) - Read replicas for read scaling - π Cloud SQL Overview - Architecture guide - π High Availability - HA architecture - π Replication - Read replicas and cross-region - π Backup and Recovery - Backup strategies - π Connection Options - Cloud SQL Proxy, Private IP
Cloud Spanner¶
Globally Distributed Relational Database: - Horizontally scalable, strongly consistent - Global transactions with 99.999% availability SLA - Multi-region configurations for HA and low latency - π Cloud Spanner Overview - Architecture concepts - π Replication - Multi-region replication - π Schema Design Best Practices - Performance optimization - π Instance Configurations - Regional and multi-regional - π Choosing Between Cloud SQL and Spanner - Decision guide
Firestore and Datastore¶
NoSQL Document Databases: - Firestore - Next-generation, real-time synchronization - Datastore Mode - Server-side applications - Automatic multi-region replication - Strong consistency for entity group queries - π Firestore Overview - Complete guide - π Choosing Between Firestore Modes - Native vs Datastore mode - π Data Modeling - Document structure - π Best Practices - Performance and cost optimization
Bigtable¶
Wide-Column NoSQL: - Petabyte-scale, sub-10ms latency - Ideal for time-series, IoT, financial services - HBase API compatible - π Bigtable Overview - Architecture and use cases - π Schema Design - Row key design critical - π Replication - Multi-cluster replication - π Performance Tuning - Optimization guide - π Choosing Between Bigtable and Other Databases - Decision tree
BigQuery¶
Serverless Data Warehouse: - Petabyte-scale analytics with standard SQL - Separation of compute and storage - Automatic optimization and indexing - π BigQuery Architecture - Complete guide - π Partitioning and Clustering - Query optimization - π BigQuery BI Engine - In-memory analytics - π BigQuery ML - Machine learning in SQL - π Cost Optimization - Query cost management - π Data Transfer Service - Scheduled data imports
Memorystore¶
Managed In-Memory Data Store: - Memorystore for Redis - Advanced features, persistence - Memorystore for Memcached - Simple caching - π Memorystore for Redis - Redis architecture - π High Availability - Standard vs basic tier
Networking Architecture¶
Virtual Private Cloud (VPC)¶
Network Foundation: - Global resource spanning all regions - Subnets are regional (not zonal) - No inter-region bandwidth charges within VPC - π VPC Overview - Fundamental concepts - π VPC Network Design - Best practices - π Subnet Configuration - IP addressing - π Firewall Rules - Traffic control - π Routes - Routing configuration - π Alias IP Ranges - Container and service IPs
Advanced VPC Patterns: - Shared VPC - Cross-project networking - VPC Peering - Private connectivity between VPCs - VPC Service Controls - Security perimeters - Private Google Access - Access Google APIs privately - Private Service Connect - Private access to managed services - π Shared VPC - Multi-project architecture - π VPC Peering - VPC interconnection - π VPC Service Controls - Security perimeter - π Private Google Access - API access without internet - π Private Service Connect - Private service access
Cloud Load Balancing¶
Global Load Balancing: - Single anycast IP serving globally - Automatic multi-region failover - Layer 4 (TCP/UDP) and Layer 7 (HTTP/S) options - π Load Balancing Overview - Architecture guide - π Choosing a Load Balancer - Decision tree - π External HTTP(S) Load Balancer - Global Layer 7 - π Internal HTTP(S) Load Balancer - Regional Layer 7 - π Network Load Balancer - Regional Layer 4 - π SSL Policies - TLS configuration - π Cloud Armor - DDoS protection and WAF
Cloud CDN¶
Content Delivery Network: - Global edge network with Google's infrastructure - Cache-to-cache filling reduces origin load - Integration with Cloud Load Balancing - π Cloud CDN Overview - Architecture - π Caching Best Practices - Performance optimization - π Cache Keys and Modes - Cache control - π Signed URLs and Cookies - Content access control
Hybrid Connectivity¶
Connecting to Google Cloud: - Cloud VPN - IPsec, up to 3 Gbps per tunnel with HA VPN - Cloud Interconnect - Dedicated physical connections - Dedicated - 10 or 100 Gbps direct connection - Partner - 50 Mbps to 50 Gbps via partner - π Hybrid Connectivity Overview - Options comparison - π Cloud VPN - VPN architecture - π HA VPN - High availability VPN - π Cloud Interconnect - Dedicated connectivity - π Partner Interconnect - Service provider connectivity - π Cloud Router - Dynamic BGP routing
Network Intelligence Center: - π Network Topology - Visualization - π Connectivity Tests - Troubleshooting - π Performance Dashboard - Monitoring
Security and Identity¶
Identity and Access Management (IAM)¶
Principle of Least Privilege: - Who - Google Account, Service Account, Google Group, Cloud Identity domain - What - Resources (projects, folders, organization) - How - Roles (primitive, predefined, custom) - π IAM Overview - Core concepts - π IAM Roles - Role types and hierarchy - π Custom Roles - Role creation - π IAM Conditions - Conditional access - π IAM Best Practices - Security guidelines - π Policy Intelligence - Policy analysis tools
Service Accounts¶
Application Identity: - Default compute service account (not recommended for production) - User-managed service accounts (recommended) - Short-lived credentials via Workload Identity Federation - π Service Accounts - Complete guide - π Best Practices - Security patterns - π Workload Identity - External identity federation - π Service Account Impersonation - Delegation patterns
Encryption¶
Data Protection: - Encryption at rest - Default with Google-managed keys - Customer-Managed Encryption Keys (CMEK) - Cloud KMS integration - Customer-Supplied Encryption Keys (CSEK) - Customer-provided keys - π Encryption at Rest - Default encryption - π Cloud KMS - Key management service - π CMEK - Customer-managed keys - π Cloud HSM - Hardware security modules - π Secret Manager - Secrets storage
Security Command Center¶
Centralized Security Management: - Asset discovery and inventory - Vulnerability scanning - Threat detection - Compliance monitoring - π Security Command Center - Overview - π Asset Discovery - Inventory management - π Finding Types - Security findings
Identity-Aware Proxy (IAP)¶
Application-Level Access Control: - Zero-trust access to applications - No VPN required - Context-aware access controls - π Identity-Aware Proxy - Architecture guide - π IAP TCP Forwarding - SSH/RDP access
Operations and Observability¶
Cloud Monitoring (Operations Suite)¶
Monitoring and Alerting: - Infrastructure and application metrics - Custom metrics from applications - Uptime checks and alerting - π Cloud Monitoring - Complete guide - π Metrics - Available metrics - π Alerting - Alert policies - π Dashboards - Visualization - π Uptime Checks - Availability monitoring
Cloud Logging (Operations Suite)¶
Centralized Log Management: - All GCP service logs automatically collected - Log sinks to BigQuery, Cloud Storage, Pub/Sub - Log-based metrics for custom monitoring - π Cloud Logging - Architecture overview - π Logs Router - Log routing - π Log Sinks - Export destinations - π Logs Explorer - Query interface - π Audit Logs - Compliance logging
Cloud Trace and Profiler¶
Application Performance: - Cloud Trace - Distributed tracing for latency analysis - Cloud Profiler - Continuous CPU and memory profiling - Cloud Debugger - Production debugging without stopping - π Cloud Trace - Latency tracking - π Cloud Profiler - Performance profiling - π Error Reporting - Error aggregation
Migration Strategies¶
Migration Framework (5 Rs)¶
Migration Patterns: 1. Rehost - Lift-and-shift to Compute Engine 2. Replatform - Minor optimizations (e.g., Cloud SQL instead of self-managed) 3. Refactor - Re-architect for cloud-native (serverless, microservices) 4. Retire - Decommission unnecessary systems 5. Retain - Keep on-premises temporarily
Migration Tools: - Migrate for Compute Engine - VM migration from on-prem or other clouds - Database Migration Service - Continuous replication for minimal downtime - Transfer Appliance - Physical data transfer for large datasets - Storage Transfer Service - Online data transfer - π Migration to Google Cloud - Migration framework - π Migrate for Compute Engine - VM migration - π Database Migration Service - Database migration - π Transfer Appliance - Offline data transfer - π Storage Transfer Service - Online data transfer
Cost Optimization¶
Compute Cost Optimization¶
Cost-Effective Compute: - Committed Use Discounts - 1 or 3 year, up to 57% savings - Sustained Use Discounts - Automatic discounts for running instances - Preemptible VMs - Up to 80% savings, 24-hour max - Spot VMs - More flexible preemptible alternative - Custom Machine Types - Right-size CPU and memory - π Pricing Overview - GCP pricing model - π Committed Use Discounts - Long-term commitments - π Resource-Based Pricing - Per-second billing - π Pricing Calculator - Cost estimation
Storage Cost Optimization¶
Storage Classes and Lifecycle: - Autoclass for Cloud Storage buckets - Object lifecycle management - Nearline/Coldline/Archive for infrequent access - Regional vs multi-region trade-offs - π Storage Cost Optimization - Best practices
Cost Management Tools¶
Visibility and Control: - Cost Management - Budgets, alerts, reports - Recommender - AI-powered cost and performance recommendations - Active Assist - Proactive optimization recommendations - π Cost Management - Cost visibility - π Billing Reports - Cost analysis - π Budgets and Alerts - Cost controls - π Recommender - Optimization recommendations
High Availability and Disaster Recovery¶
Availability Patterns¶
Multi-Zonal and Multi-Regional: - Zonal Resources - Compute Engine instances, persistent disks - Regional Resources - Cloud SQL, regional MIGs, subnets - Multi-Regional Resources - Cloud Storage, Spanner - Global Resources - VPC networks, load balancers, Cloud CDN
Disaster Recovery Strategies¶
RTO and RPO Trade-offs:
| Strategy | RTO | RPO | Cost | Use Case |
|---|---|---|---|---|
| Backup & Restore | Hours | Hours | $ | Dev/test, non-critical |
| Pilot Light | 10s of minutes | Minutes | $$ | Lower-tier production |
| Warm Standby | Minutes | Seconds | $$$ | Business-critical |
| Active-Active Multi-Region | Seconds | Near-zero | $$$$ | Mission-critical |
DR Best Practices: - Regular backup testing and validation - Automated failover procedures - Multi-region replication for critical data - Documentation and runbooks - Periodic DR drills
Compliance and Governance¶
Resource Hierarchy¶
Organization Structure:
Organization
βββ Folder (Business Unit)
β βββ Folder (Environment)
β β βββ Project (Application)
β β βββ Project (Application)
- π Resource Hierarchy - Organization structure
- π Organization Policies - Centralized constraints
- π Project Best Practices - Project design
Compliance and Certifications¶
Regulatory Compliance: - ISO 27001, SOC ⅔, PCI-DSS, HIPAA, GDPR - Regional data residency controls - Compliance reports and certifications - π Compliance Offerings - Certifications and reports - π Data Residency - Location controls
Common Architecture Patterns¶
Pattern 1: Three-Tier Web Application¶
Architecture: - Presentation Tier - Cloud Load Balancer + Cloud CDN - Application Tier - Managed Instance Group (auto-scaling) - Data Tier - Cloud SQL with read replicas
Key Services: - Global HTTP(S) Load Balancer - Cloud CDN for static assets - Cloud Armor for DDoS protection - VPC with private subnets - Cloud SQL with HA configuration
Pattern 2: Microservices on GKE¶
Architecture: - GKE Autopilot or Standard cluster - Workload Identity for service authentication - Cloud SQL Proxy for database access - Anthos Service Mesh for observability
Key Services: - GKE with VPC-native networking - Cloud Build for CI/CD - Artifact Registry for container images - Cloud Monitoring for observability
Pattern 3: Real-Time Data Pipeline¶
Architecture: - Ingestion - Pub/Sub for event streaming - Processing - Dataflow for stream processing - Storage - BigQuery for analytics - Visualization - Looker or Data Studio
Key Services: - Pub/Sub for decoupling - Dataflow for ETL - BigQuery for warehousing - Dataproc for Hadoop/Spark workloads
Pattern 4: Serverless Application¶
Architecture: - Cloud Run or Cloud Functions for compute - Firestore for NoSQL database - Cloud Storage for object storage - API Gateway for API management
Key Services: - Cloud Run with automatic scaling - Eventarc for event routing - Secret Manager for credentials - Cloud CDN for caching
Pattern 5: Hybrid Cloud with Anthos¶
Architecture: - GKE clusters on GCP and on-premises - Anthos Config Management for policy - Anthos Service Mesh for networking - Cloud Interconnect for connectivity
Key Services: - Anthos GKE on-prem - Cloud VPN or Interconnect - Binary Authorization - Cloud Operations suite
Data Engineering Architecture¶
Batch Processing¶
MapReduce and Spark: - Dataproc - Managed Hadoop and Spark - Dataflow - Serverless Apache Beam pipelines - π Dataproc - Managed big data - π Dataflow - Stream and batch processing
Stream Processing¶
Real-Time Analytics: - Pub/Sub - Global message queue - Dataflow - Stream processing - Bigtable - High-throughput writes - π Pub/Sub - Messaging architecture - π Streaming Analytics - Reference architecture
Data Warehousing¶
BigQuery Architecture: - Columnar storage for analytics - Automatic query optimization - Federated queries across sources - π BigQuery Best Practices - Performance guide
Machine Learning and AI¶
AI Platform and Vertex AI¶
ML Workflow: - Vertex AI - Unified ML platform - Training with custom or pre-built containers - Model deployment and serving - π Vertex AI - ML platform - π AutoML - No-code ML
Pre-Trained APIs¶
AI Services: - Vision API, Natural Language API, Translation API - Speech-to-Text, Text-to-Speech - π Cloud AI Products - AI/ML services
DevOps and CI/CD¶
Cloud Build¶
Continuous Integration: - Serverless build service - Container and non-container builds - Integration with GitHub, Bitbucket, Cloud Source Repositories - π Cloud Build - CI/CD platform
Infrastructure as Code¶
Deployment Automation: - Deployment Manager - Native GCP IaC - Terraform - Multi-cloud IaC (popular choice) - Config Connector - Kubernetes-native GCP resource management - π Deployment Manager - GCP native IaC - π Terraform on GCP - Terraform integration
Exam Scenarios and Solutions¶
Scenario 1: High-Traffic Web Application¶
Requirements: Handle millions of requests, global users, cost-effective
Solution: - Global HTTP(S) Load Balancer with Cloud CDN - Regional Managed Instance Groups with autoscaling - Cloud SQL with read replicas or Cloud Spanner - Cloud Storage for static assets - Cloud Armor for security
Key Decision: Cloud Spanner if multi-region writes needed, else Cloud SQL with cross-region read replicas
Scenario 2: Lift-and-Shift Migration¶
Requirements: Migrate 100+ VMs from on-premises quickly
Solution: - Migrate for Compute Engine - Phased migration approach - Cloud VPN or Interconnect for connectivity - Use Committed Use Discounts for cost savings
Key Decision: Start with non-critical workloads, validate, then migrate production
Scenario 3: Real-Time Analytics¶
Requirements: Ingest millions of events per second, real-time dashboards
Solution: - Pub/Sub for ingestion - Dataflow for stream processing - BigQuery for data warehouse - Bigtable for operational queries - Looker or Data Studio for visualization
Key Decision: BigQuery for ad-hoc analytics, Bigtable for operational low-latency queries
Scenario 4: Hybrid Cloud¶
Requirements: Keep sensitive data on-premises, use GCP for compute
Solution: - Cloud Interconnect (dedicated) for consistent performance - Shared VPC for network segregation - Private Google Access for API calls - Cloud SQL with private IP - Anthos if running Kubernetes workloads
Key Decision: Dedicated Interconnect vs Partner Interconnect based on bandwidth needs
Scenario 5: Disaster Recovery¶
Requirements: RPO < 1 hour, RTO < 4 hours
Solution: - Pilot Light strategy - Cloud SQL automated backups - Persistent disk snapshots to Cloud Storage - Infrastructure as Code for rapid deployment - Runbooks in Cloud Storage
Key Decision: Warm Standby if stricter RTO/RPO needed
Scenario 6: Multi-Tenant SaaS¶
Requirements: Isolate customer data, cost attribution
Solution: - Separate projects per customer (strong isolation) - OR Shared infrastructure with tagging (cost-effective) - Folder hierarchy for organization - Labels for cost allocation - VPC Service Controls for data exfiltration protection
Key Decision: Isolation level vs cost trade-off
Exam Tips and Strategy¶
Keywords to Watch¶
Question Patterns: - "Cost-effective" β Committed use, preemptible, autoscaling, Cloud Functions/Run - "Minimize operational overhead" β Managed services, serverless, GKE Autopilot - "High availability" β Multi-zone, multi-region, load balancing - "Low latency" β Memorystore, CDN, proximity to users, Bigtable - "Compliance/regulatory" β VPC Service Controls, organization policies, audit logs - "Real-time" β Pub/Sub, Dataflow, Bigtable - "Big data analytics" β BigQuery, Dataproc, Dataflow - "Secure" β VPC, IAM, CMEK, Private Google Access
Service Selection Decision Trees¶
Compute Decision:
Stateless application?
ββ YES β Container?
β ββ YES β Need Kubernetes?
β β ββ YES β GKE
β β ββ NO β Cloud Run
β ββ NO β Need custom runtime?
β ββ YES β App Engine Flexible
β ββ NO β App Engine Standard
ββ NO β Compute Engine
Database Decision:
Relational needed?
ββ YES β Global transactions?
β ββ YES β Cloud Spanner
β ββ NO β Cloud SQL
ββ NO β Data model?
ββ Key-Value/Document β Firestore
ββ Wide-Column β Bigtable
ββ Analytics β BigQuery
Time Management¶
- 120 minutes Γ· 50 questions = 2.4 minutes per question
- First pass: Answer confident questions (60 minutes)
- Second pass: Tackle difficult questions (45 minutes)
- Final pass: Review flagged questions (15 minutes)
Common Traps¶
- β Choosing complex solutions when simple ones suffice
- β Ignoring cost constraints
- β Over-emphasizing technical perfection vs business needs
- β Not considering operational overhead
- β Forgetting about managed service alternatives
- β Mixing up service capabilities and limits
Study Checklist¶
Knowledge Areas: - [ ] Can design multi-tier applications on GCP - [ ] Understand VPC networking, shared VPC, and VPC peering - [ ] Know when to use each compute option (GCE, GKE, App Engine, Cloud Run, Functions) - [ ] Can select appropriate database for use case - [ ] Understand migration strategies and tools - [ ] Know cost optimization techniques - [ ] Can design for high availability and disaster recovery - [ ] Understand IAM, service accounts, and security best practices - [ ] Know monitoring and logging setup - [ ] Familiar with hybrid connectivity options
Preparation: - [ ] Hands-on experience with GCP (build actual projects) - [ ] Review all case studies on exam guide - [ ] Complete practice exams (80%+ score) - [ ] Read official GCP Architecture Framework - [ ] Review common reference architectures - [ ] Practice with GCP Console and gcloud CLI
Pro Tip: The Professional Cloud Architect exam tests your ability to make architecture trade-offs based on business requirements. Always consider: cost, operational overhead, performance, security, compliance, and scalability. The "best" answer balances all these factors based on scenario constraints!
Documentation Count: This fact sheet contains 100+ embedded documentation links to official Google Cloud documentation.
Good luck! This certification demonstrates expert-level cloud architecture skills on Google Cloud Platform.