All practice questions

1598 questions

Question 621Question

A multinational enterprise wants to implement real-time security threat detection and automated monitoring across its entire Google Cloud resource hierarchy. The security team needs to detect misconfigurations and suspicious activity (such as malware or unauthorized access) at scale without deploying or managing agents on individual virtual machines. Additionally, high-severity findings must trigger immediate notifications to an automated ticketing system. Which native Google Cloud architecture meets these requirements?

Show answer & explanation

Answer: Enable Security Command Center Premium at the organization level, utilize Built-in Services such as Event Threat Detection and Security Health Analytics, and configure Continuous Exports to a Cloud Pub/Sub topic for automated alerting.

Answer

Enable Security Command Center Premium at the organization level, utilize Built-in Services such as Event Threat Detection and Security Health Analytics, and configure Continuous Exports to a Cloud Pub/Sub topic for automated alerting.
Enabling Security Command Center (SCC) Premium at the organization tier delivers centralized, agentless threat detection (Event Threat Detection) and misconfiguration scanning (Security Health Analytics). Utilizing SCC's Continuous Export feature automatically streams finding notifications to a Cloud Pub/Sub topic, enabling real-time integration with automated ticketing and remediation pipelines.

Step-by-Step Solution

1
Identify the threat detection and asset configuration auditing requirements.
Real-time threat detection and security health monitoring are needed across the Google Cloud organization without installing third-party agents on compute instances.
Security Command Center (SCC) Premium provides agentless scanning and log monitoring capabilities (Security Health Analytics and Event Threat Detection) natively integrated with GCP.
2
Determine the mechanism for continuous automated notifications.
Findings generated by SCC Premium need to be streamed to downstream ticketing or alerting systems in real time.
SCC Continuous Export allows automatically publishing security findings directly to a Cloud Pub/Sub topic as they are generated.

Key Concept

Security Command Center Premium and Automated Finding Exports
Question 622Question

Match each enterprise security and compliance requirement on the left with the corresponding Google Cloud key management implementation on the right.

Click a left item, then click its matching right item

Items

The enterprise mandates strict key sovereignty where master encryption key material must permanently reside within an on-premises FIPS 140-2 Level 3 Hardware Security Module (HSM) outside Google Cloud, while permitting Cloud Storage and BigQuery to perform cryptographic operations via API calls.
A regulatory compliance framework requires passing a raw, customer-generated 256-bit AES encryption key in the header of each individual API call for Cloud Storage object operations, ensuring no key material or key metadata is persisted in Google Cloud after the request completes.
Internal security policies mandate customer control over key rotation schedules, destruction lifecycle, and IAM permission grants, while performing all cryptographic operations inside cloud-hosted, FIPS 140-2 Level 3 validated hardware security modules managed via Google Cloud APIs.
Standard baseline security policies require transparent data-at-rest encryption across all created storage resources with zero operational management overhead, requiring no custom IAM service account configuration or external cryptographic infrastructure.

Matches

Show answer & explanation

Answer

1. External key sovereignty with on-premises key residence maps to Cloud External Key Manager (Cloud EKM).
2. Raw key supplied per API request without persistence maps to Customer-Supplied Encryption Keys (CSEK).
3. Customer key lifecycle control using cloud-hosted FIPS 140-2 Level 3 hardware maps to Customer-Managed Encryption Keys (CMEK) using Cloud HSM.
4. Transparent zero-overhead automatic protection maps to Google-default Encryption.
Each requirement maps to its exact cryptographic boundary: Cloud EKM keeps keys in external on-premises HSMs; CSEK requires raw key material passed per API call without persistence; CMEK with Cloud HSM provides customer control over keys residing in Google Cloud FIPS 140-2 Level 3 HSMs; Google-default provides automated, zero-overhead encryption.

Step-by-Step Solution

1
Analyze key residency and external control requirements.
Matched key sovereignty requiring keys to remain outside Google Cloud infrastructure to Cloud External Key Manager (Cloud EKM).
Cloud EKM connects Cloud KMS with external partner HSMs or on-premises key managers so key material never enters Google Cloud.
2
Evaluate key delivery mechanisms per API request.
Matched raw key supply per request header to Customer-Supplied Encryption Keys (CSEK).
CSEK requires raw key material in each API call and bypasses Cloud KMS storage completely.
3
Identify cloud-native HSM key management requirements.
Matched customer key management with FIPS 140-2 Level 3 cloud compliance to CMEK using Cloud HSM.
Cloud HSM hosts customer keys in managed FIPS 140-2 Level 3 hardware modules integrated with Cloud KMS.
4
Determine default platform encryption capability.
Matched zero-overhead automatic encryption to Google-default Encryption.
All GCP data at rest is encrypted by default using Google-managed keys without user configuration.

Key Concept

Architectural selection between Google-default Encryption, Customer-Managed Encryption Keys (CMEK/Cloud HSM), Customer-Supplied Encryption Keys (CSEK), and Cloud External Key Manager (Cloud EKM) based on compliance and custody requirements.
Question 623Question

A multinational enterprise structures its Google Cloud environment under an Organization node with top-level folders named Operations and Workloads. The Workloads folder contains two subfolders: Production and Development. The central security compliance team requires continuous visibility to inspect configuration metadata for all Google Cloud resources across the entire company. Meanwhile, an automated deployment system operating from a Virtual Machine in the Operations folder must provision Compute Engine instances and attach pre-existing workload service accounts exclusively within projects in the Development subfolder. You need to design an IAM access control architecture that enforces the principle of least privilege while minimizing operational overhead. Which IAM role assignment strategy should you implement?

Show answer & explanation

Answer: Grant Cloud Asset Viewer (roles/cloudasset.viewer) to the compliance team at the Organization node. Grant Compute Instance Admin (v1) (roles/compute.instanceAdmin.v1) and Service Account User (roles/iam.serviceAccountUser) to the deployment automation service account at the Development folder level.

Answer

Grant Cloud Asset Viewer at the Organization level to the central compliance team, and grant Compute Instance Admin (v1) alongside Service Account User to the deployment automation service account bounded specifically at the Development folder level.
Assigning Cloud Asset Viewer at the Organization node provides complete resource metadata visibility across all descendant folders to meet audit requirements. Binding Compute Instance Admin (v1) and Service Account User directly on the Development folder enforces least privilege by restricting instance creation and service account attachment privileges strictly to the non-production workload environment.

Step-by-Step Solution

1
Analyze organization-wide auditing requirement
Identify that Cloud Asset Viewer (roles/cloudasset.viewer) assigned at the Organization node grants read-only access to asset metadata across all child folders and projects without exposing underlying resource payload data.
Auditing configuration metadata across an entire hierarchy requires organization-level scoping using specialized predefined roles.
2
Determine compute instance deployment and identity attachment permissions
Combine Compute Instance Admin (v1) for instance lifecycle management with Service Account User (roles/iam.serviceAccountUser) to bind pre-existing service accounts to VMs.
Creating a VM that runs as a specific service account requires both compute creation privileges and impersonation/usage rights over that identity.
3
Apply least privilege scope to the workload folder hierarchy
Bind the deployment permissions strictly to the Development subfolder node.
Inheritance flows down the resource tree. Placing the binding at the Development folder ensures no deployment capabilities leak into Production or Operations.

Key Concept

IAM Resource Hierarchy Inheritance and Fine-Grained Least Privilege Roles
Estimated Time:2m 30s
Question 624Question

An enterprise operating in the European Union must comply with data sovereignty regulations requiring all newly provisioned data storage resources, such as Cloud Storage buckets and BigQuery datasets, to reside strictly within EU regions. Which Google Cloud feature should the cloud architect configure to enforce this policy centrally across all projects in the organization?

Show answer & explanation

Answer: Define an Organization Policy with the Resource Locations constraint configured to allow only EU locations.

Answer

Define an Organization Policy using the Resource Locations constraint to limit resource creation strictly to specified EU regions.
Defining an Organization Policy with the Resource Locations constraint (`constraints/gcp.resourceLocations`) allows administrators to restrict the set of physical regions where location-based resources (such as Cloud Storage buckets and BigQuery datasets) can be created, ensuring strict compliance with data sovereignty regulations.

Step-by-Step Solution

1
Identify the primary compliance requirement.
The goal is to enforce data sovereignty by restricting resource creation locations across the Google Cloud organization hierarchy.
Data sovereignty mandates require strict geographic control over where data at rest resides.
2
Evaluate Google Cloud governance mechanisms for location enforcement.
The Resource Locations organization policy constraint (`constraints/gcp.resourceLocations`) defines the set of locations where location-based Google Cloud resources can be created.
Organization policies act as centralized guardrails that block unauthorized resource creation across projects.

Key Concept

Resource Location Restrictions via Organization Policies
Estimated Time:45s
Question 625Question

A smart logistics enterprise is migrating its central warehouse management system to Google Cloud. The architecture team must establish a highly available, encrypted hybrid network connection between their on-premises data center and a GCP Virtual Private Cloud (VPC). The connection must support automated route exchange via dynamic routing and meet SLA requirements for high availability (99.99% availability). Which TWO configuration steps are required on Google Cloud to achieve this setup?

Select all that apply

Show answer & explanation

Answer: Provision an High Availability (HA) Cloud VPN gateway in the target region with two active interfaces, creating two separate IPsec VPN tunnels to the on-premises VPN device.; Deploy a Cloud Router in the target region and establish dynamic BGP sessions for both IPsec tunnels associated with the HA VPN gateway.

Answer

To establish a highly available dynamic hybrid network connection with a 99.99% SLA using Cloud VPN, you must provision an HA Cloud VPN gateway with two active interfaces terminating two separate IPsec tunnels, and deploy a Cloud Router in the target region to configure dynamic BGP sessions for both tunnels.
Google Cloud HA VPN requires an HA VPN gateway containing two interfaces (Interface 0 and Interface 1) with two separate IPsec VPN tunnels connected to the on-premises peer. In addition, HA VPN requires a Cloud Router located in the same region to manage dynamic BGP routing across the dual tunnels, satisfying the 99.99% SLA commitment.

Step-by-Step Solution

1
Identify the high availability and routing requirements for the hybrid topology.
Requirements mandate 99.99% availability (HA VPN standard) and dynamic route discovery (BGP).
HA Cloud VPN is specifically designed for 99.99% SLA requirements and requires dynamic routing via Cloud Router.
2
Select the gateway topology that satisfies the 99.99% SLA.
An HA Cloud VPN gateway with two interfaces creating dual active IPsec tunnels is required.
Redundant interfaces and dual tunnels ensure active-active or active-passive fault tolerance.
3
Configure the routing mechanism for topology changes and failover.
Deploy a Cloud Router in the VPC region to run BGP sessions over both tunnels.
Cloud Router automatically updates routing tables dynamically when link failures or path changes occur.

Key Concept

HA Cloud VPN and Dynamic Routing with Cloud Router
Question 626Question

An enterprise is configuring its Google Cloud network topology to support multi-region workloads with strict security and network connectivity constraints. Workload instances deployed in private subnets must access Google Cloud APIs securely without requiring external IP addresses, and potential data exfiltration to external Cloud Storage buckets must be blocked using perimeter-level security controls rather than user IAM permissions alone. Furthermore, the architecture utilizes a hub-and-spoke topology across multiple VPC networks where direct communication between spoke VPCs is required. Which TWO network topology and configuration choices must the cloud architect implement to satisfy these requirements?

Select all that apply

Show answer & explanation

Answer: Enable Private Google Access on all internal subnets and configure a VPC Service Controls perimeter encompassing the workload projects to restrict API access boundaries.; Establish direct VPC Network Peering connections between any pair of spoke VPCs that require inter-spoke communication, rather than attempting to route traffic through the hub VPC.

Answer

The cloud architect must enable Private Google Access with VPC Service Controls for API routing and data exfiltration defense, and establish direct VPC Network Peering between spoke VPCs due to non-transitive VPC Peering rules.
Enabling Private Google Access on subnets permits private instances to reach Google services natively. Layering VPC Service Controls creates a security perimeter that prevents authorized credentials from exfiltrating data to external storage resources. Furthermore, because GCP VPC Network Peering is non-transitive, direct VPC Peering between spoke networks is necessary to enable communication between spokes.

Step-by-Step Solution

1
Analyze API access and data exfiltration requirements
Private Google Access provides IP routing to Google APIs for instances without external IPs, while VPC Service Controls provides perimeter isolation to prevent exfiltration to external resources.
IAM rules alone cannot prevent data copies to external buckets outside the organization perimeter.
2
Analyze inter-VPC spoke routing requirements
Direct VPC Peering between spokes must be configured.
Google Cloud VPC Network Peering is non-transitive, meaning VPC A peered to VPC B cannot reach VPC C peered to VPC B without direct peering between A and C.

Key Concept

VPC Network Peering Non-Transitivity and Private Access Perimeter Security
Estimated Time:2m 30s
Question 627Question

An enterprise cloud security team needs to encrypt data stored in a Cloud Storage bucket. Security compliance mandates that the enterprise must retain complete control over key lifecycle management, including key rotation and revocation using Google Cloud APIs, without the overhead of manually managing and supplying raw cryptographic keys for every data access request. Which encryption approach should the cloud architect recommend?

Show answer & explanation

Answer: Use Customer-Managed Encryption Keys (CMEK) stored in Cloud KMS.

Answer

Customer-Managed Encryption Keys (CMEK) stored in Cloud KMS.
Customer-Managed Encryption Keys (CMEK) via Cloud KMS allow organizations to maintain control over key creation, rotation, and revocation, while allowing Google Cloud services to automatically encrypt and decrypt data at rest.

Step-by-Step Solution

1
Identify key lifecycle control requirement
The requirement demands customer management of key generation, rotation, and revocation policies.
Google-default keys do not provide direct customer lifecycle management.
2
Evaluate operational burden constraints
The requirement specifies avoiding manual key transmission/supplying per API call.
Customer-Supplied Encryption Keys (CSEK) force the caller to manage raw keys and provide them with every operation, whereas Customer-Managed Encryption Keys (CMEK) integrate natively with Cloud KMS and GCP storage services.
3
Select the appropriate encryption key model
Cloud KMS CMEK satisfies customer control over key lifecycles without requiring raw key handling.
CMEK uses Cloud KMS to manage keys while GCP services handle data encryption seamlessly.

Key Concept

Customer-Managed Encryption Keys (CMEK) vs Customer-Supplied Encryption Keys (CSEK)
Estimated Time:45s
Question 628Question

A media streaming enterprise is provisioning infrastructure on Google Cloud for a new real-time video processing pipeline. The architecture requires deploying a private GKE cluster for processing microservices and a set of Compute Engine virtual machines for legacy media encoding. The security team mandates that the GKE control plane must not be accessible from the public internet and must restrict administrative access strictly to the company's internal management subnet. Additionally, automated deployment pipelines provisioning the virtual machines must use least-privilege identity management without granting administrative control over service accounts.

Which TWO actions should the Cloud Architect implement to satisfy these security and operational requirements?

Select all that apply

Show answer & explanation

Answer: Configure control plane authorized networks on the private GKE cluster to restrict master endpoint access to the internal management subnet range.; Grant the pipeline deployment service account the Service Account User role (roles/iam.serviceAccountUser) on the specific service account attached to the Compute Engine instances.

Answer

The correct configurations are restricting GKE master access via control plane authorized networks to the internal management subnet range and granting the Service Account User role (roles/iam.serviceAccountUser) on the target service account to the deployment pipeline.
Configuring control plane authorized networks ensures that administrative traffic to the GKE control plane is limited strictly to approved subnets such as the internal management subnet. Furthermore, assigning the Service Account User role to the deployment pipeline provides the exact least-privilege permission required to bind a service account to a Compute Engine virtual machine during provisioning.

Step-by-Step Solution

1
Evaluate GKE Control Plane Security Requirements
Creating a private cluster hides node IP addresses, but restricting master access to specific CIDR blocks requires configuring Control Plane Authorized Networks.
Control Plane Authorized Networks restrict access to the public or private cluster endpoint to authorized IP ranges.
2
Evaluate Compute Engine IAM Least Privilege Requirements
Provisioning VMs that attach specific service accounts requires the identity deploying the VM to possess the `roles/iam.serviceAccountUser` permission on the target service account.
This permission allows an identity to impersonate or run jobs under a service account without granting administrative powers like creating or deleting keys.

Key Concept

GKE Private Cluster Control Plane Access and Least-Privilege Compute IAM
Question 629Question

A global media streaming platform is configuring central security guardrails across its Google Cloud resource hierarchy. The security team has defined two mandatory policy enforcement rules: preventing developers from generating service account keys across all projects within the Media-Services folder, and restricting the creation of resources so that compute and storage services can only be deployed in designated European locations (europe-west1 and europe-west3). Which TWO configuration actions should the cloud architect take using Organization Policies to satisfy these guardrails?

Select all that apply

Show answer & explanation

Answer: Enforce the boolean constraint constraints/iam.disableServiceAccountKeyCreation on the Media-Services folder.; Apply the list constraint constraints/gcp.resourceLocations on the target hierarchy node, setting an allowed values list containing in:europe-west1-locations and in:europe-west3-locations.

Answer

The cloud architect should enforce the boolean constraint `constraints/iam.disableServiceAccountKeyCreation` on the target folder and apply the list constraint `constraints/gcp.resourceLocations` with allowed European location values.
Enforcing `constraints/iam.disableServiceAccountKeyCreation` at the folder level prevents key creation across all nested projects. Applying `constraints/gcp.resourceLocations` with allowed European region values restricts GCP resource deployment strictly to specified geographical regions.

Step-by-Step Solution

1
Identify the constraint type for blocking service account key creation.
Recognize that `constraints/iam.disableServiceAccountKeyCreation` is a boolean constraint designed specifically to stop users from creating service account keys.
Organization policies provide policy-based guardrails across the resource hierarchy, and boolean constraints evaluate to true (enforced) or false.
2
Identify the constraint type for restricting resource deployment locations.
Select `constraints/gcp.resourceLocations` as a list constraint with explicit allowed location values (`in:europe-west1-locations` and `in:europe-west3-locations`).
List constraints specify allowed or denied values for supported Google Cloud configuration parameters.

Key Concept

Organization Policies supply centralized governance by enforcing boolean and list constraints on resource creation and configuration across the GCP resource hierarchy.
Question 630Question

An enterprise organization is preparing to deploy an event-driven telemetry processing engine across multiple Compute Engine managed instance groups in the us-central1 and europe-west1 regions. During an architectural audit 48 hours prior to launch, the lead cloud architect determines that the required target capacity of 640 N2 vCPUs per region exceeds the project's default regional vCPU quota limit of 200 N2 vCPUs. The deployment will be managed automatically via an Infrastructure as Code (IaC) CI/CD pipeline using Terraform. Which proactive strategy should the architect implement to ensure the automated deployment completes successfully without resource allocation failures?

Show answer & explanation

Answer: Submit a proactive regional quota increase request for N2 vCPUs in both target regions via the Google Cloud Console or Cloud Quotas API before executing the Terraform pipeline.

Answer

Submitting a proactive regional quota increase request for N2 vCPUs in both target regions via the Google Cloud Console or Cloud Quotas API prior to pipeline execution is the correct solution.
Submitting a proactive regional quota increase request ensures that the necessary N2 vCPU capacity is reviewed and allocated by Google Cloud before the deployment pipeline executes. Quotas are project-level and regional constraints enforced by GCP; requesting an increase in advance prevents API errors during automated provisioning.

Step-by-Step Solution

1
Assess current regional quota limits against planned workload requirements.
Identified a gap where 640 N2 vCPUs are required per region, exceeding the current default limit of 200 N2 vCPUs.
Google Cloud enforces default quota limits on compute resources per region to prevent accidental over-provisioning.
2
Submit a quota increase request to Google Cloud for the affected regions in advance of deployment.
Google Cloud reviews and approves the quota increase, raising the limit to accommodate the workload.
Quota requests require processing time and must be approved before infrastructure deployment begins to prevent provisioning failures.
3
Trigger the automated Infrastructure as Code deployment pipeline.
Terraform successfully provisions all 640 N2 vCPUs without encountering quota capacity errors.
Sufficient regional quota is actively available in the target project and regions.

Key Concept

Proactive Service Quota Management and Planning
Question 631Question

A healthcare enterprise is building a hybrid cloud network to connect its primary on-premises electronic health record (EHR) data centers to a Google Cloud Virtual Private Cloud (VPC). The connection must support a sustained throughput of 20 Gbps, guarantee a 99.99% availability SLA, and provide dynamic failover using BGP across redundant physical paths. Which TWO architecture steps are required to achieve this configuration in accordance with Google Cloud best practices?

Select all that apply

Show answer & explanation

Answer: Provision four Dedicated Interconnect circuits deployed across two distinct Google Cloud edge availability domains (colocation facilities).; Configure two Cloud Routers in the target VPC network, establishing redundant BGP sessions for attachments in both edge locations.

Answer

To establish a 99.99% availability SLA for high-throughput hybrid connectivity, provision four Dedicated Interconnect circuits across two distinct colocation edge locations and configure two Cloud Routers in the VPC network to manage redundant BGP sessions.
The production SLA for 99.99% availability using Dedicated Interconnect mandates four physical circuits split equally across two different Google Cloud edge colocation facilities (availability domains). Furthermore, dynamic routing via Cloud Routers terminating BGP sessions across both facilities is required to handle automatic failover and load balancing.

Step-by-Step Solution

1
Determine the physical infrastructure configuration required for a 99.99% SLA.
Identify that 99.99% availability for Dedicated Interconnect requires 2 circuits in edge location 1 and 2 circuits in edge location 2 (4 total circuits).
This redundant design protects against device, link, and facility-level outages.
2
Select the dynamic routing mechanism for multi-circuit redundancy.
Provision Cloud Routers in the VPC network and create VLAN attachments mapped to each Interconnect link.
Cloud Routers dynamically announce and learn routes using BGP across the redundant physical paths.

Key Concept

99.99% SLA Dedicated Interconnect Topology
Estimated Time:2m 0s
Question 632Question

An enterprise is building an analytics platform on Google Cloud that ingests sensitive financial records into BigQuery and stores raw log archives on Compute Engine persistent disks. Security governance requires that all data at rest be protected using Customer-Managed Encryption Keys (CMEK) managed via Cloud KMS. The security policy mandates strict separation of duties, zero usage of primitive IAM roles, and automated key rotation where legacy data decryptability is preserved without requiring manual re-encryption of historical datasets. Which TWO architectural and IAM configurations must be implemented to fulfill these compliance requirements? (Select TWO)

Select all that apply

Show answer & explanation

Answer: Grant the Cloud KMS CryptoKey Encrypter/Decrypter role (roles/cloudkms.cryptoKeyEncrypterDecrypter) specifically to the Google-managed Service Agents for BigQuery and Compute Engine on the relevant KMS keys.; Configure an automated rotation schedule for the Cloud KMS symmetric encryption key; newly written data will automatically use the updated primary key version while older key versions remain enabled to decrypt historical data.

Answer

The enterprise must grant the Cloud KMS CryptoKey Encrypter/Decrypter role to the Google-managed Service Agents for BigQuery and Compute Engine, and configure an automated key rotation schedule on the Cloud KMS key.
To implement CMEK properly while following GCP security best practices, access to Cloud KMS keys must be granted to the specific Google-managed service agents (e.g., BigQuery service agent) using fine-grained predefined roles like `roles/cloudkms.cryptoKeyEncrypterDecrypter`. Furthermore, Cloud KMS key rotation creates a new primary key version for subsequent write operations while keeping older key versions active, allowing seamlessly transparent decryption of existing historical data without full re-encryption.

Step-by-Step Solution

1
Determine the appropriate key management model and IAM role assignment for GCP service integration.
CMEK requires granting roles/cloudkms.cryptoKeyEncrypterDecrypter to the service agent accounts of BigQuery and Compute Engine rather than using primitive project roles.
Primitive roles violate principle of least privilege and organizational security mandates.
2
Evaluate key rotation mechanisms under Cloud KMS CMEK.
Automated key rotation in Cloud KMS generates new primary key versions for encryption while retaining legacy key versions for decryption.
This allows historical data in BigQuery and persistent disks to remain accessible without requiring data re-encryption.

Key Concept

Cloud KMS Customer-Managed Encryption Keys (CMEK) IAM Service Agent permissions and automated key version rotation management.
Question 633Question

An organization is deploying an enterprise application requiring a relational database on Google Cloud to handle financial transactions across three continents. The transaction volume requires predictable low latency (<10 ms reads and writes) globally, automatic horizontal scaling without manual sharding, and strong serializable consistency. As a Principal Cloud Architect, which database provisioning strategy should you select to meet these technical requirements while minimizing operational maintenance?

Show answer & explanation

Answer: Provision a Cloud Spanner instance configured with a multi-region instance configuration spanning the required geographical regions.

Answer

Provision a Cloud Spanner instance configured with a multi-region instance configuration.
Cloud Spanner is the fully managed enterprise database service on Google Cloud engineered specifically for multi-region transactional workloads requiring strong (external) consistency, high availability, and automatic horizontal scaling without manual sharding.

Step-by-Step Solution

1
Analyze the technical requirements
Identified global distribution across three continents, strict serializable consistency for financial transactions, high write scalability without sharding, and minimal operational maintenance.
Relational transactions across multiple continents require true distributed ACID capabilities.
2
Evaluate GCP managed database offerings against requirements
Cloud Spanner is designed specifically for globally distributed relational workloads requiring strong consistency and automatic horizontal partitioning.
Cloud SQL lacks multi-region write scalability, while Bigtable is NoSQL and lacks multi-row ACID transactional semantics.

Key Concept

Selecting and provisioning globally consistent relational database services (Cloud Spanner vs Cloud SQL)
Question 634Question

During a technical review of an enterprise CI/CD pipeline, an organization discovers that manual configuration edits made directly in the Google Cloud Console are frequently causing deployment pipeline failures during Terraform runs. Which operational practice should the team integrate into their continuous integration pipeline to detect and analyze configuration drift before applying changes?

Show answer & explanation

Answer: Automate execution of infrastructure plan validation checks (such as running terraform plan) within the CI pipeline to compare current real-world state against desired state definitions.

Answer

Automate execution of infrastructure plan validation checks (such as running terraform plan) within the CI pipeline to compare current real-world state against desired state definitions.
Automating plan validation runs within the CI pipeline enables continuous detection of configuration drift by comparing the actual live cloud infrastructure state against the target definitions declared in version control.

Step-by-Step Solution

1
Analyze the problem scenario
Manual changes in the GCP Console create discrepancies (configuration drift) between actual infrastructure and IaC code definitions, breaking automated CI/CD deployments.
Understanding the root cause of pipeline failures is required to select the correct CI/CD analysis practice.
2
Evaluate IaC pipeline best practices for drift analysis
Executing a dry-run spec check (such as terraform plan) in CI reads actual resource states and compares them to committed code, highlighting drift before execution.
Continuous drift detection ensures visibility into out-of-band changes before pipeline execution.

Key Concept

Configuration Drift Detection in CI/CD Pipelines
Question 635Question

A financial analytics organization manages sensitive data across a multi-folder Google Cloud resource hierarchy. The chief information security officer requires aggregating all Data Access and Admin Activity audit logs across all current and future folders into a centralized log repository. Additionally, the security design must prevent insider threats where project administrators with high-privilege project permissions could copy or exfiltrate centralized audit records to an external, unapproved storage location. Which architectural strategy fulfills all security and compliance requirements?

Show answer & explanation

Answer: Define an organization-level aggregated Cloud Logging sink destination to a Cloud Storage bucket in a dedicated security project, and enclose both the source projects and the logging storage project inside a VPC Service Controls security perimeter.

Answer

Define an organization-level aggregated Cloud Logging sink destination to a Cloud Storage bucket in a dedicated security project, and enclose both the source projects and the logging storage project inside a VPC Service Controls security perimeter.
Combining an organization-level aggregated Cloud Logging sink with VPC Service Controls provides a comprehensive compliance and security architecture. The aggregated sink ensures continuous collection of all audit logs across current and future projects under the organization hierarchy. Enclosing the storage bucket and source projects within a VPC Service Controls perimeter isolates the API access layer, ensuring that even users with broad project IAM rights cannot exfiltrate log files to external Cloud Storage buckets located outside the secure perimeter.

Step-by-Step Solution

1
Configure Organization Aggregated Log Sink
Aggregates Admin Activity and Data Access audit logs automatically from all current and future projects into a dedicated centralized project destination.
Ensures complete coverage across the organizational hierarchy without manual project-by-project setup.
2
Implement VPC Service Controls Security Perimeter
Forms a boundary around Cloud Storage services containing audit logs and source project resources.
IAM permissions alone cannot prevent data exfiltration. VPC Service Controls blocks unauthorized API data movement across boundary limits, even for privileged identities.
3
Validate Least Privilege Service Account Access
Ensures log sink writer identity is only granted the necessary Storage Object Creator role on the destination bucket.
Follows security best practices by avoiding primitive IAM roles or broad administrative grants.

Key Concept

Centralized Organization Security Logging and VPC Service Controls Perimeter Data Exfiltration Prevention
Question 636Question

A national electrical utility company is designing a new cloud platform on Google Cloud to collect, analyze, and store smart meter data. The architectural plan defines three logical tiers: an Ingestion Tier for high-throughput time-series telemetry from 5 million meters, a Storage Tier split between high-volume time-series metrics and standard single-region relational customer billing metadata, and a Security Tier enforcing strict perimeter boundaries to prevent authorized internal users from exfiltrating sensitive telemetry to external storage locations. Which physical Google Cloud architecture best maps these logical tiers to meet all operational and security requirements?

Show answer & explanation

Answer: Ingest telemetry using Cloud Pub/Sub and Cloud Dataflow; store time-series metrics in Cloud Bigtable and billing metadata in Cloud SQL; enforce data exfiltration protection by configuring VPC Service Controls perimeters around the storage resources.

Answer

The optimal architecture uses Cloud Pub/Sub and Cloud Dataflow for ingestion, Cloud Bigtable for time-series metrics, Cloud SQL for single-region relational billing metadata, and VPC Service Controls to prevent data exfiltration.
The solution correctly maps each logical tier to optimal GCP physical resources: Cloud Pub/Sub and Dataflow provide fully managed stream ingestion and transformation; Cloud Bigtable handles high-throughput time-series writes; Cloud SQL satisfies single-region relational database demands cost-effectively; and VPC Service Controls establishes perimeter security to prevent data exfiltration.

Step-by-Step Solution

1
Analyze logical ingestion requirements
High-throughput streaming telemetry from millions of meters requires scalable event ingestion and stream processing, accurately provided by Cloud Pub/Sub and Cloud Dataflow.
Managed streaming services scale automatically without infrastructure maintenance.
2
Evaluate logical storage requirements for telemetry and billing data
Time-series data requires high-write throughput (Cloud Bigtable), while single-region relational billing data requires standard SQL (Cloud SQL).
Cloud Spanner is unnecessary for single-region relational databases and adds unnecessary cost and complexity.
3
Map security and perimeter exfiltration requirements to physical GCP controls
VPC Service Controls establishes security perimeters around Google Cloud APIs and storage services to block data exfiltration.
IAM alone cannot prevent authorized users from copying data outside the security perimeter.

Key Concept

Translating Conceptual and Logical Tiers into Physical GCP Solution Architectures
Question 637Question

A global healthcare SaaS provider processing protected citizen health records for an Asia-Pacific government entity must comply with strict national data sovereignty regulations and audit requirements. The compliance mandate specifies three requirements:
1. All underlying storage data at rest and cryptographic key management boundaries must be restricted to a single specified GCP region.
2. Google support personnel must be explicitly authorized prior to viewing any customer data during administrative operations, with all access attempts fully audited.
3. Authorized service accounts and insider identities within the project must be programmatically blocked from exfiltrating sensitive datasets to unauthorized external Google Cloud Storage buckets.

Which THREE architectural controls must be implemented in Google Cloud to satisfy these compliance and data governance requirements?

Select all that apply

Show answer & explanation

Answer: Enforce the Resource Locations organization policy (constraints/gcp.resourceLocations) at the folder level restricting resource creation to the target region, and use Customer-Managed Encryption Keys (CMEK) hosted on Cloud KMS key rings provisioned within that same region.; Enable Access Approval and Access Transparency at the organization level to require explicit customer approval before Google engineers access data and to maintain immutable audit logs of support actions.; Construct a VPC Service Controls perimeter around sensitive resources (such as Cloud Storage and BigQuery) to prevent data copying or exfiltration to projects outside the perimeter.

Answer

The three required controls are: (1) Enforcing the Resource Locations organization policy paired with regional Customer-Managed Encryption Keys (CMEK), (2) Enabling Access Approval and Access Transparency for Google staff operations, and (3) Constructing a VPC Service Controls perimeter to protect against data exfiltration.
To satisfy comprehensive data sovereignty, data governance, and compliance mandates, three distinct controls must be combined. First, enforcing the Resource Locations organization policy alongside regionally configured CMEK ensures data and keys never leave the designated sovereign region. Second, combining Access Approval with Access Transparency gives the enterprise explicit control over and audit visibility into Google support staff access. Third, establishing a VPC Service Controls perimeter isolates sensitive resources like Cloud Storage and BigQuery, preventing exfiltration even by compromised or malicious internal identities.

Step-by-Step Solution

1
Address data residency and cryptographic key boundary requirements.
Applying the `constraints/gcp.resourceLocations` organization policy restricts data storage and compute resource creation to the target region. Using Cloud KMS CMEK with key rings created in that exact region ensures encryption keys remain within the sovereign boundary.
This directly guarantees both data at rest and cryptographic operations comply with national residency laws.
2
Address administrative access control and visibility over Google personnel.
Enabling Access Approval ensures that any administrative intervention requested by Google support requires customer consent. Access Transparency generates audit logs detailing Google personnel access.
This satisfies legal requirements regarding administrative vendor oversight and data access auditing.
3
Address insider threat and data exfiltration protection.
Configuring VPC Service Controls around storage and analytics services creates a perimeter boundary that blocks authorized identities from transferring data to GCP projects outside the perimeter.
IAM alone cannot prevent an authorized user or service account from copying data to an external bucket.

Key Concept

Multi-Layered Sovereign Compliance Architecture
Question 638Question

A bio-informatics platform processes sensitive clinical datasets across multiple Google Cloud projects contained within a single dedicated folder named Genomics-Prod. To ensure compliance, an external audit identity requires access to review all IAM policy bindings and resource configurations across all projects within Genomics-Prod without being able to read underlying storage object data or modify permissions. Additionally, development teams need permission to attach specific workload service accounts to Compute Engine instances without being allowed to modify service account permissions or create new service accounts. Which IAM role assignment strategy satisfies these requirements while strictly adhering to the principle of least privilege?

Show answer & explanation

Answer: Grant the roles/iam.securityReviewer role to the audit identity at the Genomics-Prod folder level, and grant developers the roles/iam.serviceAccountUser role on the specific workload service accounts.

Answer

Grant the roles/iam.securityReviewer role to the audit identity at the Genomics-Prod folder level, and grant developers the roles/iam.serviceAccountUser role on the specific workload service accounts.
Assigning roles/iam.securityReviewer at the Genomics-Prod folder level ensures inherited compliance visibility across all sub-projects without providing access to read bucket payload data. Granting roles/iam.serviceAccountUser specifically on the target workload service accounts enforces least privilege, allowing developers to attach approved service accounts to instances without elevating their administrative control over service accounts.

Step-by-Step Solution

1
Evaluate the auditing requirement across the resource hierarchy.
Assigning roles/iam.securityReviewer at the folder level allows reading IAM policies and asset metadata for all descendant projects without granting read access to underlying data objects.
Folder-level IAM bindings inherit downwards, satisfying the requirement to cover all projects under Genomics-Prod with minimum operational overhead.
2
Evaluate developer access requirements for service account utilization.
Granting roles/iam.serviceAccountUser at the individual service account resource level allows developers to attach the service account to instances.
Scoping roles/iam.serviceAccountUser to individual service accounts prevents developers from impersonating unapproved service accounts or gaining administrative privileges over IAM policies.

Key Concept

Resource hierarchy inheritance and predefined fine-grained IAM roles for security auditing and service account usage
Question 639Question

A multinational financial institution operating in the European Union is migrating a mission-critical workload to Google Cloud. To satisfy strict regulatory compliance mandates regarding EU data sovereignty and data governance, the lead architect must design a solution that satisfies the following four requirements:
1. All data stored in Cloud Storage and BigQuery must be restricted exclusively to EU multi-regions or EU sub-regions.
2. Cryptographic keys used for encryption at rest must be managed by the customer within an EU location, and Google personnel access to customer data or key material must require explicit prior customer approval and full auditability.
3. Authorized internal service accounts and users must be prevented from exfiltrating data to external Cloud Storage buckets outside the organization's boundary.

Which architectural combination of Google Cloud security and governance controls fulfills all specified regulatory requirements?

Show answer & explanation

Answer: Configure an Organization Policy with the Resource Locations constraint restricting deployments to EU locations, encrypt storage resources using Customer-Managed Encryption Keys (CMEK) located in EU key rings, enable Access Approval and Access Transparency, and enforce a VPC Service Controls perimeter around the workload projects.

Answer

The correct architecture uses an Organization Policy with the Resource Locations constraint restricted to EU regions, Cloud KMS Customer-Managed Encryption Keys (CMEK) hosted in EU key rings, Access Approval paired with Access Transparency for Google administrator access governance, and VPC Service Controls perimeters to prevent data exfiltration.
The correct solution integrates four vital GCP security primitives to meet comprehensive sovereignty and compliance rules: (1) Organization Policy resource location constraints (`constraints/gcp.resourceLocations`) block resource provisioning outside designated EU locations; (2) CMEK hosted in EU Cloud KMS key rings ensures customer-managed key lifecycle governance; (3) Access Approval and Access Transparency ensure Google support personnel cannot access underlying data without explicit approval and audited records; and (4) VPC Service Controls perimeters isolate Google Cloud API traffic, blocking data exfiltration even if an identity possesses valid IAM permissions.

Step-by-Step Solution

1
Enforce strict physical data residency boundaries
Apply the Organization Policy constraint `constraints/gcp.resourceLocations` set to `in:eu-locations` across the resource hierarchy.
This guarantees that no user or automated process can instantiate compute or storage resources outside of European Union regions.
2
Establish key governance and administrative access controls
Deploy Customer-Managed Encryption Keys (CMEK) within EU Cloud KMS key rings, and enable Access Approval alongside Access Transparency.
CMEK ensures customer control over key rotation and location, while Access Approval requires explicit authorization before Google personnel can access data for support tickets, creating cryptographic and operational sovereignty.
3
Prevent data exfiltration vectors
Construct a VPC Service Controls security perimeter around the projects containing Cloud Storage and BigQuery.
IAM alone cannot prevent an authorized identity from reading sensitive data and writing it to an unmanaged bucket outside the organization. VPC Service Controls restrict service API communication based on network boundaries.

Key Concept

Regulatory Compliance, Data Sovereignty, and Data Governance in Google Cloud
Question 640Question

A multinational logistics company plans to migrate its legacy logistics infrastructure to Google Cloud within a strict 3-week cutover window. The workload consists of a 500 TB500\text{ TB} unencrypted historical shipment tracking log archive and a 2 TB2\text{ TB} operational PostgreSQL database. The on-premises facility connects to the internet via a dedicated 100 Mbps100\text{ Mbps} network link. The solution must minimize operational downtime for the transactional workload while meeting the migration deadline. Which TWO migration and data transfer strategies should the cloud architect recommend?

Select all that apply

Show answer & explanation

Answer: Order a Google Cloud Transfer Appliance to securely transfer the 500 TB500\text{ TB} archival dataset offline into Cloud Storage.; Use Database Migration Service (DMS) with continuous replication to migrate the 2 TB2\text{ TB} operational PostgreSQL database to Cloud SQL for PostgreSQL.

Answer

The cloud architect should recommend ordering a Google Cloud Transfer Appliance for the 500 TB archival dataset and using Database Migration Service (DMS) with continuous replication for the 2 TB operational PostgreSQL database.
For the 500 TB500\text{ TB} archival dataset, network transfer over 100 Mbps100\text{ Mbps} is mathematically impractical within 3 weeks; using a Transfer Appliance allows physical offline shipment of data. For the 2 TB2\text{ TB} operational PostgreSQL database, Database Migration Service provides native continuous replication to Cloud SQL with minimal cutover downtime.

Step-by-Step Solution

1
Calculate network throughput for bulk archival transfer
Transferring 500 TB500\text{ TB} (4×1015 bits4 \times 10^{15}\text{ bits}) over a 100 Mbps100\text{ Mbps} network connection requires approximately 40,000,000 seconds40,000,000\text{ seconds} (over 460 days), which fails the 3-week constraint.
Offline transfer via Cloud Transfer Appliance is necessary to meet the 3-week deadline.
2
Evaluate database migration requirements for continuous availability
Database Migration Service (DMS) continuously replicates CDC (Change Data Capture) changes from on-premises PostgreSQL to Cloud SQL.
DMS ensures minimal downtime cutover for transactional database workloads.

Key Concept

Designing hybrid data transfer strategies based on dataset size, network bandwidth calculations, and database replication tools.
PreviousPage 32 / 80Next
All practice questions — Google Cloud Professional Cloud Architect | Examkin