Tüm alıştırma soruları

1598 soru

Soru 641Soru

An organization must enforce strict data sovereignty and data governance controls for sensitive data stored in Google Cloud. The compliance mandate requires restricting all data storage resources to a specific geographic region and managing encryption keys centrally using Google Cloud services. Which TWO architectural actions should the organization take to satisfy these requirements? (Select TWO)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Enforce the Resource Locations organization policy constraint (constraints/gcp.resourceLocations) to restrict resource deployment exclusively to the designated region.; Encrypt cloud storage and database resources using Customer-Managed Encryption Keys (CMEK) hosted in Cloud KMS within the designated region.

Cevap

Enforce the Resource Locations organization policy constraint to restrict resource deployment to the designated region, and encrypt storage resources using Customer-Managed Encryption Keys (CMEK) hosted in Cloud KMS.
To comply with data sovereignty and governance mandates, organizations should enforce the Resource Locations organization policy constraint to restrict resource creation to specific geographical boundaries, and use Customer-Managed Encryption Keys (CMEK) stored in regional Cloud KMS to maintain centralized control and auditability over key lifecycles.

Adım Adım Çözüm

1
Identify the data sovereignty requirement for geographic restriction
Apply the Organization Policy constraint for Resource Locations to restrict resource creation strictly to the allowed GCP region.
Organization policies provide programmatic compliance guardrails across the resource hierarchy.
2
Identify the central key management requirement
Configure Customer-Managed Encryption Keys (CMEK) via Cloud KMS within the compliant region.
CMEK allows central control, auditing, and key rotation management without requiring clients to supply raw keys on every request.

Anahtar Kavram

Data sovereignty controls using Organization Policies and centralized key governance with Customer-Managed Encryption Keys (CMEK).
Soru 642Soru

An enterprise security architect is designing an automated data ingestion pipeline into Google Cloud Storage for a highly regulated financial application. Compliance mandates that all stored customer data must be encrypted at rest using Customer-Managed Encryption Keys (CMEK) managed via Cloud KMS. The security policy requires strict separation of duties: storage administrators who provision and manage Cloud Storage buckets must not have direct permissions to encrypt or decrypt data or manage encryption keys, whereas automated system services must be granted least-privilege access to perform key operations. Additionally, the setup must support automatic key rotation every 90 days without re-encrypting existing data manually or breaking access to older object versions. Which architecture and identity configuration satisfies these security and operational requirements?

Cevabı ve açıklamayı göster

Cevap: Create a KeyRing and CryptoKey in Cloud KMS with an automated 90-day rotation schedule. Grant the Cloud Storage service account the Cloud KMS CryptoKey Encrypter/Decrypter role (roles/cloudkms.cryptoKeyEncrypterDecrypter) on the CryptoKey, grant Cloud KMS Admin rights (roles/cloudkms.admin) exclusively to the Security Operations team, and configure the bucket's default KMS key.

Cevap

The correct architecture requires creating a Cloud KMS KeyRing and CryptoKey configured with an automated 90-day rotation schedule, granting the Google Cloud Storage service account the Cloud KMS CryptoKey Encrypter/Decrypter role, restricting Cloud KMS Admin permissions to the Security Operations team, and setting the default CMEK key on the Cloud Storage bucket.
The solution using Cloud KMS CMEK with automated rotation and delegating `roles/cloudkms.cryptoKeyEncrypterDecrypter` to the Cloud Storage service account guarantees least privilege and separation of duties. Cloud KMS automatically manages key versions, allowing new writes to use the latest primary key version while keeping older versions active to decrypt existing objects.

Adım Adım Çözüm

1
Identify the proper key management model based on compliance requirements.
Cloud KMS with Customer-Managed Encryption Keys (CMEK) satisfies the requirement for central key management in GCP with automated rotation, unlike Customer-Supplied Encryption Keys (CSEK) which require managing key material on-premises and passing raw keys in request headers.
CMEK allows central governance in Cloud KMS while delegating key usage to Google Cloud services.
2
Apply the principle of least privilege and separation of duties for IAM roles.
The Cloud Storage service account ([email protected]) requires `roles/cloudkms.cryptoKeyEncrypterDecrypter` on the specific CryptoKey. Storage administrators must not receive key encrypter/decrypter or key admin permissions.
Cloud Storage acts on behalf of object writers/readers using its own service account to encrypt and decrypt data using the configured CMEK.
3
Configure key rotation lifecycle without manual re-encryption.
Automated key rotation in Cloud KMS creates a new primary key version every 90 days. Existing objects remain encrypted with their original key version, which Cloud KMS retains for decryption requests.
Cloud KMS handles key versioning seamlessly so that existing data decrypted by authorized services does not require manual re-encryption upon key rotation.

Anahtar Kavram

Data Encryption at Rest, CMEK, Separation of Duties, and Cloud KMS IAM Roles
Soru 643Soru

A enterprise healthcare company operating on Google Cloud needs to establish a centralized security auditing and log monitoring architecture across all projects under its organization. The compliance policy mandates that all read and write operations on sensitive patient data stored in Cloud Storage must be logged and monitored for suspicious activity, while maintaining strict adherence to the principle of least privilege. Which TWO architectural recommendations should a Cloud Architect make to fulfill these requirements?

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Enable Data Access audit logs (DATA_READ and DATA_WRITE) for Cloud Storage at the GCP Organization resource level.; Configure an organization-level aggregated log sink to route audit logs to a centralized Pub/Sub topic or BigQuery dataset.

Cevap

The Cloud Architect should recommend enabling Data Access audit logs (DATA_READ and DATA_WRITE) for Cloud Storage at the organization level and configuring an organization-level aggregated log sink to route audit logs to a centralized BigQuery dataset or Pub/Sub topic.
Enabling Data Access audit logs (DATA_READ and DATA_WRITE) for Cloud Storage at the organization level ensures that read and write operations on storage buckets across all projects are captured, as Data Access logs are not active by default for Cloud Storage. Additionally, setting up an organization-level aggregated log sink allows seamless collection and centralization of audit log entries into BigQuery or Pub/Sub for automated threat detection and compliance analysis.

Adım Adım Çözüm

1
Identify missing audit log telemetry for data operations
Determine that Cloud Storage Data Access audit logs must be explicitly enabled at the organization level because they are disabled by default.
Default GCP Audit Logging only collects Admin Activity and System Event logs.
2
Establish centralized log aggregation
Create an organization-wide aggregated log sink targeting a central Pub/Sub topic or BigQuery log repository.
Aggregated sinks automatically inherit logging across all present and future project resources.
3
Evaluate least-privilege permissions and perimeter controls
Reject primitive IAM role assignments and avoid relying solely on IAM for data exfiltration defense.
Least privilege requires fine-grained roles, while VPC Service Controls are necessary to prevent exfiltration by legitimate accounts.

Anahtar Kavram

Centralized Security Audit Logging and Data Access Control
Soru 644Soru

An enterprise organization is deploying a multi-VPC topology in Google Cloud consisting of a Central Hub VPC and two separate workload networks: Workload-VPC-A and Workload-VPC-B. The Central Hub VPC connects to an on-premises data center using a Dedicated Interconnect with Cloud Router configured for global dynamic routing. The network team has established VPC Network Peering between Workload-VPC-A and the Central Hub VPC, as well as between Workload-VPC-B and the Central Hub VPC, enabling custom route exchange on both peering connections. The architecture team mandates that Workload-VPC-A and Workload-VPC-B must be able to communicate with each other directly while retaining connectivity to the on-premises network. Which configuration accurately satisfies these requirements in accordance with Google Cloud networking rules?

Cevabı ve açıklamayı göster

Cevap: Establish a direct VPC Network Peering link between Workload-VPC-A and Workload-VPC-B for inter-workload communication, while maintaining the existing hub-and-spoke VPC Network Peering links with custom route import/export enabled to access the on-premises network.

Cevap

Establish a direct VPC Network Peering link between Workload-VPC-A and Workload-VPC-B for inter-workload communication, while maintaining the existing hub-and-spoke VPC Network Peering links with custom route import/export enabled to access the on-premises network.
VPC Network Peering in Google Cloud is strictly non-transitive. If Workload-VPC-A and Workload-VPC-B need to communicate directly, a direct VPC Network Peering link between them is necessary. Additionally, to allow instances in spoke VPCs to access on-premises networks connected via Dedicated Interconnect in the hub VPC, custom route export must be enabled on the hub side and custom route import must be enabled on the spoke side.

Adım Adım Çözüm

1
Analyze the network transitivity requirements for VPC Network Peering.
Recognize that VPC Network Peering does not support transitive routing (VPC A peering with VPC B, and VPC B peering with VPC C does not allow VPC A to reach VPC C).
Google Cloud VPC Network Peering rules strictly prohibit packets from traveling through an intermediate peered network.
2
Determine the requirement for inter-spoke communication.
Direct VPC Network Peering between Workload-VPC-A and Workload-VPC-B must be provisioned.
Direct peering enables full-mesh connectivity between the two workload networks for low-latency, internal IP communication.
3
Determine the requirement for hybrid connectivity access.
Enable custom route import and export on the VPC Peering connections between the hub and spoke VPCs.
This allows Cloud Router in the Central Hub VPC to advertise learned on-premises Dedicated Interconnect routes to the spoke VPCs.

Anahtar Kavram

VPC Network Peering Non-Transitivity and Hybrid Custom Route Exchange
Tahmini Süre:2m 0s
Soru 645Soru

An organization wants to configure Customer-Managed Encryption Keys (CMEK) using Cloud KMS to protect sensitive data stored in a Cloud Storage bucket. Which two actions must the security team perform to successfully implement CMEK? (Select TWO.)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Grant the Cloud KMS CryptoKey Encrypter/Decrypter role to the Cloud Storage service agent account.; Configure the Cloud Storage bucket default encryption setting to reference the Cloud KMS key resource identifier.

Cevap

Granting the Cloud KMS CryptoKey Encrypter/Decrypter role to the Cloud Storage service agent account and setting the Cloud KMS key resource identifier as the default encryption key on the Cloud Storage bucket.
Implementing CMEK for Cloud Storage requires granting the Cloud Storage service agent the specific Cloud KMS CryptoKey Encrypter/Decrypter role and referencing the Cloud KMS key resource ID on the bucket configuration.

Adım Adım Çözüm

1
Identify key management permissions required by Cloud Storage for CMEK integration.
The Cloud Storage service agent requires the Cloud KMS CryptoKey Encrypter/Decrypter role on the Cloud KMS key.
Google Cloud service agents use service-specific service accounts to execute operations like key encryption and decryption on behalf of users.
2
Apply the key reference configuration to the target Cloud Storage bucket.
The bucket default encryption configuration points to the Cloud KMS key resource name.
This guarantees all newly uploaded objects are encrypted with the specified CMEK key.

Anahtar Kavram

Customer-Managed Encryption Keys (CMEK) setup for Cloud Storage
Soru 646Soru

A fintech company needs to establish a secure hybrid connection between its on-premises data center and a Google Cloud VPC to migrate non-critical internal workloads. The expected bandwidth will not exceed 500 Mbps, but the connection requires encrypted IPsec transit and dynamic BGP routing. Which hybrid connectivity solution should the Cloud Architect recommend to meet these requirements with minimal setup time and cost?

Cevabı ve açıklamayı göster

Cevap: Deploy an HA Cloud VPN gateway with active-active IPsec tunnels connected to a Cloud Router.

Cevap

Deploy an HA Cloud VPN gateway with active-active IPsec tunnels connected to a Cloud Router.
Deploying an HA Cloud VPN gateway with active-active IPsec tunnels connected to a Cloud Router delivers high-availability hybrid connectivity with native IPsec encryption and dynamic BGP routing. Because the bandwidth requirement is 500 Mbps, HA Cloud VPN meets all functional and security requirements without the provisioning delay or high costs of Dedicated Interconnect.

Adım Adım Çözüm

1
Evaluate throughput and connection requirements.
The target bandwidth requirement of 500 Mbps is well within the 3 Gbps per tunnel limit of Cloud VPN.
Provisioning physical interconnect circuits for sub-1 Gbps traffic introduces unnecessary financial overhead and lead time.
2
Verify security and dynamic routing requirements.
HA Cloud VPN natively encrypts traffic using IPsec over the public internet and integrates with Cloud Router for dynamic BGP route exchanges.
This satisfies both the encryption in transit requirement and dynamic BGP routing requirement with minimal complexity.

Anahtar Kavram

Selecting appropriate hybrid connectivity options based on bandwidth, encryption, and operational complexity
Soru 647Soru

A multinational financial enterprise is architecting an analytics and data persistence pipeline on Google Cloud using Cloud SQL and BigQuery. Strict regulatory compliance requirements dictate that all data at rest must be encrypted using cryptographic key material that is stored and generated exclusively within the organization's existing on-premises Hardware Security Module (HSM). The security policy strictly prohibits raw key material from ever being stored within Google Cloud infrastructure, yet GCP services must perform automated encryption and decryption operations seamlessly. Additionally, administrative access must follow the principle of least privilege. Which encryption architecture and identity configuration satisfies all compliance and security requirements?

Cevabı ve açıklamayı göster

Cevap: Configure Customer-Managed Encryption Keys (CMEK) backed by Cloud EKM (External Key Manager) to reference external key handles residing in the on-premises HSM, and grant the Cloud KMS CryptoKey Encrypter/Decrypter role (roles/cloudkms.cryptoKeyEncrypterDecrypter) on the key to the respective GCP service agents.

Cevap

Configure Customer-Managed Encryption Keys (CMEK) backed by Cloud EKM (External Key Manager) to reference external key handles residing in the on-premises HSM, and grant the Cloud KMS CryptoKey Encrypter/Decrypter role (roles/cloudkms.cryptoKeyEncrypterDecrypter) on the key to the respective GCP service agents.
The correct solution uses Customer-Managed Encryption Keys (CMEK) integrated with Cloud EKM (External Key Manager). This setup enables Google Cloud services (such as BigQuery and Cloud SQL) to leverage keys stored in an external, on-premises Hardware Security Module (HSM), keeping key material strictly outside Google Cloud. Furthermore, granting the predefined `roles/cloudkms.cryptoKeyEncrypterDecrypter` role to the specific service agents enforces minimal necessary access permissions.

Adım Adım Çözüm

1
Analyze key storage and governance requirements.
The requirement explicitly states key material must be generated and stored exclusively within an on-premises HSM, with raw keys never entering Google Cloud.
Cloud EKM (External Key Manager) is designed specifically to allow Google Cloud services to encrypt/decrypt data using keys held in external key management systems outside GCP.
2
Evaluate service compatibility and integration method.
CMEK integration with Cloud EKM allows services like BigQuery and Cloud SQL to communicate with Cloud KMS, which proxies requests to the external HSM using Cloud EKM.
CSEK is not supported for BigQuery or Cloud SQL, making CMEK via Cloud EKM the required architectural solution.
3
Determine least privilege IAM access model.
GCP service agents for BigQuery and Cloud SQL require permissions to perform encrypter and decrypter operations.
Assigning `roles/cloudkms.cryptoKeyEncrypterDecrypter` directly to the service agent accounts on the specific KMS key enforces the principle of least privilege, avoiding primitive project-level roles.

Anahtar Kavram

Cloud EKM with CMEK for On-Premises Key Governance and Least-Privilege Service Agent IAM Roles
Soru 648Soru

A software development team migrated a legacy application to Google Cloud and granted primitive Owner roles to several application service accounts to accelerate initial deployment. An architectural review identified this setup as a critical security technical debt risk. Which action should the cloud architect recommend to mitigate this technical debt?

Cevabı ve açıklamayı göster

Cevap: Audit the exact permissions used by the application and replace the primitive roles on the service accounts with specific predefined or fine-grained custom IAM roles.

Cevap

Audit the exact permissions used by the application and replace the primitive roles on the service accounts with specific predefined or fine-grained custom IAM roles.
Replacing primitive roles with fine-grained predefined or custom roles directly remediates security technical debt by removing unneeded high-privilege access while ensuring the application maintains necessary operations.

Adım Adım Çözüm

1
Analyze the identified technical debt item
Identified that service accounts possess broad primitive Owner roles granted during rapid initial deployment.
Primitive roles grant excessive privileges across an entire project, creating a security risk and accumulating technical debt.
2
Evaluate GCP recommended mitigation strategies
Determine required minimal permissions using IAM Recommender or Cloud Logging.
Technical debt in identity management is resolved by transitioning to least-privilege predefined or custom IAM roles.
3
Select optimal architecture solution
Replace primitive Owner roles with fine-grained roles explicitly tailored to application needs.
This directly remediates the debt without adding unnecessary architectural complexity.

Anahtar Kavram

Assessing and Mitigating IAM Technical Debt via Least Privilege
Tahmini Süre:1m 0s
Soru 649Soru

A financial technology company is establishing central security guardrails for a specific Google Cloud folder containing sensitive payment processing workloads. The enterprise security policy dictates that no Compute Engine virtual machine instances created within this folder should have external IP addresses attached, preventing direct internet accessibility. To avoid disrupting existing production services, the security team needs to audit non-compliant resources first before enforcing strict blocking across all projects in the folder. Which architectural approach meets these governance requirements?

Cevabı ve açıklamayı göster

Cevap: Apply the compute.vmExternalIpAccess organization policy constraint at the target folder level in dry-run mode, monitor violations using Cloud Audit Logs, and then transition the constraint to enforced mode.

Cevap

Apply the compute.vmExternalIpAccess organization policy constraint at the target folder level in dry-run mode, monitor violations using Cloud Audit Logs, and then transition the constraint to enforced mode.
Organization Policies provide centralized, programmatic control over organization resources. The boolean constraint compute.vmExternalIpAccess specifically controls whether Compute Engine VM instances within the resource hierarchy can be configured with external IP addresses. Applying this constraint at the folder level ensures all projects within that folder inherit the guardrail. Setting the constraint to dry-run mode generates audit log events for non-compliant resources without disrupting existing infrastructure or blocking deployment pipelines during evaluation.

Adım Adım Çözüm

1
Identify the appropriate governance mechanism for resource configuration constraints.
Recognize that Google Cloud Organization Policies (specifically compute.vmExternalIpAccess) are designed to restrict specific resource configuration attributes across the resource hierarchy.
IAM roles control identity access rights, and VPC Service Controls protect API perimeters, whereas Organization Policies restrict resource creation properties.
2
Determine the appropriate scope for policy application.
Apply the policy constraint at the specific target Folder node containing payment workloads.
Inheritance will apply the policy to all current and future projects beneath that folder without impacting unrelated folders.
3
Select the policy execution mode for non-disruptive auditing.
Configure the organization policy constraint in dry-run mode initially.
Dry-run policy evaluation logs violations to Cloud Audit Logs without blocking resource creation or interrupting running production workloads, allowing safe operational validation prior to full enforcement.

Anahtar Kavram

Organization Policy Constraints and Dry-Run Enforcement
Soru 650Soru

A healthcare organization is migrating an on-premises PostgreSQL database to Cloud SQL. Corporate governance mandates that all encryption keys protecting sensitive patient records must reside strictly within an on-premises physical Hardware Security Module (HSM) outside of Google Cloud. Additionally, key access must follow the principle of least privilege, granting permission only to the necessary service identity. Which key management architecture and IAM configuration meets these regulatory requirements?

Cevabı ve açıklamayı göster

Cevap: Configure Cloud SQL to use Customer-Managed Encryption Keys (CMEK) integrated with Cloud EKM pointing to the on-premises HSM, and grant the Cloud SQL Service Agent the Cloud KMS CryptoKey Encrypter/Decrypter role on the key.

Cevap

Configure Cloud SQL with CMEK integrated with Cloud EKM pointing to the on-premises HSM, and assign the Cloud KMS CryptoKey Encrypter/Decrypter role to the Cloud SQL Service Agent.
Customer-Managed Encryption Keys (CMEK) integrated with Cloud EKM (External Key Manager) allow Google Cloud services like Cloud SQL to perform data encryption and decryption while holding the root cryptographic keys within an external, on-premises Hardware Security Module (HSM). Granting the Cloud KMS CryptoKey Encrypter/Decrypter role strictly to the Cloud SQL Service Agent satisfies least-privilege security requirements.

Adım Adım Çözüm

1
Analyze key storage location requirements
Identified that keys must physically reside inside an on-premises HSM, requiring Cloud External Key Manager (Cloud EKM).
Cloud EKM allows Google Cloud services to protect data at rest using keys stored in supported external key management systems outside Google infrastructure.
2
Evaluate service compatibility with key management options
Selected CMEK combined with Cloud EKM for Cloud SQL.
Cloud SQL supports CMEK with Cloud KMS and Cloud EKM, whereas Customer-Supplied Encryption Keys (CSEK) are not supported on Cloud SQL.
3
Determine appropriate Identity and Access Management (IAM) role
Granted the Cloud KMS CryptoKey Encrypter/Decrypter role specifically to the Cloud SQL Service Agent.
Assigning predefined fine-grained roles to the specific service agent enforces least privilege, avoiding over-privileged primitive roles like Owner or Editor.

Anahtar Kavram

Cloud EKM with CMEK for external key sovereignty and fine-grained Cloud KMS IAM roles
Soru 651Soru

An enterprise SaaS company manages its Google Cloud infrastructure using an Organization resource hierarchy with two primary folders: `Core-Services` and `Development`. To meet strict corporate compliance standards, the security team must enforce two governance rules:
1. Prevent the creation of external service account keys for all projects located within the `Development` folder.
2. Prevent Compute Engine instances throughout the entire organization from obtaining public IP addresses, with a temporary exception for a single legacy diagnostics project under `Development` that requires public connectivity.

How should the security team configure Google Cloud Organization Policies to enforce these constraints with minimal administrative effort while respecting resource hierarchy inheritance?

Cevabı ve açıklamayı göster

Cevap: Apply the boolean constraint `constraints/iam.disableServiceAccountKeyCreation` at the `Development` folder level. Apply the list constraint `constraints/compute.vmExternalIpAccess` at the Organization root node set to `Deny All`, and configure an Organization Policy rule on the legacy diagnostics project node set to `Allow All`.

Cevap

Enforce `constraints/iam.disableServiceAccountKeyCreation` on the target folder, enforce `constraints/compute.vmExternalIpAccess` as `Deny All` at the Organization root, and apply a policy override set to `Allow All` on the specific project requiring an exception.
Organization Policies allow centralized governance across the GCP resource hierarchy. Defining the boolean constraint for disabling service account key creation at the `Development` folder node applies restriction to all child projects under that folder. Defining the external IP list constraint at the Organization root establishes an organization-wide default deny behavior, while applying an explicit policy rule set to `Allow All` at the legacy project node overrides parent inheritance for that specific project only.

Adım Adım Çözüm

1
Analyze resource hierarchy placement for folder-scoped guardrails.
Identify that applying `constraints/iam.disableServiceAccountKeyCreation` at the `Development` folder node automatically enforces key creation restriction on all descendant projects via inheritance.
Organization policies inherit downwards through the resource hierarchy (Organization → Folder → Project).
2
Evaluate global baseline policies versus localized exceptions.
Apply `constraints/compute.vmExternalIpAccess` with a `Deny All` rule at the Organization level to secure all existing and future projects by default.
Setting baseline security constraints at the highest hierarchy node ensures comprehensive coverage across the entire organization.
3
Configure the policy exception using hierarchical inheritance rules.
Set an explicit policy override on the legacy diagnostics project node to allow VM external IPs (`Allow All`).
Explicit policy rules defined at child nodes override inherited policies from parent nodes for that specific resource.

Anahtar Kavram

GCP Organization Policy inheritance and constraint override mechanism across the resource hierarchy.
Soru 652Soru

An enterprise architecture team is automating the provisioning of managed relational database instances and object storage buckets using Infrastructure as Code (Terraform) within a multi-developer CI/CD pipeline. Corporate governance policies dictate that all storage and database assets must utilize key management controls where keys can be revoked or rotated within Google Cloud without requiring raw cryptographic keys to be handled or transmitted by developers. Additionally, the execution pipeline must prevent state file corruption during simultaneous deployments and safeguard infrastructure history against accidental deletions. Which TWO actions should the team implement in their provisioning configuration? (Select TWO.)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Configure a Cloud Storage remote backend for Terraform with object versioning enabled and native state locking to ensure state integrity across automated runs.; Grant resource service accounts the Cloud KMS CryptoKey Encrypter/Decrypter role and pass the Customer-Managed Encryption Key (CMEK) resource IDs into the Terraform resource configurations.

Cevap

The team should configure a Cloud Storage remote backend with object versioning and state locking for Terraform, and grant service accounts the Cloud KMS CryptoKey Encrypter/Decrypter role while specifying CMEK resource IDs in the resource definitions.
Configuring a Cloud Storage remote backend with state locking and object versioning ensures concurrent CI/CD pipeline runs cannot corrupt the Terraform state file, while enabling recovery of previous state versions. Using Customer-Managed Encryption Keys (CMEK) via Cloud KMS fulfills key governance requirements by enabling key lifecycle management and revocation within GCP without requiring developers to manage raw cryptographic key bytes.

Adım Adım Çözüm

1
Evaluate state storage requirements for multi-developer CI/CD automated deployments.
Identify that a centralized Cloud Storage backend with versioning and object locking prevents state race conditions and enables rollback.
Unversioned local state files lead to concurrency collisions and state loss across ephemeral CI/CD containers.
2
Evaluate encryption requirements under corporate key governance policy.
Select Customer-Managed Encryption Keys (CMEK) via Cloud KMS instead of Customer-Supplied Encryption Keys (CSEK).
CMEK allows key management, rotation, and revocation within Google Cloud KMS without requiring developers to handle raw 256-bit keys.
3
Bind appropriate IAM roles to resource service accounts.
Grant roles/cloudkms.cryptoKeyEncrypterDecrypter to the database and storage service accounts for the designated CMEK key.
Services require explicit cryptographic permissions to encrypt and decrypt underlying persistent disks and storage objects upon provisioning.

Anahtar Kavram

Terraform State Management and CMEK Integration for Provisioned Infrastructure
Soru 653Soru

An online retail enterprise uses Google Cloud resource hierarchy to manage environments. To reduce risks associated with unauthorized data movement, the security team needs to prevent service accounts created in non-production projects from attached usage or impersonation across project boundaries into production projects. This restriction must apply to all existing and future projects under the 'Non-Production' folder hierarchy without interrupting production service account workflows. Which solution should the principal cloud architect recommend?

Cevabı ve açıklamayı göster

Cevap: Enforce the boolean Organization Policy constraint `constraints/iam.disableCrossProjectServiceAccountUsage` at the 'Non-Production' folder level.

Cevap

Enforce the boolean Organization Policy constraint `constraints/iam.disableCrossProjectServiceAccountUsage` at the 'Non-Production' folder level.
Enforcing `constraints/iam.disableCrossProjectServiceAccountUsage` at the folder level is the Google-recommended approach to systematically prevent resources in child projects under that folder from attaching or using service accounts owned by external projects.

Adım Adım Çözüm

1
Identify the governance requirement.
The requirement mandates preventing service accounts belonging to one project from being attached to resources or used across project boundaries within a specific folder hierarchy.
Preventing cross-project service account usage limits the lateral movement of compromised identities between non-production and production environments.
2
Evaluate the appropriate governance mechanism in Google Cloud.
Organization Policy constraints enforce centralized guardrails across resource hierarchy nodes (Organization, Folder, or Project).
The predefined boolean constraint `constraints/iam.disableCrossProjectServiceAccountUsage` specifically disables attaching service accounts from other projects.
3
Select the correct resource hierarchy target node.
Enforcing the policy at the 'Non-Production' folder level ensures all current and future projects inherited under that folder automatically adhere to the guardrail.
Inheritance down the Google Cloud resource hierarchy provides central enforcement without requiring per-project manual configuration.

Anahtar Kavram

Organization Policy Constraints and Resource Hierarchy Inheritance
Soru 654Soru

An enterprise architectural team is designing a modernized data ingestion pipeline on Google Cloud. The system includes two separate workloads with distinct runtime requirements:

1. Event Ingestion Webhook: A lightweight HTTP service that receives intermittent data payloads, experiences rapid traffic spikes, requires scale-to-zero capacity during idle periods, and must minimize operational management overhead.
2. Custom Analytics Engine: A long-running backend data processing application that requires specific Linux kernel parameters (`sysctl` network tuning) and direct hardware device driver access.

Which TWO platform architectural decisions should you recommend to meet these requirements efficiently?

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Deploy the Event Ingestion Webhook on Cloud Run to leverage fully managed serverless container execution with automatic scaling to zero.; Deploy the Custom Analytics Engine on Google Kubernetes Engine (GKE) with custom node pools configured for kernel tuning and specialized node setup.

Cevap

Deploying the Event Ingestion Webhook on Cloud Run and deploying the Custom Analytics Engine on Google Kubernetes Engine (GKE) with custom node configurations represent the optimal architectural design.
Cloud Run is optimized for stateless HTTP containers requiring automatic scaling to zero with zero infrastructure management. Google Kubernetes Engine (GKE) provides full node-level access and daemonset capabilities to apply custom sysctl kernel parameters and OS drivers for specialized batch processing.

Adım Adım Çözüm

1
Analyze the requirements for the Event Ingestion Webhook service.
The webhook service is stateless, handles HTTP traffic, experiences variable/intermittent load, requires scaling to zero instances, and demands low operational overhead.
Cloud Run provides serverless container hosting that automatically scales down to zero when no requests arrive and requires no cluster management.
2
Analyze the requirements for the Custom Analytics Engine.
The engine requires custom host environment settings (`sysctl` network parameter tuning) and hardware access.
Container sandboxes like Cloud Run do not grant kernel modification permissions. GKE nodes (or Compute Engine instances) are required when low-level OS/kernel customizations are mandatory.
3
Select the optimal combination of compute platforms.
Cloud Run for the webhook service and GKE with custom node configurations for the analytics engine.
This combination minimizes operational cost for the stateless endpoint while satisfying the low-level technical constraints of the processing engine.

Anahtar Kavram

Selecting GCP Compute Platforms Based on Workload Characteristics and OS Level Access
Tahmini Süre:2m 0s
Soru 655Soru

A genomic research organization needs to migrate an on-premises data archive of 65 TB65\text{ TB} of uncompressed sequence files and an operational 400 GB400\text{ GB} PostgreSQL database to Google Cloud. The organization has an operational 1 Gbps1\text{ Gbps} Dedicated Interconnect with 600 Mbps600\text{ Mbps} of unallocated bandwidth dedicated to migration tasks. The business requirement dictates a maximum database cutover downtime of 2 hours2\text{ hours}. Which data transfer and database migration strategy should the cloud architect recommend?

Cevabı ve açıklamayı göster

Cevap: Use Storage Transfer Service over the Dedicated Interconnect to move the 65 TB65\text{ TB} archive, and use Database Migration Service (DMS) for continuous replication of the PostgreSQL database to Cloud SQL.

Cevap

Use Storage Transfer Service over the Dedicated Interconnect to move the archive data, and use Database Migration Service (DMS) with continuous replication for the PostgreSQL database migration to Cloud SQL.
Transferring 65 TB65\text{ TB} over an available 600 Mbps600\text{ Mbps} connection takes approximately 10 days online, making Storage Transfer Service over the existing Dedicated Interconnect the optimal choice without incurring physical device shipping delays. For the PostgreSQL database, Database Migration Service (DMS) provides continuous CDC replication to Cloud SQL, allowing the target instance to sync continuously until a quick cutover is performed within the 2-hour downtime window.

Adım Adım Çözüm

1
Calculate data transfer time for the unstructured archive online vs offline
Transferring 65 TB65\text{ TB} (520,000 Gbits520,000\text{ Gbits}) at 600 Mbps600\text{ Mbps} takes 520,0000.6866,667 seconds10 days\frac{520,000}{0.6} \approx 866,667\text{ seconds} \approx 10\text{ days}.
Because 10 days is well within standard online migration planning windows, an online transfer via Storage Transfer Service over the existing Dedicated Interconnect avoids physical appliance logistics.
2
Select the database migration tool based on downtime constraints
Database Migration Service (DMS) enables continuous change data capture (CDC) replication from on-premises PostgreSQL to Cloud SQL for PostgreSQL.
Continuous replication allows the target Cloud SQL database to remain synchronized, enabling cutover in minutes and staying strictly within the 2-hour downtime requirement.

Anahtar Kavram

Selecting GCP data transfer and database migration tools based on network bandwidth calculations, dataset scale, and downtime windows.
Soru 656Soru

A logistics enterprise is deploying an automated deployment pipeline to provision a database for order management limited to a single GCP region. The application requires ACID transactional consistency to handle localized regional traffic, a strict RPO of zero across two zones, and compliance mandates requiring storage encryption keys to be managed directly within Cloud KMS. Furthermore, the infrastructure operations team must manage the deployment declaratively using Terraform without risking local state file corruption or concurrent state writes. Which configuration approach fulfills these database provisioning and infrastructure management requirements?

Cevabı ve açıklamayı göster

Cevap: Provision a Cloud SQL for PostgreSQL High Availability instance configured with Customer-Managed Encryption Keys (CMEK) via Cloud KMS, and configure the Terraform remote backend to store state in a Cloud Storage bucket with object versioning and state locking enabled.

Cevap

Provision a Cloud SQL for PostgreSQL High Availability instance configured with Customer-Managed Encryption Keys (CMEK) via Cloud KMS, and store Terraform state in a Cloud Storage backend with object versioning and locking enabled.
Provisioning Cloud SQL for PostgreSQL in a High Availability configuration satisfies single-region relational storage requirements with zonal redundancy. Utilizing Customer-Managed Encryption Keys (CMEK) satisfies the requirement to leverage Cloud KMS for key management. Using a Cloud Storage bucket with object versioning and state locking for the Terraform backend ensures state security, consistency, and protection against concurrent execution conflicts.

Adım Adım Çözüm

1
Analyze regional storage and database requirement boundary.
Cloud SQL for PostgreSQL in High Availability (HA) regional configuration meets ACID requirements with automatic zonal failover (RPO=0) without incurring multi-region Cloud Spanner costs.
Cloud Spanner is designed for globally distributed workloads; Cloud SQL HA is optimized for single-region relational workloads.
2
Evaluate key management compliance requirement.
Configure CMEK using Cloud KMS key rings and service account permissions.
CMEK allows central lifecycle governance inside Google Cloud KMS, whereas CSEK requires raw key management outside Cloud KMS.
3
Determine Infrastructure as Code remote state management pattern.
Configure Terraform backend to use Google Cloud Storage (gcs) with object versioning and native state locking.
Remote state backends in GCS prevent race conditions, state corruption, and credential exposure associated with local or version-control state storage.

Anahtar Kavram

Provisioning Cloud Database Infrastructure with CMEK and IaC Remote State Locking
Soru 657Soru

A digital health platform based in Tokyo must guarantee that all newly created Cloud Storage buckets remain physically located within the asia-northeast1 region to adhere to local data residency compliance mandates. Which Google Cloud solution should the cloud architect implement to automatically enforce this restriction across all current and future projects?

Cevabı ve açıklamayı göster

Cevap: Define an Organization Policy using the Resource Locations constraint with allowed values set to asia-northeast1.

Cevap

Define an Organization Policy using the Resource Locations constraint with allowed values set to asia-northeast1.
The Resource Locations constraint in Google Cloud Organization Policies (`constraints/gcp.resourceLocations`) allows cloud architects to specify the exact geographic locations where developers and automated tools are permitted to deploy GCP resources, ensuring strict adherence to data sovereignty regulations.

Adım Adım Çözüm

1
Identify the data sovereignty requirement
Resource creation must be limited strictly to the asia-northeast1 region.
Compliance rules mandate local physical data residency boundaries.
2
Evaluate GCP governance controls for location enforcement
The Resource Locations organization policy constraint (constraints/gcp.resourceLocations) explicitly restricts resource creation locations across the resource hierarchy.
Organization Policies establish centralized policy guardrails that apply automatically across projects.

Anahtar Kavram

Data Sovereignty via Resource Locations Organization Policy
Soru 658Soru

A company deploying Compute Engine virtual machines requires that persistent disks are encrypted using raw 256-bit AES encryption keys generated in their local data center. Security policy dictates that Google Cloud must never store these key strings at rest on Google infrastructure under any circumstances, and the keys must be supplied during disk creation and attach operations. Which encryption mechanism meets these requirements?

Cevabı ve açıklamayı göster

Cevap: Customer-Supplied Encryption Keys (CSEK)

Cevap

Customer-Supplied Encryption Keys (CSEK) meet the requirement because the customer supplies their own raw 256-bit AES keys with each API call, and Google Cloud never persists these keys to disk.
Customer-Supplied Encryption Keys (CSEK) allow organizations to provide raw AES-256 keys directly to Compute Engine when creating or attaching disks. Google uses the key in memory to perform encryption/decryption operations and discards it immediately without writing the key material to persistent storage.

Adım Adım Çözüm

1
Analyze key management requirements
The requirement specifies raw AES-256 keys generated on-premises that Google must never persist at rest.
Identifying key persistence and management boundary rules is critical for selecting the correct GCP encryption implementation.
2
Compare GCP encryption options against requirements
CSEK requires the caller to provide the key string for disk read/write/attach requests, while CMEK stores keys in Cloud KMS.
Only CSEK keeps key persistence completely off Google Cloud storage.

Anahtar Kavram

Customer-Supplied Encryption Keys (CSEK) vs Customer-Managed Encryption Keys (CMEK)
Soru 659Soru

A global logistics firm structures its Google Cloud environment using an Organization node with folders for separate business units, including a top-level folder named 'FleetManagement'. A telemetry processing workload running on Compute Engine instances within a specific project under 'FleetManagement' requires reading telemetry data files from Cloud Storage buckets across all current and future projects within the 'FleetManagement' folder tree. Additionally, the application must sign Cloud Storage URL tokens for short-lived downstream download access without possessing administrative permissions over IAM policies or resource configurations. Which access control design best satisfies these requirements while strictly adhering to the principle of least privilege?

Cevabı ve açıklamayı göster

Cevap: Bind the predefined role Storage Object Viewer (roles/storage.objectViewer) to the telemetry workload's service account at the 'FleetManagement' folder level, and grant the Service Account Token Creator role (roles/iam.serviceAccountTokenCreator) on the workload's service account to itself.

Cevap

Grant the predefined Storage Object Viewer role at the 'FleetManagement' folder level and assign the Service Account Token Creator role directly on the workload's service account.
Binding the Storage Object Viewer role at the folder level leverages resource hierarchy inheritance so that all current and future projects beneath the 'FleetManagement' folder automatically grant read access to storage objects. Additionally, granting the Service Account Token Creator role directly on the service account identity allows the application to call the signBlob API and generate signed URLs for secure downstream access while satisfying the principle of least privilege.

Adım Adım Çözüm

1
Determine the optimal resource hierarchy scope for permission inheritance
Binding permissions at the 'FleetManagement' folder level ensures all nested projects automatically inherit read access without per-project maintenance overhead.
Google Cloud IAM policy evaluation unions permissions top-down through the resource hierarchy.
2
Select fine-grained predefined roles over primitive or administrative roles
Storage Object Viewer (roles/storage.objectViewer) grants read-only access to storage objects without allowing modification or deletion.
Primitive roles like Viewer or administrative roles like Storage Object Admin violate least privilege.
3
Configure permissions for generating signed URLs
Assigning Service Account Token Creator (roles/iam.serviceAccountTokenCreator) on the identity resource enables blob signing without granting full service account management rights.
Service Account Admin grants unnecessary full administrative permissions over service accounts.

Anahtar Kavram

Resource hierarchy IAM inheritance and targeted service account impersonation/token creation roles.
Soru 660Soru

An enterprise organization is provisioning a global multi-project Google Cloud network topology across `us-central1` and `europe-west1`. The architecture utilizes a Shared VPC Host Project connecting multiple Service Projects, along with an on-premises data center connected via Cloud Interconnect. The networking team must ensure continuous dynamic route propagation across all regions and hybrid links, alongside secure private connectivity to Google Cloud APIs from workloads that lack external IP addresses. Which TWO configuration steps must be implemented to satisfy these networking and access requirements? (Select TWO.)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Set the VPC network dynamic routing mode to Global and configure Cloud Router in the Host VPC to dynamically exchange BGP routes across regions and hybrid connections.; Enable Private Google Access on internal subnets and provision Private Service Connect endpoints for accessing Google Cloud APIs using internal IP addresses.

Cevap

The correct architecture requires setting the VPC dynamic routing mode to Global with Cloud Router BGP advertising across regions and hybrid links, and enabling Private Google Access alongside Private Service Connect endpoints for secure internal Google API routing.
Global Dynamic Routing enables Cloud Routers in a VPC to learn and advertise routes across all GCP regions and hybrid Interconnect attachments dynamically. In addition, enabling Private Google Access on subnets and configuring Private Service Connect endpoints allows internal VM workloads without external IP addresses to privately access Google API endpoints safely over private RFC 1918 space.

Adım Adım Çözüm

1
Analyze dynamic routing requirements for multi-region and hybrid interconnect topology.
Determined that Regional Dynamic Routing limits route visibility to the local region, whereas Global Dynamic Routing allows Cloud Router to propagate routes across all GCP regions and on-premises BGP sessions.
Global dynamic routing is required for seamless inter-region dynamic route propagation across Dedicated/Partner Interconnect.
2
Evaluate private connectivity options for Google APIs.
Configuring Private Google Access on subnets and deploying Private Service Connect endpoints fulfills the requirement to access Google APIs securely via internal IP space.
Workloads without public IP addresses depend on Private Google Access or Private Service Connect for private API ingestion.
3
Evaluate distractor configurations against Google Cloud VPC constraints.
Identified that VPC Peering transitivity assumptions fail because peering does not support transitive routing; HA VPN cannot meet >10 Gbps bandwidth requirements; and disabling GKE authorized networks breaks security posture.
Eliminating invalid networking choices based on non-transitive peering rules and throughput limits.

Anahtar Kavram

Global Dynamic Routing and Private Access Topology in Google Cloud VPCs
ÖncekiSayfa 33 / 80Sonraki
Tüm alıştırma soruları — Google Cloud Professional Cloud Architect | Examkin