All practice questions

1598 questions

Question 561Question

An enterprise security architect wants to prevent developers from creating service account keys and ensure that Compute Engine resources can only be deployed in specific approved Google Cloud regions across all projects contained within the `Production` folder. Which TWO Organization Policy constraints should be configured to satisfy these governance requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Enforce `constraints/iam.disableServiceAccountKeyCreation` at the `Production` folder level.; Enforce `constraints/gcp.resourceLocations` with an allowed locations list at the `Production` folder level.

Answer

The correct policy constraints to enforce at the `Production` folder level are `constraints/iam.disableServiceAccountKeyCreation` to block key creation and `constraints/gcp.resourceLocations` to restrict regional deployments.
Enforcing `constraints/iam.disableServiceAccountKeyCreation` directly disables service account key creation, and enforcing `constraints/gcp.resourceLocations` limits infrastructure deployment to specified regions. Configured at the folder level, these constraints automatically govern all child projects.

Step-by-Step Solution

1
Identify the requirement for disabling service account key creation.
Recognize that `constraints/iam.disableServiceAccountKeyCreation` is the built-in Organization Policy constraint designed specifically to block service account key generation.
Organization policies provide central declarative control over resource behaviors across the hierarchy.
2
Identify the requirement for restricting geographic resource deployment.
Recognize that `constraints/gcp.resourceLocations` allows administrators to specify an allowlist of Google Cloud regions for resource creation.
This constraint restricts resource provisioning to approved regions to maintain data sovereignty and regulatory compliance.
3
Determine the appropriate scope for enforcement.
Apply both constraints at the `Production` folder level so all nested child projects inherit the governance rules.
Applying policies at the folder level ensures uniform inheritance across all current and future projects under that folder.

Key Concept

Organization Policy Constraints for IAM Security and Location Restrictions
Question 562Question

A security administrator needs to investigate which user modified IAM permissions and created new Compute Engine instances within a project. The administrator requires access to log entries that record administrative actions and configuration changes. Which Cloud Audit Logs category provides this record and is enabled by default across all Google Cloud projects?

Show answer & explanation

Answer: Admin Activity audit logs

Answer

Admin Activity audit logs contain entries for API calls or administrative actions that modify resource configurations or metadata, and they are always enabled by default.
Admin Activity audit logs record API calls or administrative actions that alter the configuration or metadata of Google Cloud resources. These logs are generated automatically and enabled by default across all projects, making them the correct choice for auditing IAM and instance creation operations.

Step-by-Step Solution

1
Identify the type of operation being audited.
The operation involves modifying resource metadata and project configuration (IAM permissions and Compute Engine instance creation).
Administrative actions modifying resources fall under Admin Activity logs.
2
Determine default log enablement in Google Cloud.
Admin Activity audit logs are written automatically for all resources and cannot be disabled.
Google Cloud enforces Admin Activity logging by default for security governance.

Key Concept

Cloud Audit Logs categories and default enablement behavior
Question 563Question

A software platform team is automating the provisioning of infrastructure for a single-region transactional order processing system. The architecture requires a relational database deployed across two availability zones for high availability. Compliance guidelines mandate that storage encryption keys must be managed in Cloud KMS with custom rotation control, avoiding direct handling of raw encryption keys by the application team. Additionally, the team must protect the automated deployment pipeline state against concurrency conflicts and state file overwrites. Which combination of provisioning configurations fulfills these requirements?

Show answer & explanation

Answer: Provision a Cloud SQL for PostgreSQL regional high-availability instance configured with Customer-Managed Encryption Keys (CMEK) referencing Cloud KMS, and store the Terraform state in a Cloud Storage remote backend configured with Object Versioning and state locking.

Answer

Provision a Cloud SQL for PostgreSQL regional high-availability instance configured with Customer-Managed Encryption Keys (CMEK) referencing Cloud KMS, and store the Terraform state in a Cloud Storage remote backend configured with Object Versioning and state locking.
Provisioning Cloud SQL regional HA fulfills the regional dual-zone uptime requirement. Using Customer-Managed Encryption Keys (CMEK) integrates directly with Cloud KMS to satisfy enterprise key management and rotation policies without transmitting raw keys. Storing Terraform state in Cloud Storage with Object Versioning and native locking prevents concurrency conflicts during automated provisioning pipelines.

Step-by-Step Solution

1
Evaluate the database tier requirements
Identify that a single-region relational database with dual-zone high availability is best served by Cloud SQL regional HA rather than globally distributed Cloud Spanner.
Cloud SQL regional HA provides automated cross-zone failover within a single GCP region at optimal cost for standard transactional workloads.
2
Evaluate encryption key management constraints
Select Customer-Managed Encryption Keys (CMEK) integrated with Cloud KMS.
CMEK allows central organization control over key rotation and IAM policies in Cloud KMS without forcing administrators to hold and transmit raw encryption keys (which is required by CSEK).
3
Evaluate Infrastructure as Code (IaC) state backend requirements
Select Google Cloud Storage remote backend with state locking and Object Versioning.
Cloud Storage native state locking prevents concurrent terraform apply collisions while Object Versioning enables state recovery in case of accidental corruption.

Key Concept

Provisioning Cloud SQL with CMEK and securing remote IaC state backends
Question 564Question

A smart manufacturing company needs to migrate its regional plant monitoring infrastructure to Google Cloud within a 14-day migration window. The legacy environment consists of a 250 TB250\text{ TB} archive of historical sensor logs stored on local NFS storage and a 400 GB400\text{ GB} operational PostgreSQL database. The on-premises site has a single dedicated 100 Mbps100\text{ Mbps} internet connection, and the database cutover requires near-zero downtime.

Which TWO architectural strategies should the team implement to meet these requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Order a GCP Transfer Appliance to physically ingest and transfer the 250 TB250\text{ TB} sensor archive to Cloud Storage.; Deploy Database Migration Service (DMS) with continuous Change Data Capture (CDC) to migrate the PostgreSQL database to Cloud SQL.

Answer

The team should order a GCP Transfer Appliance to move the 250 TB250\text{ TB} sensor archive offline to Cloud Storage and use Database Migration Service (DMS) with continuous Change Data Capture (CDC) to migrate the PostgreSQL database to Cloud SQL with minimal downtime.
For large multi-terabyte data transfers (250 TB250\text{ TB}) over limited bandwidth (100 Mbps100\text{ Mbps}), online network transfer would take over 230 days, making an offline appliance like GCP Transfer Appliance essential to complete the transfer within a 14-day window. For operational relational database migrations requiring near-zero downtime, using Database Migration Service with CDC enables continuous replication from PostgreSQL to Cloud SQL, allowing a rapid cutover.

Step-by-Step Solution

1
Calculate the transfer duration for the unstructured sensor log archive over the existing network connection.
Transferring 250 TB250\text{ TB} (2×1015 bits2\times 10^{15}\text{ bits}) at 100 Mbps100\text{ Mbps} takes approximately 20,000,000 seconds231 days20,000,000\text{ seconds} \approx 231\text{ days}, which exceeds the 14-day window.
Large multi-terabyte datasets on constrained network pipes require offline physical transfer via GCP Transfer Appliance.
2
Select the appropriate data migration mechanism for the 250 TB250\text{ TB} unstructured dataset.
Use GCP Transfer Appliance to load data locally, ship the appliance to Google Cloud, and ingest into Cloud Storage within the 14-day window.
Transfer Appliance bypasses network bandwidth bottlenecks for multi-terabyte dataset migrations.
3
Select the database migration strategy for the 400 GB400\text{ GB} operational PostgreSQL database requiring near-zero downtime.
Utilize Database Migration Service (DMS) configured with continuous CDC targeting Cloud SQL for PostgreSQL.
CDC continuously syncs real-time transaction logs, allowing applications to perform a fast cutover without extended maintenance windows.

Key Concept

Evaluating network transfer throughput versus offline physical data transport appliances, and designing continuous replication paths for low-downtime relational database migrations.
Question 565Question

A security architect is establishing a new Google Cloud resource hierarchy for an enterprise workload. To ensure proper IAM role inheritance and central governance, arrange the initial administrative setup steps in the correct top-down sequence, starting from the highest scope in the resource hierarchy.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct administrative sequence starts at the Organization node, followed by creating Folders, provisioning Projects within those Folders, and finally granting fine-grained resource-level IAM permissions inside the Projects.
Google Cloud resource hierarchy follows a strict top-down structure: Organization node -> Folders -> Projects -> Resources. IAM permissions granted at parent levels automatically inherit downward to child nodes.

Step-by-Step Solution

1
Identify the top root level of the GCP resource hierarchy.
The Organization node is established at the root level to apply central governance and top-level IAM policies.
Policies applied at the Organization level automatically inherit down to all child folders, projects, and resources.
2
Structure organizational units below the root.
Folders are created under the Organization node to group projects by business unit or environment (e.g., Production, Staging).
Folders inherit Organization policies and pass down combined policy bindings to member projects.
3
Provision resource management containers.
Google Cloud Projects are created inside the designated Folders.
Projects serve as administrative boundaries for resources and inherit policies from parent Folders and the Organization.
4
Configure granular resource access control.
Fine-grained IAM roles and service account permissions are assigned to specific resources inside the Projects.
Resource-level grants enforce least-privilege access on individual workloads.

Key Concept

Google Cloud Resource Hierarchy and Top-Down IAM Policy Inheritance
Question 566Question

A global pharmaceutical company is building a public API service to ingest real-time webhook updates from external clinical research partners. The service workload is stateless, containerized, handles standard HTTPS POST requests, and experiences unpredictable traffic spikes interspersed with prolonged periods of complete inactivity. The enterprise architecture guidelines mandate zero server maintenance, fast automatic scaling down to zero instances during idle periods, and eliminating baseline running costs. Which compute platform should the Cloud Architect select to meet these requirements?

Show answer & explanation

Answer: Deploy the containerized application on Cloud Run with autoscaling configured to scale down to zero instances.

Answer

Deploying the containerized application on Cloud Run with autoscaling configured to scale down to zero instances is the optimal solution because it eliminates operational overhead, handles HTTP webhooks natively, and avoids paying for idle resources.
Cloud Run is designed specifically for stateless containerized microservices receiving web/HTTP requests. It automatically handles infrastructure provisioning, security patching, and autoscaling, including scaling down to zero instances when no requests are being processed, ensuring zero costs during idle periods.

Step-by-Step Solution

1
Analyze workload characteristics and constraints
Workload is stateless, containerized, uses HTTPS POST webhooks, experiences sharp spikes with idle periods, and requires zero server maintenance.
Identifying protocol, statefulness, and operational limits narrows down compute platform choices.
2
Evaluate Google Cloud compute options against zero-idle cost and low overhead requirements
Cloud Run natively supports stateless HTTP containers, manages all infrastructure, scales rapidly on incoming HTTP requests, and scales to zero when idle.
GKE and Compute Engine introduce baseline cost and administrative management overhead.
3
Select the optimal architecture platform
Cloud Run fulfills all technical constraints with the lowest cost and operational burden.
Meets Google Cloud architecture best practices for stateless microservices.

Key Concept

Compute Platform Selection for Stateless Containerized HTTP Workloads
Question 567Question

A cloud security architect is designing an enterprise security monitoring strategy for a multi-project Google Cloud organization. The security operations team requires real-time automated threat detection for security anomalies across all infrastructure and wants to centralize all organization-wide audit logs for export to an external Security Information and Event Management (SIEM) system. Which TWO architectural steps should the architect take to satisfy these requirements?

Select all that apply

Show answer & explanation

Answer: Enable Security Command Center Premium at the organization level to leverage Event Threat Detection for real-time analysis of audit log streams and security findings.; Create an aggregated log sink at the organization root with an inclusion filter for audit logs, setting a centralized Pub/Sub topic as the export destination.

Answer

To establish real-time threat detection and centralized log export for an enterprise Google Cloud organization, you should enable Security Command Center Premium at the organization level for Event Threat Detection, and create an organization-level aggregated log sink targeting a Pub/Sub topic connected to the external SIEM.
Enabling Security Command Center Premium at the organization root allows Event Threat Detection to analyze audit log streams across all projects automatically. Combining this with an organization-level aggregated log sink routing to Pub/Sub provides scalable, real-time log ingestion into an external SIEM.

Step-by-Step Solution

1
Enable threat detection capabilities at the organization level.
Security Command Center Premium provides Event Threat Detection to automatically monitor Cloud Audit Logs across all organization projects for security threats.
Threat detection must operate across all resources in the organization hierarchy without requiring project-by-project setup.
2
Configure centralized audit log aggregation and real-time streaming.
An aggregated log sink created at the organization root captures logs from all current and future projects and pushes them to Pub/Sub for SIEM consumption.
Aggregated sinks guarantee compliance and auditing coverage without relying on individual project configurations.

Key Concept

Organization-wide log aggregation and Security Command Center Event Threat Detection integration
Question 568Question

A financial organization needs to store sensitive audit logs in Google Cloud Storage. Regulatory requirements mandate that the organization retain control of the cryptographic keys using Google Cloud Key Management Service (Cloud KMS) to support automated key rotation. They do not want the operational burden of managing and supplying raw key material for every storage request. Which encryption approach should the cloud architect recommend?

Show answer & explanation

Answer: Customer-Managed Encryption Keys (CMEK) using Cloud KMS

Answer

Customer-Managed Encryption Keys (CMEK) using Cloud KMS
Customer-Managed Encryption Keys (CMEK) allow customers to control key lifecycle management and automated key rotation through Google Cloud KMS, satisfying regulatory control requirements without requiring raw key management per request.

Step-by-Step Solution

1
Identify key management requirements
The requirement requests using Cloud KMS with key control and automated rotation without managing raw key material directly per request.
Regulatory compliance specifies key ownership within GCP's KMS solution.
2
Evaluate Google Cloud encryption options
CMEK uses Cloud KMS to manage keys and supports automatic rotation, meeting all client specifications.
CSEK requires managing raw keys outside GCP, whereas default encryption does not give key control to the customer.

Key Concept

Customer-Managed Encryption Keys (CMEK) vs Customer-Supplied Encryption Keys (CSEK) in GCP
Question 569Question

A enterprise architecture team is implementing centralized governance guardrails across their Google Cloud resource hierarchy. They must ensure that development teams cannot allocate external IP addresses to virtual machine instances within the Development folder. Additionally, they must restrict API access within the Analytics folder so that projects can only enable approved Google Cloud services (such as Cloud Storage and BigQuery). Which TWO configuration steps should the cloud architect execute using Organization Policies to achieve these requirements? (Select TWO)

Select all that apply

Show answer & explanation

Answer: Apply the `constraints/compute.vmExternalIpAccess` boolean constraint on the Development folder to deny public IP assignment to compute instances.; Configure the `constraints/gcp.restrictServiceUsage` list constraint on the Analytics folder with an `allowed_values` list containing only the approved service identifiers.

Answer

Enforce the `constraints/compute.vmExternalIpAccess` constraint on the Development folder to block external IP creation, and apply the `constraints/gcp.restrictServiceUsage` list constraint on the Analytics folder specifying the allowed service APIs.
Organization Policies provide centralized governance controls across Google Cloud folders and organizations. The `compute.vmExternalIpAccess` constraint explicitly restricts external IP assignment on Compute Engine VMs, while `gcp.restrictServiceUsage` specifies an allowlist of service APIs that projects under the folder can enable.

Step-by-Step Solution

1
Identify the appropriate constraint type for restricting external IP addresses on Compute Engine instances.
Selected `constraints/compute.vmExternalIpAccess` enforced at the Development folder level.
Organization Policies evaluate resource attributes hierarchically, preventing VM instances from acquiring public IPs regardless of user IAM permissions.
2
Identify the appropriate constraint type for restricting which Google Cloud APIs can be enabled within a folder.
Selected `constraints/gcp.restrictServiceUsage` with allowed service list applied to the Analytics folder.
This list constraint restricts service enablement across all underlying projects to only explicitly approved service APIs.

Key Concept

Organization Policies enforce central programmatic guardrails over resource configurations and API usage across the Google Cloud resource hierarchy.
Question 570Question

An enterprise organization uses a Google Cloud resource hierarchy structured with dedicated folders for Production, Staging, and Development. A central deployment pipeline requires automated authorization to provision Compute Engine instances across all projects under the Production folder. Additionally, the deployment pipeline must attach a dedicated workload service account to these newly provisioned instances. You must enforce the principle of least privilege while minimizing management complexity. Which TWO IAM configuration steps should you execute? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Grant the Compute Instance Admin (v1) role (roles/compute.instanceAdmin.v1) to the deployment pipeline service account at the Production folder level.; Grant the Service Account User role (roles/iam.serviceAccountUser) to the deployment pipeline service account directly on the target workload service account.

Answer

Grant the Compute Instance Admin (v1) role to the deployment pipeline service account at the Production folder level, and grant the Service Account User role to the deployment pipeline service account directly on the workload service account resource.
Granting Compute Instance Admin (v1) at the Production folder level applies policy inheritance to automatically encompass all projects within that folder, meeting least privilege and avoiding per-project maintenance. Granting Service Account User specifically on the workload service account resource allows the deployment identity to attach it to VM instances without exposing administrative control over the service account itself.

Step-by-Step Solution

1
Analyze resource hierarchy scope and least-privilege role requirements for Compute Engine provisioning.
Identify that roles/compute.instanceAdmin.v1 granted at the Production folder node propagates down to all constituent projects seamlessly via IAM policy inheritance.
Prevents per-project role binding overhead while restricting access exclusively to production workloads.
2
Evaluate required permissions for attaching a service account to a compute instance.
Identify that roles/iam.serviceAccountUser granted specifically on the target workload service account provides instance-binding rights.
Allows instance attachment without granting full administrative privileges over the service account lifecycle.

Key Concept

Resource Hierarchy IAM Policy Inheritance & Fine-Grained Service Account Impersonation
Question 571Question

An enterprise organization operates a Google Cloud Shared VPC infrastructure with a Host Project for core network management and multiple Service Projects housing distinct microservice applications. The architecture team needs to enable microservices in Service Project A to privately consume an API hosted in an external software vendor's Google Cloud VPC. The solution must strictly prevent transitive network access to other Service Projects attached to the Host VPC, eliminate any risk of IP address space overlap, and avoid routing traffic across the public internet. Which network topology configuration should you implement?

Show answer & explanation

Answer: Configure Private Service Connect endpoints in Service Project A targeting the external vendor's published Service Attachment.

Answer

Configuring Private Service Connect endpoints in Service Project A targeting the external vendor's published Service Attachment provides isolated, private, and non-transitive access.
Private Service Connect (PSC) enables private, unidirectional consumption of services across GCP VPCs and organizations. By creating a PSC endpoint inside Service Project A, microservices communicate with the vendor's service using an internal IP address provisioned in Service Project A's subnet. This traffic traverses Google's internal network without requiring VPC Network Peering, avoiding transitivity constraints, eliminating CIDR range overlap issues, and isolating the connection strictly to the initiating service project.

Step-by-Step Solution

1
Analyze network isolation and transitivity constraints
Identified that VPC Network Peering does not allow transitive routing across hub/host networks, rendering VPC Peering ineffective for attached Service Projects.
Google Cloud VPC Network Peering only exchanges routes between directly peered networks and explicitly blocks transit routing.
2
Evaluate inter-tenant private service connectivity options
Selected Private Service Connect (PSC) as the matching architecture pattern.
PSC allows consumer VPCs to deploy internal IP endpoints that map directly to a producer's Service Attachment via Network Load Balancing, without peering or sharing IP address ranges.
3
Validate security and boundary requirements
PSC endpoints ensure traffic remains within Google's private network, avoids IP overlaps via NAT translation at the PSC layer, and prevents transitive access to other Service Projects.
PSC endpoints are scoped specifically to the consumer network where they are provisioned and do not expose broader network topology routes.

Key Concept

Private Service Connect vs VPC Peering Transitivity in Shared VPC Architectures
Estimated Time:2m 0s
Question 572Question

A financial services organization is automating its deployment pipeline using Google Cloud Deploy to manage releases across GKE clusters in staging and production. To ensure compliance and zero downtime during application upgrades, the release process must deploy new microservice revisions to a small percentage of user traffic first, validate service metrics, and support an automated instant rollback if error thresholds are exceeded. Which deployment and automation strategy should the Cloud Architect implement?

Show answer & explanation

Answer: Define a progressive canary deployment strategy in the Cloud Deploy delivery pipeline configuration, integrated with automated pipeline hooks to evaluate Cloud Monitoring metrics before promoting traffic.

Answer

Define a progressive canary deployment strategy in the Cloud Deploy delivery pipeline configuration, integrated with automated pipeline hooks to evaluate Cloud Monitoring metrics before promoting traffic.
Google Cloud Deploy natively supports progressive deployment strategies such as canary releases for GKE and Cloud Run. By defining canary percentage phases in the delivery pipeline configuration and integrating verification hooks, organizations can automatically validate application metrics and perform automated rollbacks if issues occur.

Step-by-Step Solution

1
Identify the release strategy requirements.
The requirement demands progressive traffic shifting (canary) with automated metric verification and zero-downtime rollback capabilities.
Enterprise continuous delivery pipelines on GCP require declarative progressive delivery tools to minimize blast radius during releases.
2
Evaluate GCP native continuous deployment tools.
Google Cloud Deploy provides built-in declarative support for canary deployment phases and custom pipeline execution hooks for automated verification.
Cloud Deploy standardizes Kubernetes and Cloud Run release automation across environments without custom shell scripting overhead.

Key Concept

Automating Continuous Deployment Pipelines and Progressive Release Strategies using Cloud Deploy
Estimated Time:1m 30s
Question 573Question

A software development company is migrating its infrastructure management from local scripts to Terraform on Google Cloud. During continuous integration runs, multiple automated build workers occasionally attempt to apply changes to the same regional infrastructure concurrently, resulting in state file race conditions and loss of state revision history. Which remote backend strategy should the cloud architect implement to ensure safe concurrent execution and historical state recovery?

Show answer & explanation

Answer: Configure the Terraform backend to use a Cloud Storage bucket with Object Versioning enabled to support automatic state locking and state history preservation.

Answer

Configure the Terraform backend to use a Cloud Storage bucket with Object Versioning enabled to support automatic state locking and state history preservation.
The standard GCP solution for Terraform remote state storage is a Cloud Storage (GCS) bucket. The `gcs` backend natively handles state locking using Cloud Storage strongly consistent operations and object metadata locks, preventing parallel modifications. Enabling Object Versioning on the bucket ensures that all state changes create historical revisions, allowing administrators to recover previous states if needed.

Step-by-Step Solution

1
Identify the concurrency and state retention requirements
The requirement calls for distributed state locking during concurrent pipeline runs and historical version retention for recovery.
Preventing state corruption requires atomic locks, while preserving revision history protects against accidental state loss.
2
Evaluate Google Cloud Storage native capabilities with Terraform
The standard Google Cloud Storage backend (`gcs`) automatically uses Cloud Storage object locks to prevent concurrent modifications.
Cloud Storage handles state locking natively without requiring additional external locking mechanisms like DynamoDB.
3
Enable Object Versioning on the Cloud Storage bucket
Enabling versioning on the Cloud Storage bucket ensures that every state modification creates a new object version.
Object versioning allows rollback to previous state files if a deployment corrupted or misplaced state data.

Key Concept

Terraform Remote State Management and Cloud Storage Locking
Question 574Question

An organization is establishing baseline security logging policies across their Google Cloud projects. Which of the following statements accurately describe default behavior and capabilities of Google Cloud Audit Logs? (Select TWO)

Select all that apply

Show answer & explanation

Answer: Admin Activity audit logs are enabled by default for all Google Cloud services and do not incur log ingestion costs.; Data Access audit logs are disabled by default for most services because they record high-volume data read and write operations.

Answer

Admin Activity audit logs are enabled by default at no cost, and Data Access audit logs are disabled by default for most GCP services to avoid excessive log ingestion.
Admin Activity audit logs are enabled automatically across all GCP resources without additional ingestion charges. Conversely, Data Access audit logs are disabled by default (except BigQuery) to manage data ingestion volume and log storage expenses.

Step-by-Step Solution

1
Evaluate default state of Admin Activity audit logs
Admin Activity logs record administrative configuration changes and are always enabled by default free of charge.
Google Cloud mandates Admin Activity logging across all GCP services to ensure foundational administrative accountability.
2
Evaluate default state of Data Access audit logs
Data Access logs are disabled by default for most services (with BigQuery being an exception).
Data Access API operations generate extremely high volumes of events, so enabling them requires explicit user configuration.

Key Concept

Cloud Audit Log Types and Default Configuration
Question 575Question

A multinational retail company structures its Google Cloud environment with dedicated folders for regional business units underneath the organization node. A third-party compliance agency requires read-only access to review IAM policies, asset metadata, and security settings across all projects in the hierarchy. However, company governance strictly prohibits the agency from viewing underlying application data stored within Cloud Storage objects or database instances. Which IAM configuration fulfills these requirements while maintaining least privilege and minimizing management overhead?

Show answer & explanation

Answer: Grant the roles/browser and roles/iam.securityReviewer predefined roles to the auditor group at the Organization node.

Answer

Granting the predefined roles for Browser and Security Reviewer to the auditor group at the Organization level satisfies the security requirements with minimal operational overhead.
Assigning the Security Reviewer and Browser roles at the Organization level leverages resource hierarchy policy inheritance so permissions automatically apply across all folders and projects. The Security Reviewer role grants access to view IAM policies and configuration metadata without exposing application data stored in Cloud Storage or database engines.

Step-by-Step Solution

1
Analyze access scope and auditing requirements across the Google Cloud resource hierarchy.
The auditors need access across all current and future regional projects contained within folders under the organization.
Assigning IAM roles at the Organization node enables permissions to inherit down the entire resource tree automatically, eliminating per-folder administrative maintenance.
2
Evaluate candidate IAM roles against least privilege security constraints.
The Security Reviewer role (roles/iam.securityReviewer) permits inspecting IAM policies and configurations without granting data read permissions, while the Browser role (roles/browser) allows viewing the hierarchy layout.
Predefined security roles separate metadata and policy inspection capabilities from actual data plane payload access.
3
Reject overly permissive configurations and improper control mechanisms.
Primitive roles (Viewer/Editor), administrative service account privileges, and network-level perimeters fail to enforce proper identity-based data access restrictions.
Relying on primitive roles or administrative grants introduces unnecessary privilege risks that breach strict organizational compliance controls.

Key Concept

IAM Policy Inheritance and Predefined Security Roles in Google Cloud Resource Hierarchy
Question 576Question

A multinational financial services enterprise manages its Google Cloud environment using a folder hierarchy divided by business units. The security compliance team requires two central guardrails across the entire `Retail-Banking` folder structure: (1) block any Compute Engine virtual machine from being provisioned with an external IP address, and (2) test a restriction against creating service account keys across the organization without breaking existing automated continuous integration pipelines. Which TWO architectural actions should the lead Cloud Architect execute using Google Cloud Organization Policies?

Select all that apply

Show answer & explanation

Answer: Apply an Organization Policy at the `Retail-Banking` folder level setting the `constraints/compute.vmExternalIpAccess` constraint to Deny All.; Configure the `constraints/iam.disableServiceAccountKeyCreation` Organization Policy constraint at the Organization root level with Enforcement set to Dry-Run.

Answer

The Cloud Architect must apply the `constraints/compute.vmExternalIpAccess` policy set to Deny All at the target folder level, and set the `constraints/iam.disableServiceAccountKeyCreation` policy to Dry-Run at the Organization root level.
The correct responses specify using Google Cloud Organization Policies appropriately: enforcing `constraints/compute.vmExternalIpAccess` at the folder node directly prevents public IP attachment on Compute Engine instances, while configuring `constraints/iam.disableServiceAccountKeyCreation` in dry-run mode at the organization root tests policy compliance against live CI pipelines without causing immediate workflow failures.

Step-by-Step Solution

1
Identify the constraint required for external IP prevention and target scope.
The `constraints/compute.vmExternalIpAccess` boolean constraint enforced at the `Retail-Banking` folder level restricts VM public IP creation across all child projects.
Organization policies inherit down the resource hierarchy, making folder-level enforcement effective for all scoped projects.
2
Identify the strategy to audit service account key creation restrictions without breaking existing pipelines.
Deploying `constraints/iam.disableServiceAccountKeyCreation` in Dry-Run mode at the organization root level emits audit logs upon key creation attempts while allowing execution.
Dry-run mode enables security teams to evaluate the operational impact on CI/CD pipelines before hard enforcement.

Key Concept

Organization Policies and Constraints
Estimated Time:2m 0s
Question 577Question

An enterprise security team has configured Cloud Audit Logs to track all read and write operations on sensitive Cloud Storage buckets containing proprietary financial data. However, the security architect wants to ensure that authorized internal users holding valid IAM read permissions cannot copy data from these corporate buckets into external Cloud Storage buckets outside the organizational boundary. Which GCP security component must be implemented alongside IAM to prevent this unauthorized data exfiltration?

Show answer & explanation

Answer: Implement VPC Service Controls around the Cloud Storage API to establish a security perimeter that restricts data transfer across perimeter boundaries.

Answer

Implementing VPC Service Controls establishes a boundary around Google Cloud services like Cloud Storage, preventing authorized credentials from copying data to external projects or locations outside the perimeter.
VPC Service Controls allow organizations to define perimeter boundaries around Google Cloud resources and services (such as Cloud Storage). Even if an identity possesses valid IAM permissions to read data inside the perimeter, VPC Service Controls prevent that data from being copied or transferred to storage resources outside the perimeter boundary.

Step-by-Step Solution

1
Analyze the threat vector described in the scenario.
Identified that authorized users with legitimate IAM read permissions can still exfiltrate data to an unauthorized destination outside the organization.
IAM grants permission to perform actions, but standard IAM alone does not restrict destination boundaries for data movement.
2
Evaluate GCP security controls designed specifically for exfiltration prevention.
VPC Service Controls restrict communication to and from restricted GCP APIs across defined enterprise perimeters.
VPC Service Controls block requests that attempt to read from a protected resource and write to a resource outside the perimeter, even if IAM permissions would otherwise allow it.

Key Concept

VPC Service Controls for Data Exfiltration Prevention
Question 578Question

An enterprise organization requires centralized compliance logging across all existing and future Google Cloud projects. The security architecture must capture both Admin Activity and Data Access audit logs, ensure that project-level administrators cannot disable or modify log export configurations, and adhere to governance requirements by protecting the centralized storage bucket with keys managed in Cloud KMS. Which strategy should the cloud security architect implement?

Show answer & explanation

Answer: Configure an organization-aggregated log sink in Cloud Logging that captures Admin Activity and Data Access logs, route the sink to a centralized Cloud Storage log bucket, and encrypt the destination bucket using Customer-Managed Encryption Keys (CMEK) hosted in Cloud KMS.

Answer

Configure an organization-aggregated log sink in Cloud Logging targeting a centralized Cloud Storage bucket encrypted with Customer-Managed Encryption Keys (CMEK) in Cloud KMS.
The correct strategy leverages organization-aggregated log sinks in Cloud Logging combined with CMEK via Cloud KMS. Organization sinks inherit down the resource hierarchy, ensuring project administrators cannot tamper with log export rules. CMEK satisfies key management governance requirements without the operational burden of managing raw key material.

Step-by-Step Solution

1
Enforce centralized log ingestion across the resource hierarchy.
Creating an aggregated log sink at the organization level automatically includes audit logs from all current and future descendant projects.
Prevents project administrators from modifying or disabling audit log collection.
2
Enable required audit log types.
Ensure Data Access and Admin Activity audit logs are included in the aggregated sink filter.
Meets compliance auditing requirements for both management operations and sensitive data reads/writes.
3
Apply Customer-Managed Encryption Keys (CMEK) to the central storage bucket.
Log data at rest is encrypted using keys managed via Cloud KMS.
Satisfies corporate governance while delegating cryptographic key lifecycle management to Cloud KMS rather than managing raw key material on-premises.

Key Concept

Organization-aggregated log sinks provide tamper-resistant, centralized security log aggregation across Google Cloud hierarchies when paired with Cloud KMS CMEK.
Question 579Question

An enterprise organization requires real-time security monitoring across all projects in its Google Cloud hierarchy. The security architecture team must stream both Cloud Storage Data Access audit logs and Security Command Center (SCC) Event Threat Detection findings to an on-premises Security Information and Event Management (SIEM) system. The solution must adhere to the principle of least privilege and native Google Cloud security recommendations. Which TWO actions should the security architect perform to meet these requirements?

Select all that apply

Show answer & explanation

Answer: Create an organization-level aggregated Cloud Logging sink configured with a filter for Data Access audit logs and set its destination to a central Pub/Sub topic monitored by the SIEM collector.; Configure Security Command Center continuous export at the organization level to stream high-severity security findings directly to a designated Pub/Sub topic.

Answer

To centrally stream security audit logs and threat findings to a SIEM while maintaining minimal necessary privileges, the architect must set up an organization-level aggregated log sink routing Data Access logs to Pub/Sub, and enable Security Command Center continuous export at the organization level to stream findings to Pub/Sub.
Centralizing security telemetry requires organization-wide aggregated log sinks for audit logs and continuous export for Security Command Center findings. Both features publish directly to Pub/Sub topics, enabling secure and real-time ingestion by third-party SIEM collectors.

Step-by-Step Solution

1
Configure centralized logging
Aggregated log sink routes Data Access audit logs from all current and future projects into a central Pub/Sub topic.
Organization-level aggregated sinks ensure complete visibility without needing project-by-project log configuration.
2
Configure Security Command Center findings export
Continuous export streams findings from Event Threat Detection and other SCC services to Pub/Sub.
Continuous export provides automated real-time notification of findings to downstream SIEM collectors.
3
Apply least privilege IAM roles
The log collector service account is granted granular Pub/Sub Subscriber permissions rather than broad administrative or primitive roles.
Primitive roles expose the organization to unnecessary security risks by granting far more privileges than needed.

Key Concept

Centralized Security Log Aggregation and Continuous Findings Export
Question 580Question

An enterprise organization is deploying a high-performance analytics platform across 15 newly created Google Cloud projects within a dedicated production folder. The deployment requires provisioning 200 N2 series Compute Engine vCPUs per project in the us-central1 region. Upon checking the newly created projects, the architect observes that the default regional quota for N2 CPUs is insufficient for the planned deployment scale. The deployment must be executed using an automated Infrastructure as Code (IaC) pipeline without causing execution failures or violating security governance principles. Which strategy should the cloud architect implement to manage this resource requirement effectively?

Show answer & explanation

Answer: Submit proactive regional quota increase requests for N2 vCPUs across all target projects via the Cloud Quotas API or Console prior to executing the IaC deployment pipeline.

Answer

Submit proactive regional quota increase requests for N2 vCPUs across all target projects via the Cloud Quotas API or Console prior to executing the IaC deployment pipeline.
The correct strategy requires evaluating regional quota constraints beforehand and submitting quota increase requests proactively through the Cloud Quotas API or GCP Console. This ensures the deployment pipeline executes without hitting quota limits or encountering runtime resource creation failures.

Step-by-Step Solution

1
Assess regional resource requirements against default project quota limits
Identified that 200 N2 vCPUs per project exceeds default regional quota limits in us-central1.
Default quota limits in new Google Cloud projects are often lower than large-scale enterprise deployment needs.
2
Request regional quota adjustments prior to IaC execution
Regional quota capacity is reviewed and approved by Google Cloud before automated deployment starts.
Quota increases require evaluation and processing time; requesting them beforehand prevents pipeline runtime failures.
3
Execute the IaC deployment using fine-grained service account permissions
Infrastructure provisions smoothly within pre-approved quota boundaries following least-privilege security controls.
Ensures full automation and compliance with organizational governance standards.

Key Concept

Proactive Resource Quota Management in GCP Infrastructure Provisioning
PreviousPage 29 / 80Next
All practice questions — Google Cloud Professional Cloud Architect | Examkin