Google Cloud Professional Cloud Architect Managing and Provisioning a Solution Infrastructure Flashcards

24 sample cards from the Managing and Provisioning a Solution Infrastructure deck

Sampled from the end of the deck, so these are different cards from the ones shown on the syllabus page.

1. What is a Managed Instance Group (MIG) and what three capabilities does it provide?

   A MIG creates identical VMs from an instance template and provides autoscaling, autohealing (health-check-based recreation), and automated/rolling updates plus load balancing integration.

2. What is the difference between a zonal and a regional MIG?

   A zonal MIG places all instances in one zone; a regional MIG spreads instances across multiple zones in a region for higher availability.

3. What signals can Compute Engine autoscaling for a MIG be based on?

   CPU utilization, HTTP(S) load balancing serving capacity, Cloud Monitoring custom metrics, and schedule-based scaling. A target value is set and the autoscaler adds/removes instances to meet it.

4. In MIG updates, what is the difference between a rolling update and a canary update?

   A rolling update gradually replaces all instances with the new template (controlled by maxSurge/maxUnavailable); a canary update applies the new template to only a subset (e.g., target size) to test before full rollout.

5. What are the high-availability options for Cloud SQL?

   Cloud SQL HA uses a regional configuration with a primary and a standby instance in a different zone, with automatic failover; read replicas can be added for read scaling (and cross-region DR).

6. What is AlloyDB and how does it relate to Cloud SQL/PostgreSQL?

   AlloyDB is a fully managed, PostgreSQL-compatible database optimized for high performance and analytical (HTAP) workloads, offering better performance and scalability than standard Cloud SQL for PostgreSQL via a disaggregated storage architecture and columnar engine.

7. What scaling/consistency properties make Cloud Spanner unique?

   Spanner is a globally distributed, horizontally scalable relational database providing strong consistency and high availability with up to 99.999% SLA (multi-region), using TrueTime for external consistency.

8. What is Bigtable best suited for, and what data model does it use?

   Bigtable is a NoSQL wide-column store for large-scale, low-latency, high-throughput analytical and operational workloads (time-series, IoT, AdTech). It uses a single-key (row key) sorted, sparse table model with no SQL/joins.

9. How does Bigtable performance scale, and what is the rough throughput per node?

   Bigtable scales linearly by adding nodes; each SSD node handles roughly 10,000 QPS (reads or writes) at ~6 ms latency. Capacity/performance grows with node count.

10. What are the two modes of Firestore and how do they differ?

    Native mode (document database with real-time listeners, offline sync, strong consistency, for mobile/web apps) and Datastore mode (backward-compatible with Datastore for server workloads, no real-time/offline features).

11. In Bigtable, why is row key design critical?

    Because data is sorted by row key and stored contiguously, poorly designed keys (e.g., sequential timestamps) cause hotspotting; well-distributed keys spread reads/writes evenly across nodes to avoid bottlenecks.

12. What is Terraform and what are its core files/commands for Google Cloud?

    Terraform is HashiCorp's declarative infrastructure-as-code tool. It uses .tf config files and the google provider; core workflow is terraform init, plan, and apply, with state stored (ideally in a GCS backend).

13. Why store Terraform state in a Cloud Storage bucket, and what feature prevents concurrent corruption?

    A GCS remote backend centralizes/shares state and enables state locking (via object generation/Cloud Storage) so concurrent applies don't corrupt state; it also keeps sensitive state off local machines.

14. What is Infrastructure Manager in Google Cloud?

    Infrastructure Manager is Google's managed service that provisions infrastructure using Terraform configurations, automating Terraform execution with state management, IAM integration, and versioned deployments.

15. What is Config Connector and what does it enable?

    Config Connector is a GKE add-on (Kubernetes addon) that lets you manage Google Cloud resources as Kubernetes objects (via CRDs/YAML), so you provision GCP infrastructure using kubectl and Kubernetes-native, declarative reconciliation.

16. What is Cloud Marketplace and what deployment benefit does it provide?

    Cloud Marketplace offers pre-configured, vendor-provided solutions (VM images, Kubernetes apps, SaaS) that can be deployed into your project with one click, often using Deployment Manager/Terraform under the hood and integrated/unified billing.

17. What is the Google Cloud resource hierarchy from top to bottom?

    Organization → Folders → Projects → Resources. IAM policies and organization policies set at a higher level are inherited by everything below.

18. What is the difference between IAM policies and Organization Policies?

    IAM policies define who (identity) can do what (role) on a resource; Organization Policies (constraints) define what configurations are allowed on resources (e.g., restrict allowed regions, disable external IPs), regardless of identity.

19. What is a project's role in the GCP resource hierarchy and billing?

    A project is the base-level organizing entity that contains resources, is the unit for enabling APIs, IAM, quotas, and billing; every resource belongs to exactly one project, and projects link to a billing account.

20. What is an organization policy constraint, and name two common examples?

    A constraint is a rule applied via Organization Policy Service to restrict resource configurations. Examples: constraints/compute.vmExternalIpAccess (disable external IPs) and constraints/gcp.resourceLocations (restrict resource regions).

21. What is Shared VPC and what problem does it solve in the resource hierarchy?

    Shared VPC lets a host project share its VPC network with multiple service projects in the same organization, so resources in different projects use a centrally managed network — separating network admin from project admins.

22. What is VPC Network Peering and one key limitation versus a single VPC?

    VPC Peering privately connects two VPCs (even across projects/orgs) so they exchange traffic using internal IPs. Limitation: peering is non-transitive (peered VPCs don't share each other's other peers) and subnet IP ranges must not overlap.

23. For data retention compliance, how do Cloud Storage retention policies and lifecycle rules work together?

    Retention policies enforce a minimum time objects must be kept (preventing deletion); lifecycle rules then automate transition to colder classes and eventual deletion once the retention period and age conditions are met.

24. What is the difference between Compute Engine sole-tenant nodes and standard shared-core provisioning?

    Sole-tenant nodes dedicate an entire physical server to a single customer's VMs (for compliance/licensing isolation), whereas standard VMs share host hardware with other tenants.

What this deck covers

Managing and Provisioning a Solution Infrastructure flashcards FAQ