Tüm alıştırma soruları

1598 soru

Soru 101Soru

An enterprise intermodal freight operator is designing a modernized fleet telemetry system on Google Cloud. As the Principal Cloud Architect, you must translate high-level business requirements into a production-ready solution following Google Cloud architecture framework best practices. Place the architectural design phases in the correct sequential order, starting from initial business abstraction down to physical infrastructure deployment.

Öğeleri doğru sıraya koymak için sürükleyin

Cevabı ve açıklamayı göster

Cevap

The correct sequence starts with defining the Conceptual Architecture (functional business capabilities), followed by formulating the Logical Architecture (component boundaries and data flows), specifying the Physical Architecture component mapping (selecting Google Cloud services), and finally executing Physical Resource Deployment (provisioning via Infrastructure-as-Code).
The standard architectural design progression begins with the Conceptual Architecture (establishing high-level functional capabilities from business needs), progresses to the Logical Architecture (defining technology-agnostic data flows, security boundaries, and component interfaces), transitions to Physical Architecture selection (mapping logical blocks to specific Google Cloud services such as Cloud Pub/Sub and Bigtable), and culminates in Physical Deployment (instantiating actual GCP infrastructure via IaC).

Adım Adım Çözüm

1
Identify the conceptual design phase
Map business requirements and SLA/SLO expectations into vendor-neutral functional capabilities.
Designing starts at the highest abstraction layer to ensure alignment with business goals before choosing technical components.
2
Determine the logical component structure
Define data movement patterns, security boundaries, and architectural patterns (e.g., event-driven ingestion, stream processing).
Logical modeling organizes interaction patterns and data contracts without locking into specific Cloud vendor SKUs.
3
Select physical Google Cloud products
Map logical tiers to physical GCP services like Pub/Sub, Cloud Bigtable, BigQuery, and VPC Service Controls.
Physical selection requires matching technical constraints (throughput, latency, compliance) to actual cloud service specs.
4
Provision physical infrastructure
Write and apply declarative IaC templates (Terraform) to deploy VPC networks, IAM roles, KMS keys, and compute clusters.
Deployment is the final execution stage where concrete infrastructure resources are instantiated in the target GCP projects.

Anahtar Kavram

Architectural Abstraction Layers (Conceptual -> Logical -> Physical)
Soru 102Soru

A global media streaming conglomerate is executing a multi-stage migration of its high-throughput video rendering and distribution platform from an on-premises datacenter to Google Cloud. Executive leadership requires strict change governance, demanding zero disruption to active production release cadences while transitioning twelve legacy engineering squads. The platform security policy mandates strict data exfiltration prevention, and compute capacity planning indicates that rendering workloads will require high-count GPU host instances in specific regional zones. Which strategy should the Lead Cloud Architect recommend to align business stakeholder change requirements with Google Cloud technical and operational best practices?

Cevabı ve açıklamayı göster

Cevap: Establish a phased migration framework using fine-grained custom IAM roles for least privilege, submit regional quota increase requests well in advance of deployment waves, and enforce VPC Service Controls perimeters around media storage buckets.

Cevap

Establish a phased migration framework using fine-grained custom IAM roles for least privilege, submit regional quota increase requests well in advance of deployment waves, and enforce VPC Service Controls perimeters around media storage buckets.
The successful cloud architecture strategy aligns organizational change management with GCP technical governance by combining phased operational onboarding, advance quota planning for high-demand GPU resources, and defense-in-depth security using least-privilege IAM custom roles alongside VPC Service Controls to prevent data exfiltration.

Adım Adım Çözüm

1
Analyze business governance and operational change requirements.
Identified the need for phased migration waves and workforce enablement to ensure zero disruption to production release cadences.
Phased rollouts allow legacy teams to adapt smoothly without overwhelming operational bandwidth.
2
Evaluate technical and capacity requirements for specialized rendering workloads.
Determined that high GPU demand requires proactive regional resource quota requests prior to launching infrastructure.
Default quota limits in Google Cloud regions will block compute provisioning if quota increases are not submitted and approved prior to rollout.
3
Formulate security and governance controls meeting enterprise compliance standards.
Combined fine-grained custom IAM roles for granular permissions with VPC Service Controls to prevent unauthorized data movement.
IAM enforces identity-based authorization while VPC Service Controls protect network boundaries against data exfiltration.

Anahtar Kavram

Analyzing Stakeholder Requirements & Organizational Change Management in GCP Architecture
Soru 103Soru

An enterprise organization is migrating a transactional analytics workload to Google Cloud. The compliance team mandates that sensitive data stored in Cloud Storage and BigQuery must be encrypted at rest using Customer-Managed Encryption Keys (CMEK) hosted in Cloud KMS. Additionally, security policy dictates strict separation of duties between key management operations and data processing tasks. Which TWO architectural configuration steps should the cloud security architect perform to satisfy these requirements? (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 on the designated KMS key to the Google-managed Service Agents for Cloud Storage and BigQuery.; Assign the Cloud KMS Admin role to the security administration team while withholding cryptographic encrypter and decrypter roles from them.

Cevap

The architect must grant the Cloud KMS CryptoKey Encrypter/Decrypter role to the Google-managed Service Agents for Cloud Storage and BigQuery, and assign the Cloud KMS Admin role to the security administration team without granting encryption or decryption permissions.
Configuring CMEK for GCP services requires granting the Cloud KMS CryptoKey Encrypter/Decrypter role specifically to the Google-managed service agents for Cloud Storage and BigQuery. Simultaneously, separation of duties is achieved by granting the Cloud KMS Admin role to security personnel while intentionally withholding data decryption roles.

Adım Adım Çözüm

1
Identify the service accounts performing cryptographic operations.
Determine that Google-managed Service Agents (e.g., service-[PROJECT_NUMBER]@gs-project-accounts.iam.gserviceaccount.com) perform CMEK encryption and decryption on behalf of Cloud Storage and BigQuery.
Google Cloud services require dedicated service agent identity permissions to interact with Cloud KMS keys.
2
Apply least-privilege KMS IAM roles for workload service agents.
Grant `roles/cloudkms.cryptoKeyEncrypterDecrypter` on the target CryptoKey to the service agents.
This allows the automated storage services to encrypt and decrypt dataset objects using the specified CMEK key without over-granting administrative rights.
3
Enforce separation of duties for security key administrators.
Assign `roles/cloudkms.admin` to the security team while omitting encrypter/decrypter permissions.
Separating administrative key management from data decryption capabilities ensures key managers cannot read sensitive customer datasets.

Anahtar Kavram

CMEK Service Agent Authorization and Separation of Duties in Cloud KMS
Soru 104Soru

A digital publishing platform hosts its core services on Google Cloud Platform across multiple projects within an organizational hierarchy. The architecture includes steady-state core API services running continuously, unpredictable web traffic spikes during breaking news events, simple stateless web microservices, and standard relational database backends. The enterprise FinOps team requires a cost governance strategy that minimizes overall spend while maintaining operational performance and avoiding wasteful over-provisioning. Which architectural strategy should the Cloud Architect recommend?

Cevabı ve açıklamayı göster

Cevap: Apply Flexible Committed Use Discounts (CUDs) to cover baseline compute across Cloud Run and Compute Engine, leverage Cloud Run for stateless microservices to scale to zero during idle periods, and retain Cloud SQL for standard relational workloads.

Cevap

The optimal solution is to apply Flexible Committed Use Discounts (CUDs) for baseline compute expenditure across Cloud Run and Compute Engine, utilize Cloud Run for simple stateless microservices to leverage scale-to-zero capabilities, and maintain Cloud SQL for standard relational database requirements.
Combining Flexible Committed Use Discounts (CUDs) for continuous baseline spend with serverless scale-to-zero services (Cloud Run) for stateless microservices ensures maximum financial efficiency. Cloud SQL provides the appropriate right-sized cost profile for standard relational data storage.

Adım Adım Çözüm

1
Analyze workload traffic patterns and resource requirements.
Identified steady-state baseline API demand, unpredictable breaking news spikes, simple stateless microservices, and standard relational database needs.
Different compute and storage patterns require tailored cost optimization mechanisms rather than a one-size-fits-all commitment.
2
Evaluate compute commitment models and serverless options.
Flexible CUDs cover baseline spend across multiple compute services, while Cloud Run automatically scales to zero for variable stateless microservices.
Flexible commitments prevent locking into rigid VM instance types, and serverless scaling eliminates cost overhead during low-traffic periods.
3
Align database selections with architectural and cost requirements.
Cloud SQL satisfies standard relational database needs cost-effectively without requiring high-cost global Spanner provisioning.
Avoiding over-engineered database solutions preserves capital while meeting standard uptime and performance SLAs.

Anahtar Kavram

FinOps Cost Optimization and Compute Commitment Models
Soru 105Soru

An organization is migrating an on-premises deployment pipeline to interact with Google Cloud resources. The pipeline needs to fetch database credentials stored in Google Cloud Secret Manager to deploy application updates. Organization security governance strictly forbids the creation of exportable long-lived service account keys and mandates strict adherence to the principle of least privilege. Which solution should the cloud architect implement to meet these requirements securely?

Cevabı ve açıklamayı göster

Cevap: Configure Workload Identity Federation using the on-premises environment's OpenID Connect (OIDC) identity provider, allowing the pipeline to exchange short-lived tokens and impersonate a GCP service account granted the Secret Manager Secret Accessor role on the specific secret.

Cevap

Configure Workload Identity Federation with an external OIDC provider to allow short-lived service account token exchange, and grant the service account the Secret Manager Secret Accessor role on the specific secret.
Workload Identity Federation allows external workloads running outside Google Cloud to authenticate securely using short-lived tokens from an external OIDC provider, satisfying the requirement to eliminate long-lived service account keys. Coupling identity federation with the fine-grained Secret Manager Secret Accessor role bound to a specific secret enforces least-privilege access controls.

Adım Adım Çözüm

1
Eliminate static service account keys
Avoid exportable long-lived JSON keys by establishing Workload Identity Federation with the external on-premises OIDC identity provider.
Security governance strictly prohibits long-lived service account key files due to risks of credential exposure and compliance violations.
2
Configure identity federation and impersonation
Map external OIDC identity claims to a target GCP service account using workload identity pools and providers.
Allows on-premises workloads to exchange native short-lived identity tokens for short-lived Google Cloud federated access tokens.
3
Apply least privilege IAM permissions
Grant the targeted service account the `roles/secretmanager.secretAccessor` role specifically scoped to the required secret resource.
Ensures the deployment pipeline can read secret values without receiving excessive project-level or administrative permissions.

Anahtar Kavram

Workload Identity Federation & Service Account Lifecycle Governance
Tahmini Süre:2m 0s
Soru 106Soru

An enterprise online video platform hosts its core subscriber session management service on Google Cloud across a primary region (us-east1) and a DR region (us-west1). The business has established a strict 15-minute Recovery Time Objective (RTO) and near-zero Recovery Point Objective (RPO). As part of developing standard Disaster Recovery (DR) validation procedures, the lead cloud architect needs to design a simulation process that verifies regional failover capability without risking live production traffic or encountering unexpected resource limits during an actual regional outage. Which validation procedure should the cloud architect implement?

Cevabı ve açıklamayı göster

Cevap: Perform scheduled automated failover drills in a isolated staging environment mirroring production, verifying that regional quotas and capacity reservations in us-west1 are validated prior to routing synthetic traffic, while validating automated DNS updates and database replication lag metric bounds.

Cevap

The correct procedure is to execute scheduled automated failover drills in an isolated staging environment mirroring production, verifying regional quota increases and capacity reservations in us-west1 before running synthetic traffic tests, while validating DNS propagation and replication lag metrics.
Executing scheduled failover tests using synthetic workloads in an isolated staging environment ensures complete validation of DNS propagation, database replication lag, and automated failover scripts. Pre-allocating capacity reservations and auditing regional resource quotas in the target region prevents unexpected deployment failures during failover.

Adım Adım Çözüm

1
Assess DR requirements
Identified strict RTO (15 minutes) and RPO (near-zero) constraints alongside the requirement to prevent live production disruption during testing.
Validation procedures must accurately test failover mechanics without breaking live user traffic or failing due to unverified capacity limits.
2
Evaluate regional capacity and quota validation steps
Pre-validating regional quota bounds and active capacity reservations in the destination region (us-west1) ensures that resource allocation succeeds during failover.
Compute and database auto-scaling cannot exceed established regional GCP quota limits without prior approval.
3
Select optimal synthetic testing framework
Running synthetic workloads in a production-mirrored staging environment validates DNS switchover, routing, and replication lag metrics safely.
Synthetic traffic testing isolated from live users provides realistic failover measurements without incurring customer impact.

Anahtar Kavram

Disaster Recovery Validation & Quota/Capacity Management
Tahmini Süre:2m 0s
Soru 107Soru

A digital media organization is preparing to launch a globally televised live streaming event. The application architecture requires provisioning thousands of Compute Engine Virtual Machine instances across multiple target regions. To prevent infrastructure deployment failures and maintain strict governance over project resources, which TWO actions should the Cloud Architect perform prior to the event?

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

Cevabı ve açıklamayı göster

Cevap: Audit existing regional Compute Engine quotas across all target regions and submit proactive quota increase requests well in advance of the event.; Restrict quota management privileges by assigning the Quota Administrator role (roles/servicemanagement.quotaAdmin) only to authorized governance principals.

Cevap

The Cloud Architect should audit regional Compute Engine quotas and submit quota increase requests proactively prior to the event, and restrict quota management permissions by assigning the Quota Administrator role to authorized governance principals.
Proactively reviewing and requesting regional quota increases ensures capacity availability prior to high-demand events, preventing deployment failures caused by quota limits. Restricting quota administration using the fine-grained Quota Administrator role enforces least-privilege IAM governance.

Adım Adım Çözüm

1
Evaluate regional quota requirements against default limits.
Identify regions where planned VM instance counts exceed default regional quotas.
Quota limit breaches prevent VM instance creation during scale-out events.
2
Submit quota increase requests in advance.
Ensure Google Cloud support approves the required capacity before the live event.
Quota increases can require review time and cannot be guaranteed instantly during high-traffic events.
3
Apply fine-grained IAM governance for quota management.
Grant roles/servicemanagement.quotaAdmin to dedicated admin roles while avoiding primitive roles.
Enforces least privilege and prevents unauthorized quota changes.

Anahtar Kavram

Proactive Quota Management and IAM Governance
Soru 108Soru

A regulatory authority requires a financial institution to store highly sensitive customer audit logs in BigQuery. The institution's strict governance policy dictates that the cryptographic root of trust must reside exclusively within an on-premises Hardware Security Module (HSM) outside Google Cloud, ensuring Google never holds raw key material at rest. Which architectural configuration meets these regulatory compliance requirements while adhering to Google Cloud security best practices?

Cevabı ve açıklamayı göster

Cevap: Configure BigQuery table encryption using Customer-Managed Encryption Keys (CMEK) integrated with Cloud External Key Manager (Cloud EKM), and grant the BigQuery Service Agent the Cloud KMS CryptoKey Encrypter/Decrypter role.

Cevap

Configure BigQuery table encryption using Customer-Managed Encryption Keys (CMEK) integrated with Cloud External Key Manager (Cloud EKM), and grant the BigQuery Service Agent the Cloud KMS CryptoKey Encrypter/Decrypter role.
Cloud External Key Manager (Cloud EKM) allows Google Cloud services like BigQuery to encrypt data using keys stored in an external, on-premises Key Management Partner or HSM. By configuring CMEK pointed at a Cloud EKM key reference and granting the BigQuery service agent the minimal `roles/cloudkms.cryptoKeyEncrypterDecrypter` role, the organization maintains external key control while maintaining least-privilege security standards.

Adım Adım Çözüm

1
Identify the key management and external custody requirements.
The requirement mandates external key custody in an on-premises HSM, ensuring Google Cloud never holds raw key material at rest.
Cloud External Key Manager (Cloud EKM) is the GCP solution designed to integrate GCP services with external Key Management Partners / external HSMs.
2
Evaluate service compatibility and key configuration mode.
BigQuery supports CMEK backed by Cloud KMS keys that point to Cloud EKM.
Customer-Supplied Encryption Keys (CSEK) are unsupported for BigQuery and would involve sending raw keys into GCP RAM.
3
Determine necessary IAM permissions for the BigQuery service agent.
Grant `roles/cloudkms.cryptoKeyEncrypterDecrypter` on the Cloud KMS key reference to the BigQuery service account.
This grants minimum required operational access without granting primitive administrative permissions (`roles/owner`).

Anahtar Kavram

Cloud External Key Manager (Cloud EKM) and CMEK Integration
Soru 109Soru

A health-tech company hosts a data ingestion microservice on Google Cloud Compute Engine Managed Instance Groups (MIGs) in Project A. The microservice needs to access sensitive third-party API credentials stored in GCP Secret Manager located in a central security project (Project B). The security team mandates strict enforcement of least privilege, zero exposure of static service account key JSON files, and proper service account lifecycle controls. Which TWO actions should the Lead Cloud Architect recommend to establish a secure authentication and access pattern? (Select TWO)

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

Cevabı ve açıklamayı göster

Cevap: Attach a dedicated custom service account to the Compute Engine instances and grant it the Secret Manager Secret Accessor role (`roles/secretmanager.secretAccessor`) strictly on the target secret resource in Project B.; Configure cross-project service account impersonation by granting the caller service account in Project A the Service Account Token Creator role (`roles/iam.serviceAccountTokenCreator`) on the resource identity in Project B.

Cevap

The architect should attach a dedicated custom service account to the compute instances with the Secret Manager Secret Accessor role granted on the specific secret resource, and configure cross-project impersonation using the Service Account Token Creator role.
Securing Secret Manager access and service account lifecycles requires using dedicated custom service accounts with narrow IAM roles. Assigning the Secret Manager Secret Accessor role directly on the targeted secret resource enforces granular access control. For cross-project identity delegation without downloading keys, granting the Service Account Token Creator role enables short-lived impersonation while maintaining strict governance.

Adım Adım Çözüm

1
Identify compute identity requirements
Avoid using default service accounts and static service account JSON keys by creating a dedicated custom service account attached to Compute Engine VMs.
Default service accounts often carry broad permissions, and static key files create credential leakage risks.
2
Apply least-privilege secret access
Grant `roles/secretmanager.secretAccessor` at the secret resource level rather than the project level.
Restricting access to the specific secret prevents the service account from accessing other secrets or modifying secret metadata.
3
Configure cross-project identity delegation
Grant `roles/iam.serviceAccountTokenCreator` on the target service account to generate short-lived OAuth2/ID tokens.
Token creation allows keyless impersonation across GCP projects without assigning excessive administrative privileges.

Anahtar Kavram

Service Account Lifecycle & Least-Privilege Secret Access
Soru 110Soru

An enterprise financial institution is modernizing its Google Cloud architecture to satisfy strict regulatory compliance and perimeter security mandates. The architecture team must evaluate and assign the appropriate network security control mechanism to meet four distinct security requirements across their multi-project environment.

Match each architectural security requirement with the corresponding Google Cloud network security mechanism that best satisfies it.

Soldaki öğeye tıklayın, sonra eşleşen sağdaki öğeye tıklayın

Öğeler

Mitigate Layer 7 web application attacks such as SQL injection and enforce IP-based rate limiting at the Google Cloud network edge.
Prevent authorized IAM users in a sensitive analytics project from copying BigQuery datasets to unauthorized external cloud resources.
Enforce mandatory, non-overridable organization-wide ingress firewall deny rules across all current and future VPC networks.
Provide private, isolated access to a third-party managed SaaS application residing in an external GCP organization without using transitive VPC peering.

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

Layer 7 inspection and edge rate limiting map to Cloud Armor Security Policies. BigQuery exfiltration prevention maps to VPC Service Controls Service Perimeter. Organization-wide non-overridable firewall rules map to Hierarchical Firewall Policies. Private third-party SaaS connectivity without VPC peering maps to Private Service Connect (PSC) Endpoints.
Each requirement aligns directly with a distinct layer of Google Cloud's defense-in-depth architecture. Cloud Armor provides edge WAF and DDoS protection for web workloads. VPC Service Controls form logical security perimeters around GCP APIs to block data exfiltration. Hierarchical Firewall Policies enforce top-down network security rules that project owners cannot modify. Private Service Connect delivers private, consumer-endpoint access to SaaS or producer services across project boundaries.

Adım Adım Çözüm

1
Analyze the Layer 7 web threat mitigation requirement.
Identified Cloud Armor Security Policies as the edge defense attached to HTTP(S) Load Balancers.
Cloud Armor operates at the network edge to filter web traffic against OWASP Top 10 risks and apply rate-limiting rules.
2
Analyze the data exfiltration prevention requirement for managed GCP services.
Identified VPC Service Controls as the perimeter boundary mechanism.
IAM controls who can access resources, but VPC Service Controls restrict from where and to where API requests can move data, effectively preventing exfiltration.
3
Analyze the centralized governance firewall requirement.
Identified Hierarchical Firewall Policies attached at Folder or Organization nodes.
Hierarchical firewall rules inherit down the resource hierarchy and take precedence over local VPC firewall rules, preventing local project admin overrides.
4
Analyze the cross-tenant private service connectivity requirement.
Identified Private Service Connect (PSC) Endpoints.
PSC allows unidirectional, private IP connectivity between independent GCP project/organization VPCs without requiring full network peering topology.

Anahtar Kavram

Google Cloud Perimeter Security and Network Controls
Soru 111Soru

A global enterprise is establishing an automated Infrastructure as Code (IaC) pipeline to provision Cloud Spanner databases and Cloud Storage buckets across multiple operational regions. During automated CI/CD runs, concurrent pipeline executions occasionally attempt to modify the same environment simultaneously. The lead architect must ensure that remote Terraform state operations prevent race conditions and allow state recovery if accidental deletion occurs. Which provisioning approach best satisfies these requirements?

Cevabı ve açıklamayı göster

Cevap: Configure the Terraform backend to store the state file in a Google Cloud Storage bucket with Object Versioning enabled, allowing native object locking to manage concurrency.

Cevap

The team should store the Terraform state in a Google Cloud Storage backend with Object Versioning enabled to leverage native state locking and preserve state history.
The correct strategy uses Google Cloud Storage as a remote Terraform backend with Object Versioning enabled. The GCS backend natively supports state locking using Google Cloud Storage object locking capabilities, ensuring that concurrent pipeline runs cannot mutate the state simultaneously while providing history recovery.

Adım Adım Çözüm

1
Identify the concurrency and recovery requirements for IaC database and storage provisioning.
The solution requires centralized state storage, concurrent execution protection, and state restoration capabilities.
Simultaneous pipeline executions can corrupt un-locked Terraform state files.
2
Evaluate Google Cloud Storage features for Terraform backend integration.
GCS provides native object locking support for Terraform state files and supports Object Versioning for point-in-time state recovery.
Native locking guarantees single-writer access during `terraform apply` operations without external lock tables.

Anahtar Kavram

Terraform State Management and Storage Backend Provisioning
Tahmini Süre:1m 30s
Soru 112Soru

A Nordic shipping and maritime logistics company is migrating its container tracking system and customer data to Google Cloud. Regional regulations dictate that all stored data must physically reside within European Union boundaries, cloud service provider personnel access must require explicit administrative approval, and data exfiltration across network perimeters to external buckets must be blocked. Which TWO architectural actions should you implement to meet these governance and data sovereignty mandates? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Set an Organization Policy using the resource locations constraint restricted to European Union regions, and enable Access Approval to require explicit administrator authorization before Google support can access data.; Configure Customer-Managed Encryption Keys (CMEK) using Cloud KMS key rings deployed in EU regions, and establish a VPC Service Controls perimeter around Cloud Storage and BigQuery resources.

Cevap

The correct architectural steps are to enforce an Organization Policy for resource locations along with Access Approval, and to deploy Customer-Managed Encryption Keys (CMEK) in EU regions protected by a VPC Service Controls security perimeter.
Enforcing the `constraints/gcp.resourceLocations` Organization Policy restricted to EU locations guarantees data residency, while Access Approval prevents unauthorized Google operator access. Pairing CMEK stored in EU Cloud KMS key rings with VPC Service Controls ensures regional key control and prevents data exfiltration.

Adım Adım Çözüm

1
Enforce strict data residency and access transparency controls.
Applying the `constraints/gcp.resourceLocations` Organization Policy restricts resource creation strictly to specified EU regions. Enabling Access Approval mandates explicit customer consent before Google personnel can access data.
Regulatory compliance mandates physical data localization within the EU and strict cloud provider access governance.
2
Configure CMEK and establish network perimeter boundaries.
Using Cloud KMS key rings located in EU regions for CMEK guarantees cryptographic data protection within the sovereignty boundary, while VPC Service Controls isolate services to prevent data exfiltration.
CMEK ensures regional key governance, and VPC Service Controls protect against data exfiltration across security perimeters.

Anahtar Kavram

Data Sovereignty, Access Approval, and Exfiltration Guardrails in GCP
Soru 113Soru

An automotive IoT company structures its Google Cloud resource hierarchy with an Organization node containing an Autonomous Vehicles folder. Within this folder are two projects: telemetry-ingest, which hosts automated telemetry processing microservices on Compute Engine, and telemetry-storage, which contains a centralized Cloud Storage bucket for long-term diagnostic logs. The ingestion microservice requires read-only access to objects in the centralized bucket. Additionally, developer identity group members need to launch compute instances that execute as the ingestion service account without gaining administrative control over service accounts. Following Google-recommended security practices of least privilege and resource hierarchy management, which set of role assignments should you configure?

Cevabı ve açıklamayı göster

Cevap: Grant Storage Object Viewer (roles/storage.objectViewer) on the centralized bucket to the ingestion service account, and grant Service Account User (roles/iam.serviceAccountUser) on the ingestion service account to the developer identity group.

Cevap

Grant Storage Object Viewer (roles/storage.objectViewer) on the centralized bucket to the ingestion service account, and grant Service Account User (roles/iam.serviceAccountUser) on the ingestion service account to the developer identity group.
The correct solution follows the principle of least privilege by binding the fine-grained predefined role 'Storage Object Viewer' directly to the destination Cloud Storage bucket rather than inheriting broad permissions from a project or folder level. Furthermore, granting 'Service Account User' specifically on the service account resource permits developers to bind the identity to instances without granting administrative privileges over service account management.

Adım Adım Çözüm

1
Determine the minimal required role for reading Cloud Storage objects.
Identify roles/storage.objectViewer as the predefined role granting read access to bucket objects without administrative privileges.
Principle of least privilege requires avoiding broad primitive roles (Editor/Owner) or administrative roles (Storage Admin).
2
Determine the resource hierarchy scope for the bucket access.
Apply the IAM binding directly on the centralized Cloud Storage bucket rather than at the project or folder level.
Inheritance down the resource hierarchy means folder- or project-level roles apply to all storage resources within those containers.
3
Identify the required IAM role for attaching a service account to Compute Engine instances.
Select roles/iam.serviceAccountUser bound directly to the target service account resource.
Developers require the ability to run instances as the service account without needing administrative control (roles/iam.serviceAccountAdmin) over service account lifecycles.

Anahtar Kavram

Fine-Grained IAM Scoping and Service Account Impersonation via Resource Hierarchy
Soru 114Soru

An organization is analyzing its automated software release process for a hybrid microservices platform deployed on Compute Engine Managed Instance Groups (MIGs). The CI/CD pipeline utilizes Cloud Build to build custom Golden Images using Packer and execute Terraform scripts to update instance templates. An SDLC architecture review identified two critical issues: the Cloud Build default service account uses the primitive Editor role across the project, and Terraform state files generated during execution are stored on local runner storage without locks, causing concurrency errors during parallel pipeline runs. Which TWO actions should the architecture team recommend to resolve these issues while following Google Cloud best practices? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Configure a dedicated user-managed service account for Cloud Build with granular roles for compute resource management and grant it the Service Account User role on the workload runtime service account.; Configure a central Google Cloud Storage bucket backend with Object Versioning enabled for Terraform state management.

Cevap

To establish a secure and reliable CI/CD pipeline, the organization must create a dedicated user-managed service account for Cloud Build with least-privilege predefined roles (including Service Account User for compute workload attachment) and store Terraform state remotely in a Google Cloud Storage bucket with Object Versioning enabled.
The solution requires hardening the CI/CD pipeline identity and securing IaC state management. Configuring a dedicated user-managed service account with fine-grained permissions and the Service Account User role enforces least privilege. Storing Terraform state in a centralized Google Cloud Storage bucket with versioning prevents state corruption, lock contention, and drift during automated pipeline runs.

Adım Adım Çözüm

1
Analyze pipeline security and identify IAM role anti-patterns.
Identified that primitive Editor/Owner roles grant broad unnecessary access across GCP services.
Least privilege requires replacing primitive roles with fine-grained custom or predefined roles and using roles/iam.serviceAccountUser to attach identities to compute resources.
2
Evaluate Infrastructure as Code (IaC) state management requirements.
Identified that local state files on ephemeral runner storage cause race conditions and state loss.
Google Cloud Storage provides central state locking and versioning for multi-execution Terraform pipelines.

Anahtar Kavram

CI/CD Pipeline Security and IaC Remote State Management
Soru 115Soru

An enterprise organization is restructuring its software delivery lifecycle to establish an end-to-end secure, automated CI/CD pipeline for deploying a critical microservice to Google Kubernetes Engine (GKE). The security policy mandates least-privilege access, container vulnerability scanning, cryptographic image attestation using Binary Authorization, Terraform state validation, and controlled canary traffic routing. Place the operational stages of this deployment pipeline in the correct chronological order from initial source submission to full production release.

Öğeleri doğru sıraya koymak için sürükleyin

Cevabı ve açıklamayı göster

Cevap

The correct operational sequence begins with Cloud Build compiling the container image and performing static security and vulnerability analysis via Artifact Analysis. Once validated, Cloud Build uses Cloud KMS to generate a cryptographic Binary Authorization attestation and pushes the image and signature to Artifact Registry. Next, Cloud Build uses Workload Identity Federation with a dedicated user-managed service account to validate infrastructure state via `terraform plan`. Cloud Deploy then initiates deployment to GKE, where Binary Authorization verifies the KMS signature before establishing a 10% canary traffic allocation. Finally, Cloud Monitoring evaluates canary stability metrics against defined Service Level Indicators (SLIs) before Cloud Deploy automatically promotes the release to 100% production traffic.
The sequence follows Google Cloud best practices for secure SDLC and progressive delivery. Artifact vulnerability scanning must precede attestation signing so that only clean images receive KMS signatures. Infrastructure state validation via Terraform and Workload Identity Federation ensures environment readiness. GKE Binary Authorization enforces the signature requirement at cluster admission during Cloud Deploy canary launch. Finally, canary health observation against Cloud Monitoring SLIs ensures automated, risk-managed full promotion.

Adım Adım Çözüm

1
Perform initial artifact construction and security scanning.
Container image built and checked for vulnerabilities via Container Analysis prior to artifact signing.
Security checks must run immediately at artifact creation to prevent compromised code from proceeding further into the pipeline.
2
Sign the validated container image and push to Artifact Registry.
A cryptographic attestation linked to Cloud KMS is produced and stored along with the container image.
Binary Authorization policies require a verified attestation signature tied to a compliant image digest before cluster admission.
3
Validate infrastructure state changes.
Terraform plans are generated against remote GCS backends using short-lived credentials via Workload Identity Federation.
Least-privilege service account authentication ensures infrastructure drift and state lock checks complete securely before deployment.
4
Trigger canary deployment under admission policy control.
GKE Binary Authorization validates the KMS signature and Cloud Deploy routes 10% of live traffic to the canary workloads.
Admission control prevents unauthorized container execution while canary deployment minimizes blast radius for new code.
5
Evaluate canary health metrics and complete production promotion.
Cloud Monitoring confirms error budget integrity and SLI health, triggering 100% traffic rollout.
Automated metrics verification ensures production stability before full rollout.

Anahtar Kavram

Continuous Integration and Continuous Delivery (CI/CD) Pipeline Analysis
Soru 116Soru

A logistics organization is building an automated continuous deployment pipeline to manage multi-environment releases of a microservice application across Google Kubernetes Engine (GKE) clusters using Cloud Build and Cloud Deploy. The security and operations teams require that all Infrastructure as Code (IaC) updates executed during the release process maintain state integrity and concurrency locking, and that the execution service account follows the principle of least privilege when delegating compute workloads. Which deployment pipeline configuration fulfills these architectural requirements?

Cevabı ve açıklamayı göster

Cevap: Configure Cloud Build to execute Terraform using a Cloud Storage remote backend with versioning and object locking, assign the Service Account User role (roles/iam.serviceAccountUser) to the build execution service account for compute resource delegation, and use Cloud Deploy to automate progressive release rollouts.

Cevap

Configure Cloud Build to use a Cloud Storage backend with object locking and versioning for Terraform state management, grant roles/iam.serviceAccountUser to the execution service account for least privilege workload delegation, and use Cloud Deploy for automated releases.
The solution using Cloud Build with Cloud Storage remote state storage (featuring object versioning and state locking) ensures state file persistence and prevents concurrent modification errors. Granting the Service Account User role satisfies least-privilege security requirements for attaching service accounts to compute resources without exposing administrative management controls.

Adım Adım Çözüm

1
Analyze state management requirements for automated IaC pipelines
Identified the need for a remote backend using Cloud Storage with state locking to prevent state file corruption and concurrency conflicts during automated pipeline executions.
Local state files on ephemeral build runner instances are discarded after run completion, leading to configuration drift and state loss.
2
Determine least privilege IAM requirements for service account usage
Selected Service Account User role (roles/iam.serviceAccountUser) to allow resources to run under a target service account.
Granting administrative roles like Service Account Admin or primitive Owner roles violates IAM security governance.
3
Integrate Cloud Deploy for automated release pipelines
Configured Cloud Deploy to handle automated and progressive application delivery to GKE clusters.
Cloud Deploy provides managed continuous delivery with built-in release promotion and rollback capabilities.

Anahtar Kavram

Automated Continuous Deployment Pipelines with IaC State Locking and Least-Privilege IAM
Tahmini Süre:2m 0s
Soru 117Soru

An Australian telecommunications enterprise is migrating its customer analytics platform to Google Cloud. To comply with national data sovereignty regulations and strict audit requirements, the architecture must ensure that customer personally identifiable information (PII) is stored and processed exclusively within Australian geographic boundaries, Google support engineers cannot access customer data without explicit loggable authorization, and authorized internal users are prevented from exfiltrating data to external resources outside the organization. Which TWO architectural controls should the Cloud Architect implement to meet these requirements?

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

Cevabı ve açıklamayı göster

Cevap: Enforce an Organization Policy using the Resource Locations constraint (constraints/gcp.resourceLocations) restricted to Australian regions to block resource creation outside allowed geographic boundaries.; Configure a VPC Service Controls perimeter around projects containing PII to prevent data exfiltration, and enable Access Approval to mandate explicit customer authorization prior to Google support access.

Cevap

The Cloud Architect must enforce an Organization Policy with the Resource Locations constraint restricted to Australian regions and deploy a VPC Service Controls security perimeter combined with Access Approval.
To fulfill strict data sovereignty mandates, enforcing an Organization Policy with `constraints/gcp.resourceLocations` prevents resources from being provisioned outside specified regions. Combining VPC Service Controls with Access Approval provides robust governance by blocking unauthorized data exfiltration across project boundaries and requiring explicit customer consent before Google support engineers can access underlying data.

Adım Adım Çözüm

1
Address data sovereignty and geographic location restrictions.
Apply the Organization Policy constraint `constraints/gcp.resourceLocations` limited strictly to `in:australia-southeast1-locations` and `in:australia-southeast2-locations`.
This policy guarantees that compute, storage, and managed data services cannot be provisioned outside Australian borders.
2
Address data exfiltration protection and Google administrative access controls.
Define VPC Service Controls perimeters around PII storage and processing projects, and activate Access Approval across the resource hierarchy.
VPC Service Controls create a cryptographic and network boundary preventing network egress to unauthorized external GCP projects, while Access Approval requires customer confirmation before Google staff access data for support requests.

Anahtar Kavram

Enforcing data sovereignty and data governance using Resource Locations Organization Policies, VPC Service Controls, and Access Approval
Soru 118Soru

An enterprise architecture team is designing an automated secret rotation pipeline in Google Cloud for database credentials stored in Secret Manager. The secret payload is encrypted using a Customer-Managed Encryption Key (CMEK) hosted in Cloud KMS. Rotation must occur automatically every 30 days via a Cloud Run microservice triggered by Secret Manager rotation notifications sent to Cloud Pub/Sub. Enterprise compliance policy strictly forbids long-lived service account JSON keys and mandates least-privilege access controls across all services. Which architectural configuration correctly satisfies these operational and security requirements?

Cevabı ve açıklamayı göster

Cevap: Grant the Cloud Run service account the Secret Manager Secret Accessor and Secret Manager Version Manager roles on the target secret, grant the Cloud SQL Client role on the database instance, and grant the Cloud KMS CryptoKey Decrypter role to the Secret Manager Service Agent. Configure Pub/Sub to trigger Cloud Run using OIDC authentication tied to a dedicated Pub/Sub service account.

Cevap

The optimal configuration grants fine-grained predefined roles (Secret Accessor, Version Manager, Cloud SQL Client) to the Cloud Run service account, delegates CMEK decryption permissions to the Secret Manager Service Agent, and uses Pub/Sub push authentication with OIDC tokens.
The solution implementing fine-grained predefined roles (Secret Manager Secret Accessor, Secret Manager Version Manager, and Cloud SQL Client) directly on the Cloud Run service account enforces strict least privilege. Granting Cloud KMS Decrypter rights to the Secret Manager Service Agent enables native CMEK support for secret versions. Utilizing Pub/Sub push subscriptions with OIDC token service account authentication enables secure, passwordless execution without generating service account JSON keys.

Adım Adım Çözüm

1
Analyze Service Account Identity & Least Privilege
Cloud Run requires fine-grained roles (Secret Accessor, Version Manager, Cloud SQL Client) bound directly to the resource level, avoiding project-wide primitive roles or key generation.
Adheres to security governance requiring minimal access boundaries without service account key creation.
2
Configure CMEK Encryption Key Access
Grant `roles/cloudkms.cryptoKeyDecrypter` on the Cloud KMS key to the automated Secret Manager Service Agent (`service-PROJECT_NUMBER@gcp-sa-secretmanager.iam.gserviceaccount.com`).
Secret Manager manages CMEK envelope encryption operations asynchronously through its dedicated service agent.
3
Configure Secure Trigger Authentication
Set up Secret Manager rotation to publish events to Pub/Sub, and configure a Pub/Sub push subscription with an OIDC token specifying the target Cloud Run service account.
Ensures authenticated microservice invocations over HTTPS without embedding static credentials.

Anahtar Kavram

Secret Manager CMEK Integration and Service Account Lifecycle Security
Soru 119Soru

A financial analytics company manages its cloud resources using Google Cloud folders to isolate production workloads. The security team mandates that no virtual machine (VM) instances created inside any project under the 'Analytics-Production' folder may be assigned public IP addresses. This security constraint must apply automatically to all existing and future projects created within this folder. Which approach should the Cloud Architect take to enforce this constraint centrally with minimal operational overhead?

Cevabı ve açıklamayı göster

Cevap: Apply an Organization Policy at the 'Analytics-Production' folder level enforcing the `constraints/compute.vmExternalIpAccess` boolean constraint as Deny.

Cevap

Apply an Organization Policy at the 'Analytics-Production' folder level enforcing the `constraints/compute.vmExternalIpAccess` constraint.
Applying an Organization Policy with the constraint `constraints/compute.vmExternalIpAccess` enforced as Deny at the parent folder level enforces programmatic guardrails across all contained projects. Any attempt to attach a public IP to a VM instance within this folder will be rejected automatically.

Adım Adım Çözüm

1
Identify the target resource hierarchy node
The requirement specifies enforcing the rule across all current and future projects under the 'Analytics-Production' folder.
Applying guardrails at the parent folder ensures inherited enforcement without needing per-project manual configuration.
2
Select the appropriate Google Cloud governance feature for resource constraints
Organization Policy constraints regulate configuration properties (such as external IPs on VMs).
Organization Policies define strict guardrails on resources regardless of IAM permissions.
3
Apply the boolean constraint `constraints/compute.vmExternalIpAccess`
External IP address allocation on VM instances within the folder hierarchy is denied.
This specific constraint directly controls whether Compute Engine instances can have external IP interfaces.

Anahtar Kavram

Organization Policies and Constraints
Soru 120Soru

A government-owned energy enterprise based in Denmark is migrating its critical smart-grid telemetry and customer billing datasets to Google Cloud. To comply with national data sovereignty regulations and European data protection mandates, the lead cloud architect must satisfy two primary compliance requirements: ensure that all newly provisioned data storage resources remain strictly within the Denmark/Nordic region, and prevent authorized project identity credentials from exfiltrating sensitive data to external Google Cloud resources outside the organization's control. Which TWO architectural controls should the architect implement to satisfy these requirements?

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

Cevabı ve açıklamayı göster

Cevap: Enforce an Organization Policy with the Resource Locations constraint (constraints/gcp.resourceLocations) restricted to the europe-north1 region across the resource hierarchy.; Configure a VPC Service Controls perimeter around the project enclosing BigQuery and Cloud Storage to restrict data movement across the perimeter boundary.

Cevap

The architect must enforce an Organization Policy using the Resource Locations constraint restricted to europe-north1, and configure a VPC Service Controls perimeter around BigQuery and Cloud Storage.
Data sovereignty and data governance require complementary controls at both the resource provisioning layer and the network perimeter layer. Restricting deployment locations via the Resource Locations organization policy ensures that resources are created exclusively within the approved geographic zone (europe-north1). Simultaneously, wrapping sensitive services within a VPC Service Controls perimeter ensures that even fully authenticated IAM principals cannot extract data to external buckets or datasets outside the organization.

Adım Adım Çözüm

1
Address data residency constraints at the resource deployment boundary.
Applying the constraints/gcp.resourceLocations organization policy prevents project administrators from creating storage resources outside the allowed region (europe-north1).
Organization policies provide declarative governance controls that restrict physical deployment regions.
2
Mitigate data exfiltration risks from compromised or authorized identities.
Defining a VPC Service Controls security perimeter around Cloud Storage and BigQuery isolates the data services from unauthorized external projects and internet endpoints.
IAM permissions authorize WHO can access data, whereas VPC Service Controls restrict WHERE data can be moved, blocking exfiltration to external resources.

Anahtar Kavram

Data Sovereignty and Perimeter Security Controls
ÖncekiSayfa 6 / 80Sonraki
Tüm alıştırma soruları — Google Cloud Professional Cloud Architect | Examkin