Examkin

All practice questions

1598 questions

All types1,598Multiple choice815Multiple select537Numeric8Matching64Ordering174
Question 1281Question →

A logistics enterprise is designing the cloud architecture for its real-time package tracking API and regional operational backend on Google Cloud. The solution must satisfy the following technical and high-availability requirements:

1. The stateless tracking API microservices receive bursty HTTP traffic and must auto-scale dynamically without introducing server management overhead.
2. Hybrid connectivity between the on-premises data center and GCP must support up to 1.5 Gbps1.5\text{ Gbps} of encrypted steady-state throughput with 99.99%99.99\% availability.

Which TWO architectural decisions should you include in your design to meet these requirements? (Select 2 answers)

Select all that apply

Show answer & explanation

Answer: Deploy the stateless tracking API microservices to Cloud Run and front them with an External Application Load Balancer.; Provision HA Cloud VPN with two active-active IPsec tunnels using BGP dynamic routing across distinct availability zones.

Answer

Deploy the stateless API microservices using Cloud Run fronted by an External Application Load Balancer, and establish hybrid connectivity using HA Cloud VPN with two active-active IPsec tunnels via BGP dynamic routing.
Deploying the microservices on Cloud Run provides serverless container execution that scales automatically down to zero and handles bursty HTTP traffic without cluster maintenance. Pairing this with HA Cloud VPN satisfies the 1.5 Gbps bandwidth requirement (as HA Cloud VPN supports up to 3 Gbps per tunnel) while delivering a high availability SLA of 99.99% through dual active-active IPsec tunnels across separate availability zones.

Step-by-Step Solution

1
Evaluate compute requirements for stateless API microservices
Identify Cloud Run as the optimal serverless execution engine for HTTP traffic that requires zero cluster management and automatic scaling.
Stateless microservices with bursty HTTP traffic benefit from Cloud Run's fully managed execution rather than managing GKE cluster infrastructure.
2
Evaluate hybrid networking options for 1.5 Gbps bandwidth and 99.99% SLA
Identify HA Cloud VPN as the correct choice since each tunnel delivers up to 3 Gbps encrypted bandwidth, and dual topology achieves 99.99% availability.
Dedicated Interconnect is designed for higher bandwidth (10 Gbps or 100 Gbps circuits) and is unnecessary for a 1.5 Gbps workload, whereas HA Cloud VPN natively meets the throughput and SLA requirements.

Key Concept

Designing high-availability cloud architecture balancing managed compute and redundant hybrid networking based on explicit technical SLAs and capacity requirements.
Question 1282Question →

An enterprise financial services organization is designing the data storage architecture for a new regional transaction auditing platform on Google Cloud. The system operates exclusively within a single Google Cloud region (us-east4) and requires a relational database supporting strict ACID transactions, complex SQL queries, and automatic failover across zones. Peak database throughput is estimated at 8,000 queries per second with required latencies under 10 milliseconds. A primary business requirement is to strictly minimize infrastructure costs by avoiding global database overhead. Furthermore, 2 PB of historical audit log files currently stored on-premises must be migrated offline to Cloud Storage, and data security governance mandates protecting Cloud Storage against unauthorized exfiltration by internal service accounts. Which architecture meets all technical and business requirements?

Show answer & explanation

Answer: Deploy Cloud SQL for PostgreSQL configured with High Availability (HA) across two zones in us-east4, utilize Google Cloud Transfer Appliance for the offline audit log migration, and enforce a VPC Service Controls perimeter around Cloud Storage.

Answer

Deploy Cloud SQL for PostgreSQL configured with High Availability (HA) across two zones in us-east4, utilize Google Cloud Transfer Appliance for the offline audit log migration, and enforce a VPC Service Controls perimeter around Cloud Storage.
The solution correctly pairs Cloud SQL for PostgreSQL HA for single-region cost-effective relational processing, Transfer Appliance for multi-petabyte offline migration, and VPC Service Controls to prevent exfiltration.

Step-by-Step Solution

1
Evaluate the database tier requirements.
Cloud SQL for PostgreSQL with HA meets single-region ACID relational database needs with high throughput and lower cost than Cloud Spanner.
Cloud Spanner is designed for globally distributed, multi-region database workloads and carries higher baseline costs unnecessary for single-region requirements.
2
Evaluate the data transfer mechanism for 2 PB of historical logs.
Transfer Appliance is required for offline physical data shipment.
Transferring multi-petabyte datasets over internet connections using Storage Transfer Service would take months and saturate network capacity.
3
Evaluate security controls against data exfiltration.
VPC Service Controls must be configured around Cloud Storage resources.
IAM permissions control identity access, but VPC Service Controls define a security perimeter that prevents copying data to external projects or unauthorized storage buckets.

Key Concept

Selecting GCP database and data transfer services based on regional scale, cost optimization, physical migration limits, and security perimeters.
Question 1283Question →

A financial services organization is designing a high-availability architecture for its stateless payment gateway microservices on Google Cloud. The architecture must achieve a 99.99% availability SLA, support automatic multi-region failover during a regional outage, and handle unpredictable traffic bursts seamlessly. To minimize operational costs and infrastructure management overhead, which compute deployment strategy should you recommend?

Show answer & explanation

Answer: Deploy the stateless microservices to Cloud Run across multiple regions behind a global External HTTP(S) Load Balancer.

Answer

Deploy the stateless microservices to Cloud Run across multiple regions behind a global External HTTP(S) Load Balancer.
Deploying stateless microservices to Cloud Run in multiple regions behind a global External HTTP(S) Load Balancer meets the 99.99% availability requirement with automatic cross-region failover while removing compute management overhead.

Step-by-Step Solution

1
Analyze technical and operational requirements
Identified stateless microservice workload needing multi-region high availability (99.99% SLA) and minimal management overhead.
Stateless containerized services benefit most from serverless infrastructure.
2
Select optimal compute layer
Selected Cloud Run deployed in multiple GCP regions.
Cloud Run scales instantly from zero to handle unpredictable bursts without requiring cluster administration or VM patch management.
3
Configure global traffic management
Added a global External HTTP(S) Load Balancer routing to Serverless Network Endpoint Groups (NEGs) in each region.
The global load balancer directs user traffic to the nearest healthy region and automatically redirects requests if a region becomes unavailable.

Key Concept

Designing High Availability for Stateless Microservices using Cloud Run and Global Load Balancing
Estimated Time:1m 30s
Question 1284Question →

A regional media streaming company is architecting a storage backend for user profile management and subscription entitlements. The workload requires strict ANSI SQL compliance, full ACID transactional guarantees, automated regional high availability across multiple zones, and encryption at rest using Customer-Managed Encryption Keys (CMEK) via Cloud KMS. The total database footprint is estimated at 2 TB, and all application traffic originates within a single GCP region. Which GCP database service should the cloud architect recommend to fulfill these requirements while minimizing cost and operational complexity?

Show answer & explanation

Answer: Cloud SQL for PostgreSQL configured with High Availability (regional failover) and Customer-Managed Encryption Keys (CMEK).

Answer

Cloud SQL for PostgreSQL configured with High Availability (regional failover) and Customer-Managed Encryption Keys (CMEK).
The correct recommendation is Cloud SQL for PostgreSQL configured with High Availability (HA) and Customer-Managed Encryption Keys (CMEK). Cloud SQL supports databases up to 64 TB, delivers full ANSI SQL compliance and ACID transactional semantics, provides regional cross-zone failover for high availability, and seamlessly integrates with Cloud KMS for CMEK governance at an optimal price point for single-region applications.

Step-by-Step Solution

1
Analyze the workload storage requirements
Identified requirements for relational ANSI SQL, strict row-level ACID transactions, single-region deployment, 2 TB scale, high availability, and CMEK key management.
Establishing accurate data access patterns and scaling bounds determines the target GCP database class (OLTP vs OLAP vs NoSQL).
2
Compare candidate GCP database options against workload characteristics
Cloud SQL for PostgreSQL easily supports 2 TB relational OLTP workloads with multi-zone HA failover and Cloud KMS CMEK encryption in a single region. Cloud Spanner is over-provisioned and costly for non-global multi-region scale.
Choosing the appropriate managed database avoids over-engineering and controls infrastructure expenditure.
3
Validate security key management options
Cloud SQL integrates directly with Cloud KMS for Customer-Managed Encryption Keys (CMEK). Customer-Supplied Encryption Keys (CSEK) are not supported on Cloud SQL.
Ensuring regulatory security compliance requires choosing supported GCP encryption mechanisms.

Key Concept

Selecting Cloud SQL over Cloud Spanner for regional relational workloads
Estimated Time:1m 30s
Question 1285Question →

A global media streaming provider is architecture-designing its next-generation GCP storage layer. The architecture must support two core workloads with distinct performance and transactional operational requirements:

1. A global user subscription entitlement database requiring relational SQL capabilities, multi-region synchronous write consistency, high availability across continents, and seamless horizontal scale without application downtime.
2. A high-throughput telemetry engine recording real-time user playback interaction events (time-series data) generating millions of write requests per second with sub-10ms write latency.

Which TWO storage and database service selections should the cloud architect recommend to satisfy these requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Deploy Cloud Spanner to manage the global user subscription entitlement database.; Deploy Cloud Bigtable to handle the high-throughput real-time user playback interaction telemetry.

Answer

The optimal architectural selection requires Cloud Spanner for the globally distributed transactional relational subscription entitlement database and Cloud Bigtable for the high-throughput real-time playback telemetry workload.
Cloud Spanner fulfills the requirement for a multi-region relational database with strong global consistency and horizontal write scaling. Cloud Bigtable delivers the low sub-10ms write latency and high throughput required for real-time time-series telemetry processing.

Step-by-Step Solution

1
Analyze the requirements for the subscription entitlement database.
Identified needs for multi-region relational SQL, synchronous global write consistency, and horizontal scale.
Cloud Spanner is Google Cloud's globally distributed relational database offering relational features with multi-region strong consistency.
2
Analyze the requirements for the playback telemetry engine.
Identified needs for high write throughput, time-series access pattern, and sub-10ms write latency at scale.
Cloud Bigtable is a NoSQL wide-column database engineered specifically for high-volume time-series and low-latency streaming write workloads.
3
Evaluate and eliminate non-conforming service options.
Cloud SQL with cross-region replicas lacks multi-region write consistency and horizontal scale. CSEK unnecessarily adds raw key management overhead compared to CMEK.
Cloud SQL regional boundaries limit multi-region write scalability, while CSEK places raw key security management on the customer.

Key Concept

Selecting GCP Storage Services Based on Scalability, Consistency, and Workload Access Patterns
Estimated Time:2m 0s
Question 1286Question →

Match each application workload requirement to the Google Cloud storage or database service that best fulfills its operational and architectural needs.

Click a left item, then click its matching right item

Items

Ingesting high-velocity streaming IoT telematics data requiring low write latency, time-series indexing, and seamless scaling to petabytes of data.
Serving a global e-commerce payment transaction platform requiring multi-region relational ACID compliance, horizontal scaling, and 99.999% availability.
Storing compliance audit documents for long-term cold archive with bucket-level lock policies for Write Once Read Many (WORM) immutability.
Powering a mobile application with semi-structured user profile data that requires real-time document synchronization and offline state caching.

Matches

Show answer & explanation

Answer

High-velocity IoT streaming matches with Cloud Bigtable; Global transactional ACID relational database matches with Cloud Spanner; Immutable compliance document archive matches with Cloud Storage (Archive class); Mobile document sync with offline support matches with Firestore in Native mode.
Each GCP database and storage service is purpose-built for specific access patterns: Cloud Bigtable handles massive throughput key-value and time-series streams; Cloud Spanner provides globally consistent relational transactions; Cloud Storage Archive handles low-cost long-term immutable object storage; and Firestore supports real-time document synchronization with mobile clients.

Step-by-Step Solution

1
Analyze access pattern and throughput needs for time-series IoT ingestion.
High-velocity writes and petabyte-scale key-value capabilities point directly to Cloud Bigtable.
Cloud Bigtable delivers single-digit millisecond latency for massive write-heavy analytical workloads.
2
Analyze global relational and availability requirements for transactional payment processing.
Global ACID transactions and 99.999% availability point to Cloud Spanner.
Cloud Spanner is Google Cloud's globally distributed relational database designed for high availability and strict transactional consistency across regions.
3
Evaluate long-term compliance storage requirements for WORM immutability.
Unstructured document retention with WORM policies maps to Cloud Storage Archive class with Bucket Lock.
Cloud Storage offers specialized storage classes for infrequent access alongside bucket retention policies for regulatory compliance.
4
Identify database model needed for real-time mobile user sync and offline caching.
Flexible document structure with real-time updates maps to Firestore in Native mode.
Firestore native client SDKs feature automatic offline data sync and real-time data push mechanisms.

Key Concept

Selecting and Designing Storage and Database Resources
Estimated Time:2m 0s
Question 1287Question →

A healthcare enterprise is designing its cloud architecture on Google Cloud for a patient medical imaging retrieval API and metadata repository. On-premises hospitals must securely stream imaging data to Google Cloud over a dedicated hybrid network connection requiring a sustained throughput of 15 Gbps with 99.99% availability. The imaging retrieval service consists of stateless, containerized HTTP microservices with variable traffic patterns that require low operational overhead. The relational metadata database operates within a single GCP region and requires high availability with automatic zonal failover, but does not require global multi-region write replication. Which TWO architectural decisions should you implement to satisfy these high availability and technical requirements?

Select all that apply

Show answer & explanation

Answer: Provision redundant Dedicated Interconnect connections with at least two 10 Gbps circuits terminating in separate edge availability domains.; Deploy the stateless HTTP microservices on Cloud Run and utilize Cloud SQL in a High Availability (HA) dual-zone configuration for the metadata database.

Answer

The optimal architecture requires provisioning redundant Dedicated Interconnect circuits (at least 10 Gbps each across separate edge availability domains) to meet the 15 Gbps throughput and 99.99% SLA requirements, along with deploying stateless containers on Cloud Run backed by a regional Cloud SQL HA instance.
To satisfy 15 Gbps sustained bandwidth and a 99.99% uptime SLA, Dedicated Interconnect with redundant 10 Gbps circuits across distinct edge availability domains is required. For the application tier, Cloud Run provides a serverless platform for stateless HTTP services with minimal operational overhead, and Cloud SQL in HA mode provides automatic cross-zone failover for single-region relational data without the cost and complexity of Cloud Spanner.

Step-by-Step Solution

1
Evaluate hybrid network throughput and SLA requirements
Sustained throughput of 15 Gbps exceeds the standard per-tunnel limit of Cloud VPN (3 Gbps per tunnel). Achieving 99.99% availability requires Dedicated Interconnect configured across two edge availability domains in a single region or metro.
Dedicated Interconnect provides dedicated physical 10 Gbps or 100 Gbps pipes to GCP, satisfying high bandwidth and stringent uptime SLAs.
2
Evaluate compute tier requirements for stateless HTTP microservices
Cloud Run provides fully managed serverless container execution for stateless HTTP workloads, automatically scaling based on incoming web traffic without server or cluster administration.
Cloud Run minimizes operational overhead compared to managing GKE cluster control planes and node pools for simple stateless services.
3
Evaluate database requirements for single-region HA relational storage
Cloud SQL with High Availability (HA) configuration replicates data synchronously to a standby instance in a secondary zone within the same region and supports automatic failover.
Cloud Spanner is over-engineered and costly for workloads that do not require horizontal write scaling across multiple regions.

Key Concept

Designing High-Availability Hybrid Networks and Compute/Storage Tier Selection
Question 1288Question →

An enterprise retail company is designing the data architecture for a new e-commerce platform on Google Cloud. The application architecture requires two separate storage components:
1. A transactional relational database for order processing that must support SQL queries, scale across multiple geographic regions, and guarantee strong ACID consistency.
2. A high-throughput, low-latency key-value store to maintain real-time user shopping cart sessions.

Which TWO Google Cloud database services should the Cloud Architect select to meet these requirements?

Select all that apply

Show answer & explanation

Answer: Cloud Spanner for global multi-region transactional order processing with strong ACID compliance.; Cloud Bigtable for high-throughput, low-latency key-value shopping cart session storage.

Answer

Cloud Spanner for global multi-region transactional order processing, and Cloud Bigtable for high-throughput, low-latency session key-value storage.
Cloud Spanner is specifically designed for globally distributed relational workloads requiring strong ACID consistency and multi-region write scalability. Cloud Bigtable delivers high-throughput, low-latency key-value performance required for user session tracking.

Step-by-Step Solution

1
Analyze the requirements for the order processing database
The database requires relational SQL support, multi-region horizontal scaling, and strong ACID consistency.
Cloud Spanner is the only native GCP database offering globally distributed relational scale with strong consistency.
2
Analyze the requirements for the shopping cart session database
The database requires high throughput, sub-10ms response latency, and a key-value data structure.
Cloud Bigtable excels at scalable key-value access with single-digit millisecond latency.
3
Evaluate and reject improper storage options
Cloud SQL cannot support multi-region scale with global consistency, and Storage Transfer Service is an offline/batch transfer tool.
Matching workload access patterns and scalability boundaries ensures valid architectural selection.

Key Concept

Database Selection based on Scale, Latency, and Consistency Requirements
Question 1289Question →

A digital media streaming provider is designing a high-availability architecture on Google Cloud for its user profile and session management REST API service. The workload consists of stateless HTTP services experiencing variable traffic up to 5,000 requests per second. The backend database requires regional transactional consistency with low Recovery Time Objective (RTO) zonal failover, but does not require global multi-region write replication. The on-premises operations center requires a resilient connection to the Google Cloud VPC, with aggregate peak traffic limited to 1.5 Gbps. Which architecture meets all technical and high availability requirements while minimizing operational overhead and cost?

Show answer & explanation

Answer: Deploy the stateless REST API service on Cloud Run with a Serverless VPC Access connector, store user profile data in a regional Cloud SQL instance configured for High Availability across multiple zones, and establish hybrid connectivity using HA Cloud VPN.

Answer

The optimal architecture combines Cloud Run for stateless compute auto-scaling, a Regional Cloud SQL instance configured for zonal High Availability (HA), and HA Cloud VPN for hybrid network connectivity under 3 Gbps.
The solution combining Cloud Run, regional HA Cloud SQL, and HA Cloud VPN meets all operational SLAs with minimal cost and management overhead. Cloud Run auto-scales stateless HTTP APIs efficiently. Regional Cloud SQL with HA provides automatic failover between zones in a single region to satisfy RTO/RPO goals. HA Cloud VPN supports up to 3 Gbps per tunnel with a 99.99% SLA, making it ideal for the 1.5 Gbps peak hybrid bandwidth requirement.

Step-by-Step Solution

1
Evaluate Compute Requirements
Cloud Run is selected over GKE because the service consists of simple stateless HTTP REST APIs requiring serverless scale-to-zero without cluster management overhead.
Choosing GKE for simple HTTP REST services adds unnecessary cluster management complexity and baseline infrastructure cost.
2
Evaluate Database High Availability Requirements
Regional Cloud SQL with HA (primary and standby instances in separate zones within the same region with automatic failover) meets the RTO and transactional consistency requirements.
Cloud Spanner is designed for globally distributed relational databases across regions; using it for regional workloads introduces excessive cost and over-engineering.
3
Evaluate Hybrid Connectivity Throughput Requirements
HA Cloud VPN provides 99.99% availability and up to 3 Gbps bandwidth per tunnel, satisfying the 1.5 Gbps peak bandwidth requirement.
Dedicated Interconnect is intended for high-bandwidth workloads (10 Gbps/100 Gbps) or strict non-Internet connectivity, making it cost-prohibitive for a 1.5 Gbps connection.

Key Concept

Selecting right-sized high-availability compute, database, and networking primitives to meet technical RTO/RPO SLAs without over-engineering.
Question 1290Question →

Match each enterprise workload requirement to the most appropriate Google Cloud storage or database service.

Click a left item, then click its matching right item

Items

Global financial ledger requiring horizontal scaling for relational tables, strong consistency across multiple regions, and full ACID transaction support.
Real-time vehicle telemetry ingest engine requiring sub-10ms latency for massive write throughput of structured key-value time-series records.
Regional human resources portal requiring a managed relational database with full PostgreSQL compatibility, high availability, and routine point-in-time recovery.
Centralized media archive needing store-once-read-many (ORM) immutability rules, multi-region durability, and automatic cost-tiering over time.

Matches

Show answer & explanation

Answer

Global financial ledger pairs with Cloud Spanner; Real-time vehicle telemetry pairs with Cloud Bigtable; Regional HR portal pairs with Cloud SQL; Centralized media archive pairs with Cloud Storage.
Each GCP storage service is matched based on data structure (relational vs NoSQL vs object), transaction guarantees, geographical scope, and throughput characteristics. Cloud Spanner is built for multi-region relational ACID workloads; Cloud Bigtable excels at high-throughput time-series key-value access; Cloud SQL fits regional relational databases; and Cloud Storage is designed for unstructured object data with lifecycle policies.

Step-by-Step Solution

1
Analyze the relational data models and geographical consistency constraints.
Identified that the global financial ledger requires horizontal scaling with ACID transactions across regions (Cloud Spanner), whereas the regional portal requires standard PostgreSQL compatibility in a single region (Cloud SQL).
Cloud Spanner is designed for globally distributed relational scale, while Cloud SQL handles standard regional relational workloads.
2
Evaluate the non-relational access patterns and latency requirements.
Matched high-throughput key-value time-series telemetry to Cloud Bigtable.
Cloud Bigtable provides continuous low-latency write performance for heavy time-series workloads.
3
Evaluate unstructured data object storage requirements.
Matched media archiving with retention rules to Cloud Storage.
Cloud Storage natively supports object lifecycle management, bucket locks, and multi-region availability.

Key Concept

Selecting GCP Storage and Database Services Based on Access Patterns, Latency, and Scalability
Question 1291Question →

A financial technology startup is designing the transactional backend for a peer-to-peer payment processing service operating exclusively within a single Google Cloud region. The service requires a relational database that enforces strict ACID compliance and complex foreign key relationships. The infrastructure must provide high availability with automated failover and zero data loss (RPO = 0) during a single zonal outage. Peak throughput is estimated at 2,500 write transactions per second. Global multi-region scaling is explicitly out of scope, and minimizing operational cost is a primary constraint. Which database solution should the cloud architect choose?

Show answer & explanation

Answer: Provision a Cloud SQL for PostgreSQL instance with High Availability (HA) enabled across two zones.

Answer

Provision a Cloud SQL for PostgreSQL instance with High Availability (HA) enabled across two zones.
Cloud SQL for PostgreSQL with High Availability (HA) enabled fulfills all requirements: full ACID compliance, relational foreign key support, automatic failover across zones within a single region with zero data loss (RPO = 0), and a cost-effective price point suitable for single-region deployment.

Step-by-Step Solution

1
Analyze data model and transactional constraints.
Relational data model with strict ACID compliance and foreign key constraints requires a relational RDBMS (Cloud SQL or Cloud Spanner). NoSQL options like Cloud Bigtable or object storage like Cloud Storage are eliminated.
Live financial transaction workloads requiring complex queries and relational constraints must use a relational database.
2
Evaluate geographic scale and cost constraints.
Workload is strictly single-region, and cost minimization is required.
Cloud Spanner is designed for massive global horizontal scale and multi-region synchronization. For single-region workloads with standard throughput, Cloud SQL provides the required capabilities at significantly lower cost.
3
Verify High Availability configuration.
Enabling High Availability (HA) on Cloud SQL configures synchronous regional persistent disk replication to a standby instance in a second zone, satisfying the RPO = 0 requirement.
Cloud SQL HA ensures automatic failover without data loss during a zonal outage.

Key Concept

Selecting Cloud SQL over Cloud Spanner for single-region relational database workloads to satisfy ACID requirements while optimizing cost.
Question 1292Question →

Match each enterprise application workload requirement to the most appropriate Google Cloud database or storage service based on data model, access pattern, and scalability requirements.

Click a left item, then click its matching right item

Items

Globally distributed relational database requiring ANSI SQL compliance, horizontal write scaling, and multi-region strong consistency.
Massive-scale key-value store optimized for high-throughput, low-latency append-only time-series IoT device telemetry data.
Serverless NoSQL document database designed for modern web and mobile applications with native offline data synchronization.
Single-region operational OLTP relational database supporting standard PostgreSQL or MySQL with automated regional high-availability failover.

Matches

Show answer & explanation

Answer

The workload requirements match as follows: Global relational transactions with strong multi-region consistency map to Cloud Spanner; high-throughput time-series key-value telemetry maps to Cloud Bigtable; mobile document storage with offline sync maps to Firestore; single-region managed relational OLTP maps to Cloud SQL.
Each service aligns precisely with its intended workload: Cloud Spanner handles global relational scale; Cloud Bigtable manages high-throughput time-series key-value data; Firestore supports mobile document sync; Cloud SQL hosts single-region operational databases.

Step-by-Step Solution

1
Identify the storage requirements for global relational transactions needing multi-region strong consistency.
Matched with Cloud Spanner.
Cloud Spanner uniquely provides horizontally scalable ANSI SQL relational storage with multi-region strong consistency.
2
Identify the service for high-throughput time-series telemetry key-value storage.
Matched with Cloud Bigtable.
Cloud Bigtable is designed for massive key-value ingest throughput with single-digit millisecond latency.
3
Identify the database providing NoSQL document hierarchy with client offline synchronization.
Matched with Firestore.
Firestore offers mobile client SDK integration with real-time listeners and offline state persistence.
4
Identify the solution for standard single-region operational SQL workloads.
Matched with Cloud SQL.
Cloud SQL manages standard engines (PostgreSQL/MySQL/SQL Server) with regional HA failover.

Key Concept

Selecting GCP Database Services based on data structure, transaction model, scale, and latency requirements
Question 1293Question →

A digital health platform is designing its Google Cloud storage architecture to support two distinct workload requirements:
1. A transactional relational database for patient appointment scheduling operating strictly within a single GCP region that requires high availability across zones.
2. An initial migration of 2 petabytes of historical medical imaging records stored on-premises, where the existing 1 Gbps internet connection is heavily saturated during business hours.

Which two storage architecture decisions should the engineering team implement? (Select TWO answers.)

Select all that apply

Show answer & explanation

Answer: Deploy Cloud SQL for PostgreSQL configured with High Availability (regional failover across two zones) for the appointment scheduling database.; Order a Google Cloud Transfer Appliance to capture and physically ship the 2 petabytes of medical imaging data to Cloud Storage.

Answer

The architecture team should deploy Cloud SQL for PostgreSQL configured with High Availability for the single-region appointment database, and order a Google Cloud Transfer Appliance to perform the offline migration of the 2 petabyte imaging dataset.
Cloud SQL for PostgreSQL configured with High Availability delivers automated cross-zone failover within a single region for relational OLTP workloads. Google Cloud Transfer Appliance is the optimal solution for transferring multi-petabyte datasets offline when network bandwidth is constrained.

Step-by-Step Solution

1
Evaluate transactional database requirements.
The workload requires a relational OLTP database operating in a single region with cross-zone high availability.
Cloud SQL HA meets regional failover SLAs cost-effectively without requiring Cloud Spanner's global distributed scaling.
2
Evaluate data migration transfer constraints.
The migration involves moving 2 petabytes over a 1 Gbps network connection.
Streaming multi-petabyte datasets over a constrained 1 Gbps connection takes an impractically long time, making an offline physical transfer appliance necessary.

Key Concept

Selecting GCP database and migration resources based on regional transaction requirements, relational model fit, and data transfer network constraints.
Question 1294Question →

A global retail e-commerce company is re-architecting its online flash-sale transactional engine on Google Cloud to handle global customer traffic. The system must meet the following strict technical and availability requirements:

- The database tier requires multi-region high availability with strict serializable consistency, supporting transactional writes across multiple geographic regions with zero Recovery Point Objective (RPO).
- The hybrid connectivity between the company's primary on-premises data center and GCP must support a dedicated, SLA-backed private throughput of 15 Gbps without traversing the public internet.

Which TWO architectural decisions should the cloud architect choose to satisfy these requirements? (Choose two.)

Select all that apply

Show answer & explanation

Answer: Provision a multi-region Cloud Spanner instance for the transactional database tier.; Provision Dedicated Interconnect connections between the on-premises facility and Google Cloud.

Answer

The cloud architect should deploy a multi-region Cloud Spanner instance for global zero-RPO transactional data and establish Dedicated Interconnect connections for dedicated 15 Gbps private hybrid connectivity.
Combining multi-region Cloud Spanner with Dedicated Interconnect satisfies both technical constraints. Multi-region Cloud Spanner uses TrueTime and synchronous consensus replication to provide globally distributed, strongly consistent ACID transactions with zero RPO. Dedicated Interconnect delivers private physical connection circuits (10 Gbps or 100 Gbps per link) with uptime SLAs, fulfilling the requirement for 15 Gbps dedicated private bandwidth.

Step-by-Step Solution

1
Evaluate the database tier requirements against GCP storage products.
Cloud Spanner is selected because it delivers global multi-region active-active relational replication with strict serializability and zero RPO. Cloud SQL cannot deliver multi-region zero-RPO transactions, and Bigtable is a NoSQL store.
Technical requirements demand multi-region strong consistency and zero RPO for transactional data.
2
Evaluate the network connectivity options for bandwidth and transport requirements.
Dedicated Interconnect is selected because it provides physical direct fiber connections (10 Gbps / 100 Gbps circuits) with dedicated SLAs capable of carrying 15 Gbps. Cloud VPN is rejected due to its 3 Gbps per tunnel limit and reliance on public internet transit.
Technical requirements specify 15 Gbps throughput over a private connection with enterprise SLAs.

Key Concept

Designing Multi-Region High Availability and High-Throughput Hybrid Architecture
Question 1295Question →

A regional media publishing company is migrating its central subscription and billing management application to Google Cloud. The workload requires a transactional relational database schema, strong ACID consistency, standard SQL querying capabilities, and high availability within a single GCP region. The total database footprint is approximately 450 GB with predictable daily transactional throughput. Which database deployment architecture should you select to satisfy these requirements while minimizing operational cost and architectural complexity?

Show answer & explanation

Answer: Provision Cloud SQL for PostgreSQL with a high-availability regional configuration across two zones.

Answer

Provisioning Cloud SQL for PostgreSQL with a high-availability regional configuration across two zones.
The correct response recommends Cloud SQL for PostgreSQL with a high-availability regional configuration. Cloud SQL natively supports relational SQL schemas, ACID transactions, and automated zonal failover within a single GCP region. With a 450 GB footprint, Cloud SQL meets all functional and availability requirements at a fraction of the operational complexity and cost of globally distributed alternatives.

Step-by-Step Solution

1
Analyze data model and query requirements
The application requires transactional relational integrity, ACID guarantees, and standard SQL support, matching a relational database service (Cloud SQL or Cloud Spanner).
Non-relational databases or object storage cannot provide ACID transactional guarantees for billing schemas.
2
Evaluate scale and regional boundary requirements
The dataset is 450 GB and operates strictly within a single GCP region without requiring global multi-region write replication.
Cloud SQL supports single-region databases up to 30 TB, making Cloud Spanner unnecessary for this capacity.
3
Determine high availability architecture and cost optimization
Cloud SQL configured with high availability (HA) provides automatic failover to a standby instance in a secondary zone within the same region.
HA Cloud SQL meets the availability objective while minimizing license, node, and operational overhead.

Key Concept

Selecting appropriate GCP storage and database services based on data model, transaction scale, regional scope, and cost efficiency.
Estimated Time:1m 30s
Question 1296Question →

An online gaming enterprise is designing the infrastructure for a global multiplayer matchmaking service on Google Cloud. The frontend microservices are lightweight and stateless, requiring dynamic scaling to handle sudden traffic spikes with minimal operational overhead. The data tier manages active player session states and transactional matchmaking queues, requiring strong global consistency and high availability across multiple regions to ensure zero data loss during regional outages. Which architecture best satisfies these technical and availability requirements while minimizing operational complexity?

Show answer & explanation

Answer: Deploy the stateless microservices on Cloud Run across multiple regions, and use a multi-region Cloud Spanner instance for the transactional player session data tier.

Answer

Deploy the stateless microservices on Cloud Run across multiple regions, and use a multi-region Cloud Spanner instance for the transactional player session data tier.
Combining multi-region Cloud Run deployments with a multi-region Cloud Spanner database fulfills all constraints. Cloud Run automatically handles bursty traffic for stateless HTTP services across regions without managing cluster infrastructure. Cloud Spanner delivers globally distributed, strongly consistent SQL transactions with synchronous multi-region replication, eliminating regional single points of failure and meeting high availability targets.

Step-by-Step Solution

1
Evaluate compute tier requirements
Cloud Run is selected because it offers fully managed serverless container execution that scales automatically with rapid traffic spikes across regions without infrastructure overhead.
Lightweight, stateless microservices do not require complex cluster management provided by self-managed GKE, minimizing operational toil.
2
Evaluate database high availability and consistency requirements
Cloud Spanner configured in a multi-region deployment is selected.
Cloud Spanner provides synchronous multi-region replication with external consistency (ACID transactions) and high availability guarantees, enabling seamless regional failover with zero RPO.

Key Concept

Designing High Availability Cloud Architectures using Serverless Compute and Multi-Region Spanner
Estimated Time:1m 30s
Question 1297Question →

An automotive technology enterprise is building a telemetry and account management solution on Google Cloud. The application has two distinct storage requirements:

1. High-throughput, sub-10ms write latency ingestion for semi-structured sensor diagnostics arriving from millions of connected vehicles worldwide.
2. Standard relational database storage for customer subscription profiles and billing accounts that operates strictly within a single GCP region with high availability.

Which TWO database and storage services should you recommend to meet these requirements while optimizing cost and operational efficiency? (Select TWO)

Select all that apply

Show answer & explanation

Answer: Provision Cloud Bigtable to handle the high-throughput, low-latency semi-structured time-series sensor diagnostic data.; Provision Cloud SQL with High Availability (regional failover) for single-region relational customer subscription and billing data.

Answer

The optimal architecture combines Cloud Bigtable for high-throughput semi-structured telemetry data and Cloud SQL configured for High Availability for single-region relational subscription and billing records.
Selecting Cloud Bigtable provides scalable, low-latency NoSQL storage for massive semi-structured IoT telemetry ingestion. Selecting Cloud SQL configured for High Availability delivers fully managed, single-region relational ACID capabilities with automatic failover, satisfying all business and technical constraints cost-effectively.

Step-by-Step Solution

1
Analyze requirement 1 (IoT sensor diagnostic ingestion)
Semi-structured data requiring sub-10ms write latency at massive scale maps directly to Cloud Bigtable.
Cloud Bigtable provides wide-column NoSQL storage built for high-write-throughput time-series and IoT workloads.
2
Analyze requirement 2 (Relational account and billing storage)
Single-region relational workload requiring high availability maps to Cloud SQL in HA mode.
Cloud SQL satisfies single-region relational ACID requirements cost-effectively without global overhead.
3
Evaluate and reject distractors based on cost and workload suitability
Reject Cloud Spanner (unnecessary for single-region relational workloads) and Storage Transfer Service for offline petabyte data migration.
Choosing Spanner for single-region databases leads to over-provisioning, while online transfer for disconnected petabyte datasets is inefficient.

Key Concept

Selecting optimal GCP storage resources based on relational vs NoSQL access patterns, latency bounds, scale, and regional requirements.
Question 1298Question →

A global maritime freight company is designing a high-availability tracking and customs compliance system on Google Cloud. The system consists of stateless HTTP API microservices processing real-time vessel updates, backed by a transactional relational database. The solution must provide multi-region high availability with a Recovery Point Objective (RPO) of 0 and a Recovery Time Objective (RTO) under 1 minute across two GCP regions. Additionally, the system requires hybrid connectivity to an on-premises data center with a peak bandwidth requirement of 500 Mbps. Which architecture meets all technical requirements while minimizing operational complexity and cost?

Show answer & explanation

Answer: Deploy the stateless microservices on Cloud Run across both regions behind a Global External Application Load Balancer. Use a multi-region Cloud Spanner instance for the database, and establish HA VPN for hybrid connectivity to the on-premises data center.

Answer

Deploying stateless microservices on Cloud Run across two regions fronted by a Global External Application Load Balancer, using multi-region Cloud Spanner for zero RPO relational data storage, and connecting on-premises via HA VPN fulfills all HA, compliance, performance, and cost requirements.
The combination of Cloud Run for stateless compute, multi-region Cloud Spanner for globally consistent zero RPO database writes, and HA VPN for 500 Mbps hybrid connectivity perfectly satisfies the RTO, RPO, availability, and cost constraints.

Step-by-Step Solution

1
Evaluate compute requirements for stateless HTTP APIs
Cloud Run provides scalable, serverless container hosting across regions with lower operational overhead than Kubernetes Engine clusters.
Stateless microservices do not require complex Kubernetes orchestration.
2
Evaluate database requirements for multi-region zero RPO transactional consistency
Cloud Spanner configured with a multi-region instance configuration guarantees synchronous replication across regions and synchronous zero RPO failover.
Cloud SQL regional HA only covers single-region zone failures, and cross-region replication in Cloud SQL is asynchronous.
3
Evaluate hybrid networking requirements for 500 Mbps bandwidth
HA VPN supports up to 3 Gbps per tunnel, fully satisfying the 500 Mbps requirement cost-effectively.
Dedicated Interconnect requires a minimum 10 Gbps pipe and higher baseline costs.

Key Concept

Designing multi-region high-availability architectures with zero RPO data storage and appropriate hybrid connectivity scaling.
Question 1299Question →

A financial software provider is designing a new regional order-processing database on Google Cloud. The system requires standard SQL compliance, ACID transactional guarantees, and high availability across multiple zones within a single GCP region. The access patterns are typical operational OLTP queries, and the architecture team explicitly wants to avoid paying for unneeded multi-region global replication while keeping operational complexity low. Which Google Cloud database architecture should the cloud architect recommend?

Show answer & explanation

Answer: Deploy Cloud SQL for PostgreSQL configured with High Availability (regional failover instance in a secondary zone).

Answer

Cloud SQL for PostgreSQL configured with High Availability (regional failover instance in a secondary zone) is the optimal choice.
Cloud SQL for PostgreSQL with High Availability (HA) enabled provides automatic zonal failover within a single GCP region, full ACID transactional compliance, and standard SQL support without the high costs of multi-region database infrastructure.

Step-by-Step Solution

1
Analyze workload requirements
Workload needs standard SQL, ACID compliance, low-latency OLTP, single-region deployment, and zonal high availability.
Matching access patterns and geographical scope narrows down the viable GCP database options.
2
Evaluate Cloud SQL against requirements
Cloud SQL for PostgreSQL HA provides synchronous replication to a standby instance in a secondary zone within the same region, offering automatic failover and fully managed relational features.
Cloud SQL delivers regional HA at a cost-effective tier suitable for standard OLTP applications.
3
Eliminate over-provisioned and unsuitable services
Cloud Spanner is over-provisioned for single-region needs, BigQuery is an analytical store rather than an OLTP engine, and self-hosted databases increase operational burden.
Architectural best practice dictates choosing managed services that meet technical requirements without unnecessary cost.

Key Concept

Selecting Cloud Database Services Based on Scale, Consistency, and Region Scope
Question 1300Question →

A healthcare diagnostics company is building a high-availability infrastructure on Google Cloud to ingest and process high-resolution medical imaging scans from on-premises diagnostic centers. The sustained peak bandwidth requirement between the on-premises environment and Google Cloud is 8 Gbps8\text{ Gbps} with a mandatory 99.99%99.99\% availability Service Level Objective (SLO). The backend image processing pipeline runs memory-intensive image parsing workloads on Compute Engine virtual machines. Which TWO architectural solutions should you implement to satisfy both the high-availability hybrid networking and auto-scaling technical requirements? (Select TWO)

Select all that apply

Show answer & explanation

Answer: Establish redundant Cloud Dedicated Interconnect connections across two distinct edge availability domains for 99.99% availability.; Configure Compute Engine Managed Instance Group (MIG) autoscaling based on custom Cloud Monitoring metrics measuring memory utilization.

Answer

The correct architectural choices are establishing redundant Dedicated Interconnect connections across two edge availability domains and configuring Compute Engine Managed Instance Group autoscaling using custom Cloud Monitoring memory utilization metrics.
Dedicated Interconnect satisfies high-bandwidth demands (8 Gbps8\text{ Gbps}) that exceed single IPsec VPN tunnel limits, and deploying across dual edge availability domains delivers a 99.99%99.99\% availability SLA. Furthermore, memory-bound compute workloads require scaling rules tied to actual memory pressure via Cloud Monitoring custom metrics rather than CPU utilization.

Step-by-Step Solution

1
Evaluate hybrid bandwidth and availability requirements
Sustained bandwidth of 8 Gbps8\text{ Gbps} exceeds HA VPN single-tunnel limits (3 Gbps3\text{ Gbps} per tunnel). Dedicated Interconnect with links across two edge availability domains is required to support high throughput and achieve a 99.99%99.99\% uptime SLA.
HA VPN cannot natively scale to 8 Gbps on a single tunnel, whereas Dedicated Interconnect provides 10 Gbps or 100 Gbps pipes with 99.99% availability when deployed redundantly across edge domains.
2
Identify resource bottlenecks for compute autoscaling
The medical imaging parsing workload is memory-intensive rather than CPU-bound.
Autoscaling on CPU utilization will cause memory exhaustion errors before CPU thresholds trigger. Using Cloud Monitoring custom metrics for memory consumption ensures accurate auto-scaling behavior under load.

Key Concept

Designing High Availability Hybrid Networking and Metric-Specific Compute Scaling
Estimated Time:2m 0s
PreviousPage 65 / 80Next
All practice questions — Google Cloud Professional Cloud Architect | Examkin