All practice questions

1598 questions

Question 681Question

An automotive technology company is setting up Google Cloud compute infrastructure to process real-time telemetry streams from connected vehicles. The architecture requires provisioning a Google Kubernetes Engine (GKE) cluster to run containerized microservices that write processed metrics to BigQuery and Cloud Storage. Corporate security policies require that the cluster control plane is secured against unrestricted public internet access while allowing management access from designated corporate CIDR blocks, and that container pods authenticate to Google Cloud APIs using fine-grained, least-privilege IAM roles without relying on exported long-lived service account keys. Which deployment approach meets these requirements?

Show answer & explanation

Answer: Provision a private GKE cluster with Control Plane Authorized Networks restricted to corporate IP ranges, and enable Workload Identity to bind Kubernetes service accounts to dedicated IAM service accounts.

Answer

Provisioning a private GKE cluster with Control Plane Authorized Networks configured for corporate IP ranges, combined with Workload Identity for pod-level IAM authentication, satisfies all security and connectivity requirements.
The correct recommendation is to provision a private GKE cluster configured with Control Plane Authorized Networks and Workload Identity. Control Plane Authorized Networks restrict public endpoint access strictly to designated corporate CIDRs, satisfying network isolation rules. Workload Identity securely binds Kubernetes service accounts used by microservices directly to fine-grained IAM service accounts, eliminating key management overhead and fulfilling least-privilege requirements.

Step-by-Step Solution

1
Analyze security boundaries for GKE control plane access.
Enabling Control Plane Authorized Networks ensures that only specified corporate IP ranges can communicate with the Kubernetes API server endpoint.
Prevents unauthorized internet traffic from reaching the cluster management plane.
2
Configure pod identity management using Google Cloud best practices.
Enabling Workload Identity maps Kubernetes service accounts (KSAs) to Google IAM service accounts (GSAs).
Allows containerized microservices to securely access BigQuery and Cloud Storage with fine-grained IAM roles without managing exported JSON keys.

Key Concept

GKE Private Cluster Security and Workload Identity Provisioning
Question 682Question

A cloud architect is establishing a secure provisioning workflow to deploy a multi-cluster Cloud Bigtable database for processing real-time trade data. The database must use Customer-Managed Encryption Keys (CMEK) and be accessible only via private network endpoints. In what order should the architect execute these steps to ensure all security and resource dependencies are satisfied?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct execution sequence is: First, create the Cloud KMS CryptoKey and grant the Cloud Bigtable Service Agent the CryptoKey Encrypter/Decrypter IAM role. Second, configure the VPC network with Private Google Access and Private Services Access IP allocation. Third, provision the Cloud Bigtable instance and clusters referencing the CMEK key. Fourth, create the Bigtable tables and configure column families. Fifth, grant the application service account the Bigtable User IAM role on the target table resources.
Provisioning GCP database infrastructure requires strict adherence to cryptographic and network dependency chains. First, the Cloud KMS key must exist and explicit encrypter/decrypter rights must be granted to the GCP service account for Bigtable. Second, the VPC networking layer and Private Services Access IP allocation must be ready. Third, the Bigtable instance is deployed using the CMEK key and network bindings. Fourth, once the instance is active, table structures and column families are created. Finally, identity permissions (such as Bigtable User) are applied to the application service account for the specific table resources.

Step-by-Step Solution

1
Provision Cloud KMS Key and bind Service Agent IAM role
Cloud Bigtable Service Agent (service-[PROJECT_NUM]@gcp-sa-bigtable.iam.gserviceaccount.com) has cryptographic permissions to wrap/unwrap data keys.
Google Cloud service APIs validate CMEK key permissions during instance instantiation; missing IAM bindings cause immediate deployment failure.
2
Configure VPC Networking and Private Services Access
VPC network contains allocated IP ranges and peered private connection endpoints.
Private network paths and IP ranges must be established prior to creating instance clusters bound to private VPC subnets.
3
Deploy Cloud Bigtable Instance and Regional Clusters
Active Cloud Bigtable instance with storage clusters encrypted using the specified CMEK key.
The parent managed instance resource must be fully initialized before child schema objects can be instantiated.
4
Instantiate Table Schema and Column Families
Tables and column family definitions with garbage collection rules exist inside the instance.
Schema definitions exist within the logical scope of an initialized Bigtable instance.
5
Bind Application Identity IAM Access
Application service account is authorized to perform data-plane reads and writes on specific tables.
Fine-grained IAM policy bindings at the table level require target table resource paths to exist in GCP IAM.

Key Concept

Dependency-Aware Provisioning Workflow for Encrypted GCP Storage
Question 683Question

A biomedical research enterprise needs to execute high-throughput genomic processing jobs on Google Cloud. The workload consists of non-HTTP containerized batch tasks that run between 15 and 45 minutes per execution, require GPU acceleration for parallel processing, and run unpredictably based on daily research submissions. The architecture team must select compute platforms that minimize operational management overhead while ensuring zero cost incurred when no jobs are executing. Which TWO compute architecture deployment strategies fulfill these requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Execute the containerized tasks using Cloud Batch configured with GPU-attached Spot VM instances that scale down to zero upon job completion.; Deploy the processing workloads as Cloud Run jobs configured with GPU allocation and scale-to-zero execution limits.

Answer

The optimal strategies are deploying the containerized workloads using Cloud Batch with GPU-attached Spot VMs and utilizing Cloud Run jobs configured with GPU resources.
For non-HTTP containerized workloads that run intermittently and require GPU acceleration, fully managed job-based serverless architectures such as Cloud Batch (with Spot VMs) and Cloud Run jobs offer optimal serverless execution. Both options eliminate baseline infrastructure costs by scaling down to zero when idle while taking on all infrastructure lifecycle management.

Step-by-Step Solution

1
Analyze workload operational parameters and scaling requirements.
The workload is non-HTTP batch processing, GPU-dependent, long-running (15-45 minutes), and highly intermittent.
Serverless container options or dedicated batch schedulers that scale to zero and support GPUs are required to prevent paying for idle infrastructure.
2
Evaluate Google Cloud managed compute platforms against operational overhead limits.
Cloud Batch and Cloud Run jobs provide fully managed, serverless execution models for batch containers with native GPU support and zero baseline cost.
Both services manage underlying infrastructure lifecycles automatically, removing cluster administration tasks.
3
Eliminate options that introduce management overhead, idle cost, or improper scaling metrics.
Discard permanent GKE cluster setups, long-term CUD commitments for variable workloads, and CPU-only MIG autoscaling.
These alternatives increase operational complexity and introduce cost misallocations or improper autoscaling triggers.

Key Concept

Selecting Serverless Compute and Managed Batch Platforms for Intermittent GPU Workloads
Question 684Question

An enterprise financial institution is designing a zero-trust container pipeline and runtime protection architecture on Google Cloud for their mission-critical Google Kubernetes Engine (GKE) clusters. The security policy mandates three operational requirements:

1. Container images stored in Artifact Registry must be automatically analyzed for software vulnerabilities.
2. Only container images verified with cryptographic attestations created during the CI/CD pipeline can be deployed to GKE clusters.
3. Runtime security monitoring must analyze GKE node telemetry and audit streams to detect suspicious container executions, shell spawns, and anomaly events without requiring third-party agent deployments inside individual pods.

Which TWO architectural components must the Cloud Architect integrate to fulfill these security requirements? (Select TWO options.)

Select all that apply

Show answer & explanation

Answer: Enable Container Analysis continuous scanning on Artifact Registry and configure GKE Binary Authorization to enforce deploy-time policy evaluation using Cloud KMS-signed attestations.; Enable Security Command Center Premium to leverage Container Threat Detection and Event Threat Detection for agentless runtime monitoring of GKE nodes and GCP audit logs.

Answer

The architecture requires enabling Container Analysis continuous scanning paired with GKE Binary Authorization using Cloud KMS attestations, as well as enabling Security Command Center Premium for Container Threat Detection and Event Threat Detection.
Combining Container Analysis continuous scanning with GKE Binary Authorization guarantees that container images are scanned and cryptographically validated prior to execution. Concurrently, Security Command Center Premium provides native, agentless runtime threat detection across both GKE nodes (via Container Threat Detection) and GCP log streams (via Event Threat Detection).

Step-by-Step Solution

1
Evaluate vulnerability scanning and deploy-time governance requirements.
Artifact Registry vulnerability scanning is natively managed by Container Analysis. To ensure only signed binaries are deployed, GKE Binary Authorization acts as an admission controller enforcing signed attestations backed by Cloud KMS key pairs.
This establishes a cryptographic chain of trust from build to deployment.
2
Evaluate agentless runtime threat detection requirements.
Security Command Center (SCC) Premium includes Container Threat Detection, which monitors GKE node kernel telemetry, and Event Threat Detection, which analyzes Cloud Audit Logs.
These capabilities operate natively at the GCP infrastructure layer without requiring third-party pod agents or custom daemonsets.
3
Analyze distractor configurations against security governance boundaries.
Granting primitive Owner roles introduces massive security vulnerabilities, and relying on Container Analysis IAM to block network egress misunderstands the distinction between API identity authorization and network perimeter/data exfiltration controls.
IAM permissions control control-plane access, whereas VPC Service Controls and firewalls regulate network data movement.

Key Concept

Multi-layered container security incorporating automated image vulnerability scanning, Binary Authorization attestations, and agentless runtime threat detection using Security Command Center Premium.
Question 685Question

A cloud security architect needs to implement continuous container image security for an enterprise application. The requirement is to automatically inspect container images for known software vulnerabilities immediately after they are pushed to Google Artifact Registry. Which Google Cloud solution fulfills this requirement with minimal operational overhead?

Show answer & explanation

Answer: Enable automatic vulnerability scanning in Artifact Registry using Container Analysis.

Answer

Enable automatic vulnerability scanning in Artifact Registry using Container Analysis.
Enabling automatic vulnerability scanning in Artifact Registry leverages Container Analysis, which automatically scans container images for software vulnerabilities when they are uploaded. This provides continuous threat management with zero management overhead.

Step-by-Step Solution

1
Identify the core requirement for automated vulnerability scanning upon pushing container images.
Recognize that a native Google Cloud container analysis tool is required.
The system must continuously and automatically scan images for CVEs without custom scripts or excessive administrative privileges.
2
Evaluate Google Cloud container security services integrated with Artifact Registry.
Select Container Analysis vulnerability scanning.
Container Analysis integrates natively with Artifact Registry to perform automated vulnerability scanning on pushed container images.

Key Concept

Automated Container Vulnerability Scanning in Google Cloud
Question 686Question

An enterprise security team must ensure that authorized users inside an organization cannot exfiltrate sensitive data from Google Cloud Storage buckets into external, unauthorized projects. Which Google Cloud feature should the architecture team implement to establish a security perimeter around these managed service resources?

Show answer & explanation

Answer: VPC Service Controls

Answer

VPC Service Controls
VPC Service Controls enable organizations to construct a perimeter around managed Google Cloud services such as Cloud Storage. This prevents data exfiltration by restricting API calls to authorized services and projects inside the perimeter.

Step-by-Step Solution

1
Identify the primary security requirement
The goal is to prevent data exfiltration from Google Cloud Storage by authorized users to external storage locations.
Standard IAM permissions grant resource access to users, but do not prevent authorized users from copying data outside corporate perimeter boundaries.
2
Evaluate perimeter security services in Google Cloud
VPC Service Controls isolate Google Cloud service APIs (like Cloud Storage) within a configured service perimeter.
VPC Service Controls block data exfiltration by restricting network access to specified Google Cloud services based on caller context and target destination.

Key Concept

VPC Service Controls Service Perimeters
Question 687Question

A media streaming company structures its Google Cloud resource hierarchy into an Organization node with environment folders, including a dedicated Production-Workloads folder and a separate Tools-and-CI project. An automated CI/CD pipeline running on a Compute Engine instance in the Tools-and-CI project uses a dedicated deployment Service Account to manage application compute instances inside projects under the Production-Workloads folder. Developers need to trigger builds that execute deployment tasks through this pipeline, but security governance requires enforcing least privilege while preventing developers from altering the deployment Service Account policy or accessing production instances directly. How should IAM roles and resource hierarchy bindings be configured to meet these requirements?

Show answer & explanation

Answer: Grant the Compute Instance Admin (v1) role to the deployment Service Account at the Production-Workloads folder level, and grant the Service Account User role on the deployment Service Account to the developer group at the Tools-and-CI project level.

Answer

Granting the Compute Instance Admin (v1) role to the deployment Service Account at the Production-Workloads folder level, and granting the Service Account User role on the deployment Service Account to the developer group at the Tools-and-CI project level.
The solution granting Compute Instance Admin (v1) at the folder level and Service Account User on the target service account enforces strict least privilege. The deployment service account receives specific compute privileges inherited by all projects in the target folder, while developers receive only the permission to run jobs under the service account identity without gaining administrative power over the service account itself.

Step-by-Step Solution

1
Determine appropriate resource hierarchy scoping for compute workload management.
Binding the predefined role roles/compute.instanceAdmin.v1 at the Production-Workloads folder level ensures all current and future projects under that folder inherit permissions to manage compute instances without granting global organization access.
IAM roles applied at a folder node propagate down to all contained project resources via hierarchy inheritance.
2
Select the minimal IAM role required for developers to deploy workloads via the Service Account.
Developers require roles/iam.serviceAccountUser on the deployment Service Account to attach or act as the identity during pipeline execution.
The Service Account User role grants permission to use a service account for compute workloads without giving administrative permissions to edit keys, policies, or service account configurations.
3
Verify least privilege and operational security constraints.
Developers cannot directly SSH into production compute instances or alter service account security settings, satisfying security compliance.
Service Account User permissions are scoped strictly to impersonation/usage within the build project.

Key Concept

IAM resource hierarchy inheritance and Service Account User delegation
Question 688Question

An enterprise organization is deploying a centralized Shared VPC topology in Google Cloud to connect multiple application service projects with an on-premises environment via Dedicated Interconnect. The architecture must enable a third-party partner organization to securely consume an internal microservice hosted in one of the service projects, while strictly preventing the partner from accessing the on-premises network over the hybrid connection. Additionally, on-premises systems require reliable access to subnets in the service projects. Which TWO network topology configurations should the Cloud Architect implement? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Publish the internal microservice using a Private Service Connect (PSC) Service Attachment in the producer VPC and configure consumer endpoints in the partner VPC.; Configure Cloud Routers in the Shared VPC host project to use custom route advertisements for advertising Shared VPC subnet IP ranges to on-premises routers over BGP.

Answer

The optimal configuration involves publishing the service using Private Service Connect service attachments for partner access and configuring Cloud Router custom route advertisements in the Shared VPC host project for hybrid connectivity.
Publishing the internal microservice via Private Service Connect allows the partner organization to privately reach the application endpoint using IP addresses in their own VPC, preventing any direct network peering or access to the on-premises Interconnect. Concurrently, configuring custom route advertisements on Cloud Routers in the Shared VPC host project ensures that on-premises devices receive BGP routes to all subnets across the host and service projects.

Step-by-Step Solution

1
Analyze partner service access requirement without transit risk
Private Service Connect allows unidirectional, service-level private access across organization boundaries without creating transitive network paths to on-premises environments.
VPC Peering would fail due to non-transitivity and would expose broader network visibility than intended.
2
Configure dynamic hybrid routing for Shared VPC subnets
Cloud Routers established in the host project advertise subnets belonging to service projects using BGP custom route advertisements.
On-premises routers require explicit BGP advertisements to route traffic directly to GCP service subnets over Dedicated Interconnect.

Key Concept

Shared VPC hybrid routing with Dedicated Interconnect and Private Service Connect service publishing
Question 689Question

A financial enterprise processes sensitive analytical records in BigQuery and archives raw log files in Cloud Storage. Enterprise compliance guidelines specify three mandatory controls:
1. Key Management: Data at rest must be encrypted using Customer-Managed Encryption Keys (CMEK) managed via Cloud KMS to support automated key rotation.
2. Access Governance: Key access must follow the principle of least privilege using predefined IAM roles assigned to dedicated service agents without granting administrative privileges.
3. Perimeter Protection: Data exfiltration must be strictly prevented so that authorized identity credentials cannot copy data to external Cloud Storage buckets outside the organizational boundary.

Which TWO configurations must the security architect implement to fulfill these compliance requirements?

Select all that apply

Show answer & explanation

Answer: Grant the Cloud KMS CryptoKey Encrypter/Decrypter role on the Cloud KMS key to the service agents for Cloud Storage and BigQuery.; Configure a VPC Service Controls security perimeter that encompasses the BigQuery and Cloud Storage projects.

Answer

The architect must grant the Cloud KMS CryptoKey Encrypter/Decrypter role to the BigQuery and Cloud Storage service agents and configure a VPC Service Controls security perimeter around the projects.
To satisfy CMEK requirements under least privilege, GCP service agents (such as service-PROJECT_NUMBER@gs-project-accounts.iam.gserviceaccount.com) must be granted the dedicated predefined role `roles/cloudkms.cryptoKeyEncrypterDecrypter` on the key. Additionally, guarding against data exfiltration even when users hold valid IAM privileges requires a network-level boundary via VPC Service Controls surrounding the storage and analytics services.

Step-by-Step Solution

1
Identify the key management and service access requirements for CMEK.
Cloud Storage and BigQuery require key usage permissions through their respective service agents (service accounts managed by Google Cloud).
Granting the predefined Cloud KMS CryptoKey Encrypter/Decrypter role directly to the service agents ensures cryptographic operations succeed while following least privilege.
2
Address the data exfiltration prevention requirement.
Deploying VPC Service Controls perimeters restricts egress of data across GCP API boundaries.
IAM permissions control WHO has access, whereas VPC Service Controls enforce WHERE data can go, preventing authorized users from copying data outside the perimeter.

Key Concept

Cloud KMS CMEK integration with GCP Service Agents and exfiltration defense via VPC Service Controls
Question 690Question

An organization is deploying an internal analytics service in a Producer VPC behind an Internal HTTP(S) Load Balancer. Multiple independent consumer projects with overlapping IP address spaces require secure, private access to this analytics API without enabling full IP routing or VPC Network Peering between the consumer VPCs. Which TWO network topology configurations must you implement to establish this connectivity?

Select all that apply

Show answer & explanation

Answer: Create a Service Attachment in the Producer VPC that references the Internal HTTP(S) Load Balancer's forwarding rule.; Provision a Private Service Connect (PSC) endpoint in each Consumer VPC that targets the published Service Attachment URI.

Answer

To allow consumer VPCs with overlapping IP address ranges to securely access an internal service in a producer VPC without establishing VPC Network Peering or IP routing, you must create a Service Attachment pointing to the Producer VPC's Internal HTTP(S) Load Balancer forwarding rule, and deploy a Private Service Connect (PSC) endpoint in each Consumer VPC targeting the URI of that Service Attachment.
Private Service Connect allows private consumption of services across GCP projects even when VPCs have overlapping IP address spaces. Creating a Service Attachment in the producer VPC exposes the internal load balancer's forwarding rule via a NAT subnet. Provisioning a Private Service Connect endpoint in the consumer VPC allocates an internal IP address within the consumer's local subnet, establishing one-way private connectivity to the producer service.

Step-by-Step Solution

1
Identify connectivity constraints across VPC boundaries
Recognize that overlapping IP space and isolation requirements preclude using VPC Network Peering or direct IP routing.
VPC Network Peering requires non-overlapping IP ranges and does not support transitive routing.
2
Publish the internal service in the producer VPC
Configure a Private Service Connect Service Attachment referencing the Producer VPC's internal load balancer forwarding rule and designated NAT subnet.
The Service Attachment acts as the published gateway that consumer endpoints connect to.
3
Consume the published service from consumer VPCs
Provision a Private Service Connect endpoint in each Consumer VPC using an IP address from the consumer's own local subnet targeting the Service Attachment URI.
This translates consumer traffic locally to the producer service via NAT without exposing consumer IP addresses or establishing network peering.

Key Concept

Private Service Connect (PSC) for Published Services
Question 691Question

A multinational financial services enterprise operating in South America must host its payment processing workloads and financial transaction archives on Google Cloud while complying with strict central bank data sovereignty mandates and regulatory audit requirements. The compliance framework dictates that all data and primary infrastructure must remain geographically restricted to the São Paulo region, and any emergency administrative access by cloud provider support personnel must require explicit, real-time approval and auditing from the enterprise security team. Which TWO architectural controls should the lead cloud architect implement to meet these requirements?

Select all that apply

Show answer & explanation

Answer: Enforce the `constraints/gcp.resourceLocations` Organization Policy at the top-level organization folder to restrict resource creation strictly to `southamerica-east1`.; Enable Access Approval alongside Access Transparency to require explicit permission before Google personnel can access data and to maintain an immutable log of access reasons.

Answer

The enterprise must enforce the `constraints/gcp.resourceLocations` Organization Policy to restrict resource creation strictly to the `southamerica-east1` region, and enable Access Approval along with Access Transparency to ensure explicit security team approval and immutable logging for any Google support access.
To satisfy strict regional data sovereignty mandates, enforcing the `constraints/gcp.resourceLocations` Organization Policy ensures all resources remain within `southamerica-east1`. To satisfy administrative auditing and cloud provider access oversight requirements, enabling Access Approval gates support access behind explicit customer permissions while Access Transparency provides audit logs of vendor access.

Step-by-Step Solution

1
Address data sovereignty and regional confinement mandates.
Apply the `constraints/gcp.resourceLocations` organization policy constraint specifying `in:southamerica-east1-locations` to prevent resource deployment outside the approved geographical jurisdiction.
Organization policies provide programmatic guardrails that block infrastructure provisioning in unapproved geographic locations regardless of IAM permissions.
2
Address cloud provider access governance and auditing mandates.
Enable Access Approval to establish an explicit sign-off workflow when Google engineers require system access, and enable Access Transparency to generate audit logs of provider personnel activities.
Regulatory compliance frameworks often demand that third-party access (including cloud vendor administrators) is gated by explicit authorization and recorded in audit trails.

Key Concept

Data Sovereignty Guardrails and Cloud Provider Access Controls
Question 692Question

An international maritime shipping logistics enterprise is designing a modern vessel telemetry and port operations platform on Google Cloud. The architecture team needs to map high-level business goals into conceptual, logical, and physical tiers. The system must ingest high-velocity IoT position and engine diagnostic telemetry from thousands of vessels globally, process stateless tracking pings with minimal infrastructure management overhead, and enforce strict data exfiltration defenses around sensitive manifest records stored in managed storage. Which TWO architectural decisions correctly map these requirements across logical and physical layers? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Map the logical real-time telemetry ingestion and analytical storage tiers to Cloud Pub/Sub paired with Cloud Bigtable, using Cloud Run for stateless HTTP tracking pings.; Map the physical data perimeter security tier by configuring VPC Service Controls around Cloud Storage and Cloud Bigtable, restricting exfiltration pathways regardless of IAM authorization.

Answer

The correct architecture maps real-time telemetry ingestion and high-velocity storage to Cloud Pub/Sub and Cloud Bigtable with Cloud Run for stateless processing, and secures sensitive storage resources using VPC Service Controls to prevent data exfiltration.
The correct architectural choices appropriately align logical functions with optimal physical GCP services: Pub/Sub and Bigtable handle high-velocity time-series ingestion and analytical storage, Cloud Run provides low-friction stateless compute, and VPC Service Controls establishes perimeter security around storage resources to mitigate data exfiltration risks.

Step-by-Step Solution

1
Analyze high-velocity IoT telemetry requirements at the logical and physical layers.
Cloud Pub/Sub handles decoupled high-throughput messaging, while Cloud Bigtable provides scalable low-latency storage for time-series telemetry. Serverless Cloud Run handles stateless HTTP pings efficiently without GKE cluster management overhead.
Matching workload patterns to managed cloud services minimizes operational toil and satisfies performance constraints.
2
Evaluate security constraints for protecting sensitive manifest data from exfiltration.
VPC Service Controls creates a logical/physical security perimeter around GCP storage APIs (Cloud Storage and Cloud Bigtable) to prevent data exfiltration beyond defined trust boundaries.
IAM authorization alone does not prevent authorized identities from writing data to external GCP resources outside the organization perimeter.

Key Concept

Mapping business requirements to conceptual, logical, and physical architecture tiers on Google Cloud Platform.
Estimated Time:2m 0s
Question 693Question

An enterprise organization is automating its continuous deployment pipeline using Google Cloud Deploy to roll out application releases across multiple GKE environments. The architecture team needs to ensure that the infrastructure state files managed by Terraform during pipeline execution are safe from concurrent modification and state corruption, while ensuring the execution service account adheres to the principle of least privilege. Which deployment pipeline configuration should the team implement?

Show answer & explanation

Answer: Configure the Terraform pipeline to use a Cloud Storage backend with object versioning and state locking enabled, and assign fine-grained predefined roles to the Cloud Deploy execution service account.

Answer

Configure the Terraform pipeline to use a Cloud Storage backend with object versioning and state locking enabled, and assign fine-grained predefined roles to the Cloud Deploy execution service account.
Configuring a Cloud Storage backend for Terraform ensures state files are persisted remotely with automatic object locking to prevent concurrent apply conflicts. Combining this with fine-grained predefined IAM roles for the Cloud Deploy execution service account adheres strictly to least-privilege access security controls.

Step-by-Step Solution

1
Evaluate infrastructure state management requirements.
Identify that Cloud Storage remote backends provide distributed locking and versioning for Terraform state.
Prevent concurrent pipeline executions from corrupting the IaC state.
2
Evaluate IAM least-privilege constraints for pipeline service accounts.
Select specific predefined roles for Cloud Deploy target management rather than primitive or administrative roles.
Ensure security compliance by restricting pipeline permissions to only necessary operations.

Key Concept

Continuous Deployment Pipeline Security and IaC State Management
Question 694Question

An organization needs to ensure that authorized users cannot copy sensitive data stored in Cloud Storage to external, unauthorized Google Cloud projects. Which Google Cloud security feature should be configured to establish this security boundary?

Show answer & explanation

Answer: VPC Service Controls service perimeters around the project

Answer

VPC Service Controls service perimeters around the project
VPC Service Controls allow security administrators to define perimeter boundaries around Google Cloud resources to prevent sensitive data from being moved outside controlled network environments.

Step-by-Step Solution

1
Identify the primary threat and boundary requirement in the scenario.
The requirement is preventing data exfiltration to unauthorized Google Cloud projects by authorized users.
Exfiltration prevention requires restricting access to Google API services at the perimeter level.
2
Evaluate the capabilities of VPC Service Controls.
VPC Service Controls block API communication to resources outside the defined service perimeter.
It acts as a perimeter control for Google-managed APIs like Cloud Storage.

Key Concept

VPC Service Controls for Data Exfiltration Prevention
Estimated Time:1m 0s
Question 695Question

A security architect is configuring perimeter controls for an enterprise application on Google Cloud. The application backend stores sensitive analytical data that must be guarded against unauthorized data exfiltration, while the public endpoint requires protection against Layer 7 distributed denial-of-service (DDoS) attacks. Which TWO security controls should you implement to satisfy these requirements?

Select all that apply

Show answer & explanation

Answer: Attach a Google Cloud Armor security policy to the External HTTP(S) Load Balancer backend service.; Configure a VPC Service Controls perimeter around the project resources containing sensitive data.

Answer

To protect against Layer 7 DDoS attacks and prevent data exfiltration, you should attach Google Cloud Armor security policies to the External HTTP(S) Load Balancer backend service and establish a VPC Service Controls perimeter around sensitive GCP resources.
Google Cloud Armor provides edge security filtering and DDoS mitigation for HTTP(S) load-balanced endpoints. VPC Service Controls establishes security perimeters around GCP APIs to block unauthorized external data movement and exfiltration.

Step-by-Step Solution

1
Identify the edge web application protection mechanism.
Google Cloud Armor integrates directly with External HTTP(S) Load Balancing to inspect Layer 7 traffic and mitigate DDoS attacks.
Web application firewalls and edge protection require inspectable ingress proxies.
2
Identify the data exfiltration boundary control mechanism.
VPC Service Controls creates a security boundary around GCP services to prevent sensitive data from being moved outside authorized perimeters.
IAM alone cannot prevent authorized users from copying data to external unapproved cloud storage buckets.

Key Concept

Perimeter defense combining Google Cloud Armor edge filtering and VPC Service Controls boundaries.
Question 696Question

An enterprise team wants to secure their container pipeline on Google Cloud. They need to automatically detect software vulnerabilities in container images stored in Artifact Registry and ensure that only cryptographically signed images can be deployed to Google Kubernetes Engine (GKE). Which TWO security solutions should the cloud architect implement?

Select all that apply

Show answer & explanation

Answer: Enable automatic vulnerability scanning in Artifact Registry for container images; Configure a Binary Authorization policy on the GKE cluster to require attestations prior to deployment

Answer

The team should enable automatic vulnerability scanning in Artifact Registry to detect image vulnerabilities upon push, and configure a Binary Authorization policy on the GKE cluster to enforce cryptographic attestation before container deployment.
Automated vulnerability scanning in Artifact Registry inspects container images for security flaws at push time, while Binary Authorization checks image attestations at deployment time to ensure only signed container images run on GKE.

Step-by-Step Solution

1
Identify the build and storage container vulnerability detection solution
Automatic vulnerability scanning in Artifact Registry scans container images for known vulnerabilities upon upload.
This satisfies the requirement to scan images stored in Artifact Registry automatically.
2
Identify the deploy-time container image signature enforcement solution
Binary Authorization integrates with GKE to verify cryptographic signatures (attestations) before allowing pods to deploy.
This satisfies the requirement to restrict cluster deployment strictly to verified and signed container images.

Key Concept

Combining Artifact Registry vulnerability scanning for image analysis with Binary Authorization for deploy-time signature enforcement on GKE.
Estimated Time:1m 0s
Question 697Question

An enterprise organization is setting up a hybrid connectivity architecture between an on-premises data center and Google Cloud using Dedicated Interconnect. The architecture uses a single custom-mode VPC network with application subnets deployed in both the us-central1 and europe-west1 regions. Cloud Routers are deployed in both regions to establish BGP sessions with on-premises routers. The lead network architect requires workloads in all GCP regions to dynamically send and receive traffic to and from on-premises through the Interconnect attachments in any region. Which VPC network configuration must be applied to satisfy this requirement?

Show answer & explanation

Answer: Set the VPC network dynamic routing mode to Global.

Answer

Set the VPC network dynamic routing mode to Global.
In Google Cloud Networking, a VPC network's dynamic routing mode determines whether dynamic routes learned by Cloud Routers (via BGP over Interconnect or VPN) are available only in the region of the Cloud Router (Regional) or across all regions in the VPC (Global). Setting dynamic routing to Global allows instances in europe-west1 to utilize the Cloud Router and Interconnect located in us-central1, and vice versa.

Step-by-Step Solution

1
Analyze the routing scope requirement for multi-region VPC subnets communicating via BGP.
Identified that by default, Regional Dynamic Routing only shares dynamic routes learned by Cloud Routers with resources in the same region.
Regional dynamic routing restricts dynamic routes to the local region of the Cloud Router.
2
Determine the parameter required to expand dynamic route propagation across all regions within the VPC.
Configuring Global Dynamic Routing allows Cloud Routers in any region to propagate BGP-learned routes to all subnets in the VPC across all regions.
Global dynamic routing enables global visibility of BGP dynamic routes across the entire VPC topology.

Key Concept

VPC Dynamic Routing Modes (Regional vs. Global)
Question 698Question

An organization is deploying application container images to Google Kubernetes Engine (GKE). To prevent unauthorized or untested code from running in production, the cloud security team requires that only container images digitally signed by an approved CI/CD attestation authority can be deployed to the cluster. Which Google Cloud service should the cloud architect configure to enforce this requirement?

Show answer & explanation

Answer: Binary Authorization

Answer

Binary Authorization should be used to enforce deploy-time cryptographic signature validation for container images on GKE clusters.
Binary Authorization is Google Cloud's deploy-time security control that ensures only container images that have been built and signed by trusted attestors can be deployed to GKE clusters.

Step-by-Step Solution

1
Identify the security goal in the scenario
The requirement is to prevent untrusted or unsigned container images from being deployed to GKE.
Container supply chain security requires validating software signatures before execution.
2
Evaluate GCP native container security controls
Binary Authorization provides deployment-time policy enforcement based on cryptographic signatures (attestations).
It integrates directly with GKE deployment APIs to block non-compliant image deployments.

Key Concept

Deploy-time image verification using Binary Authorization
Question 699Question

An organization is analyzing its automated continuous deployment pipeline, which uses Cloud Build to deploy microservice updates to a Google Kubernetes Engine (GKE) cluster and store images in Artifact Registry. An architecture review reveals that the pipeline currently uses the default Cloud Build service account with broad broad-spectrum project access, violating security compliance guidelines. Which IAM configuration strategy should the cloud architect recommend to secure the CI/CD pipeline while adhering to the principle of least privilege?

Show answer & explanation

Answer: Configure Cloud Build to execute using a dedicated user-managed service account, and assign only granular predefined roles such as Kubernetes Engine Developer for GKE deployments and Artifact Registry Writer for container image uploads.

Answer

Configure Cloud Build to execute using a dedicated user-managed service account, and assign only granular predefined roles such as Kubernetes Engine Developer for GKE deployments and Artifact Registry Writer for container image uploads.
Configuring Cloud Build to run as a user-managed service account with fine-grained roles (Kubernetes Engine Developer and Artifact Registry Writer) follows Google Cloud security best practices. It ensures the pipeline has necessary operational privileges for GKE deployments and artifact pushes while restricting unnecessary project-level access.

Step-by-Step Solution

1
Analyze pipeline permission requirements
Identify the minimum operations required: deploying workloads to GKE and pushing artifacts to Artifact Registry.
Security best practices dictate scoping permissions exclusively to actions performed by the automated pipeline.
2
Select service account architecture
Create a dedicated user-managed service account instead of relying on the default Cloud Build service account.
User-managed service accounts allow fine-grained access control bound to specific build triggers and workflows.
3
Attach minimal predefined IAM roles
Grant Kubernetes Engine Developer (roles/container.developer) and Artifact Registry Writer (roles/artifactregistry.writer).
These roles provide exact permissions needed for cluster deployment and image publishing without granting administrative access.

Key Concept

CI/CD Pipeline Security and Service Account Governance in GCP
Question 700Question

An enterprise organization is preparing to migrate its core application workloads to Google Cloud ahead of a major product launch. During pilot testing, automated deployment pipelines failed because the target region exceeded default Compute Engine vCPU limits. Which operational change management practice should the Cloud Architect implement to prevent this deployment disruption?

Show answer & explanation

Answer: Include quota verification and proactive regional quota increase requests as required milestones in the migration readiness checklist.

Answer

Include quota verification and proactive regional quota increase requests as required milestones in the migration readiness checklist.
Proactively auditing projected workload demands against default GCP quota limits and requesting necessary quota adjustments during pre-migration planning ensures smooth operational execution and avoids deployment downtime.

Step-by-Step Solution

1
Identify resource requirements and potential bottlenecks for the upcoming cloud migration.
Recognize that default Google Cloud regional project quotas may be lower than the capacity needed for large-scale enterprise deployments.
Default quota limits are safety mechanisms that prevent accidental over-provisioning.
2
Integrate quota reviews into organizational change management and readiness procedures.
Establish a process where project teams request regional quota increases in Google Cloud Console ahead of time.
Quota increases require evaluation by Google Cloud and may take time to process, making pre-planning essential to maintain deployment schedules.

Key Concept

Analyzing Business Stakeholder Requirements and Managing Organizational Change
PreviousPage 35 / 80Next
All practice questions — Google Cloud Professional Cloud Architect | Examkin