Tüm alıştırma soruları

1598 soru

Soru 181Soru

A fintech company is establishing a procedure to test and validate a new microservices-based transaction processing solution on Google Cloud before moving it to production. The architecture uses Terraform for Infrastructure as Code (IaC) and Google Kubernetes Engine (GKE) for compute. The validation procedure must ensure infrastructure readiness, deployment safety, and pre-flight operational checks without risking configuration drift or quota failures. Which TWO steps should be included in this solution validation procedure? (Select TWO)

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

Cevabı ve açıklamayı göster

Cevap: Perform automated dry-run plan validations (`terraform plan`) using a versioned Cloud Storage remote backend with state locking in the CI/CD pipeline.; Verify regional resource quota limits in Cloud Quotas and execute load tests in a dedicated staging environment prior to initiating production deployment.

Cevap

The validation procedure should include performing automated dry-run plan validations using a versioned Cloud Storage remote backend with state locking, and verifying regional resource quota limits while executing load tests in a dedicated staging environment.
Validating technical solutions on Google Cloud requires a comprehensive approach covering both Infrastructure as Code (IaC) deployment safety and infrastructure capacity readiness. Using a versioned Cloud Storage backend with state locking during automated `terraform plan` executions ensures that proposed infrastructure changes are validated safely without risking state corruption. Additionally, proactively verifying regional quota availability and conducting load tests in an isolated staging environment ensures the environment is prepared for operational traffic without hitting resource limits.

Adım Adım Çözüm

1
Analyze the technical validation requirements for Infrastructure as Code and cloud environment readiness.
Identified the need for secure state management, pre-deployment dry runs, and proactive quota verification.
Technical solution validation requires verifying that infrastructure definitions are deterministic and environment quotas can support workload demands.
2
Evaluate IaC state management and testing practices.
Selected automated `terraform plan` execution backed by versioned Cloud Storage with locking, while rejecting unversioned local state storage.
Remote state backends with locking prevent state corruption and race conditions during automated pipeline validation.
3
Evaluate capacity and quota validation strategies.
Selected proactive quota checking in Cloud Quotas and staging load testing, while rejecting delayed quota requests.
Quota increases require lead time; requesting them after experiencing production failures causes deployment blockages.

Anahtar Kavram

Technical solution validation procedures for cloud infrastructure and IaC readiness
Soru 182Soru

An enterprise biotechnology organization is designing an automated continuous delivery pipeline to manage infrastructure across multiple Google Cloud projects using Terraform. The pipeline must guarantee secure remote state persistence, prevent state file corruption during concurrent deployment execution, eliminate long-lived service account authentication keys, and maintain strict identity least privilege. Which TWO actions should the cloud architecture team implement to satisfy these requirements? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Configure a Google Cloud Storage backend with Object Versioning enabled for remote Terraform state storage and state locking.; Authenticate the external deployment runner using Workload Identity Federation to impersonate a dedicated service account with fine-grained IAM roles.

Cevap

The architecture team should store remote Terraform state in a Google Cloud Storage bucket with Object Versioning enabled to ensure state resilience and concurrency control, and authenticate external deployment pipelines using Workload Identity Federation to eliminate long-lived service account keys while enforcing least privilege through fine-grained IAM roles.
Configuring Cloud Storage with Object Versioning provides secure, centralized, and version-controlled remote state persistence that automatically handles locking to prevent concurrent state modifications. Pairing this backend with Workload Identity Federation allows external CI/CD systems to securely assume dedicated GCP service account identities using short-lived tokens, adhering strictly to least-privilege access without exporting static credential files.

Adım Adım Çözüm

1
Evaluate remote backend state lock and durability requirements
Selected Cloud Storage with Object Versioning to store Terraform state securely with locking and version history.
Google Cloud Storage backends provide native file locking mechanisms to prevent concurrent state access and maintain version history against corruption.
2
Assess pipeline authentication security and key management constraints
Selected Workload Identity Federation for external CI/CD pipeline access.
Workload Identity Federation enables short-lived identity exchange for service account impersonation without creating long-lived exported JSON keys.
3
Verify adherence to least privilege security rules
Scoped service account access to predefined granular roles rather than broad primitive roles.
Primitive roles like Owner grant excessive broad permissions and break enterprise GCP compliance standards.

Anahtar Kavram

Infrastructure as Code Governance, State Backend Lock Security, and Pipeline Identity Scoping
Soru 183Soru

A healthcare provider is configuring a pre-flight staging test strategy to validate a telemetry processing solution on Google Cloud prior to releasing it into production. The application requires automated deployment of private Google Kubernetes Engine (GKE) clusters via Terraform, strict compliance controls against unauthorized data transfers, and seamless capacity scaling. Which validation procedure should the cloud architect implement to verify technical infrastructure readiness while preventing deployment risks?

Cevabı ve açıklamayı göster

Cevap: Execute infrastructure dry-runs using a centralized Google Cloud Storage state backend with locking, pre-evaluate regional compute quota availability via API checks, enforce authorized network boundaries for GKE control plane endpoints, and run VPC Service Controls in dry-run mode to audit exfiltration rules.

Cevap

The correct validation strategy involves running infrastructure planning steps with remote state locking, checking regional quotas before resource creation, maintaining control plane endpoint restrictions, and testing security perimeters in dry-run mode.
The solution that combines remote state management with locking, pre-flight API quota verification, strict control plane access control, and dry-run security perimeter auditing represents GCP best practice for solution validation. This approach confirms operational, capacity, and security readiness prior to production promotion.

Adım Adım Çözüm

1
Assess Infrastructure as Code state safety and concurrency
Ensure Terraform uses a Google Cloud Storage backend with state locking enabled so concurrent validation pipelines do not corrupt environment state.
Prevents race conditions and state file corruption during automated validation phases.
2
Verify resource quotas prior to cluster expansion
Query GCP quota APIs programmatically to ensure regional CPU, memory, and IP allocation limits accommodate planned scale.
Prevents abrupt deployment halts caused by unfulfilled compute or network resource limits.
3
Validate security perimeters without service disruption
Use GKE Master Authorized Networks for control plane isolation and evaluate VPC Service Controls policies using dry-run mode.
Verifies network security and exfiltration protection without blocking legitimate test traffic.

Anahtar Kavram

Developing Procedures to Test and Validate Technical Solutions
Tahmini Süre:1m 30s
Soru 184Soru

A healthcare technology enterprise operates a multi-project Google Cloud environment with steady-state core web services alongside bursty, fault-tolerant batch analytics workloads. The organization needs to establish FinOps governance to improve cost transparency across business units and optimize compute spend without impeding development velocity. Which TWO architectural and governance strategies should the Cloud Architect recommend?

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

Cevabı ve açıklamayı göster

Cevap: Configure detailed Cloud Billing export to BigQuery and implement custom dashboards to enable chargeback and showback reporting using standardized resource labels.; Purchase Committed Use Discounts (CUDs) for predictable steady-state core workloads while utilizing Spot VMs for bursty, fault-tolerant batch processing.

Cevap

The architect should recommend exporting detailed Cloud Billing data to BigQuery for label-based showback/chargeback governance, and combining Committed Use Discounts (CUDs) for steady-state baselines with Spot VMs for variable, fault-tolerant workloads.
Combining BigQuery billing exports with standardized labels provides complete financial visibility and enables precise chargeback capabilities across organizational boundaries. Additionally, pairing Committed Use Discounts for predictable baseline services with Spot VMs for fault-tolerant batch workloads achieves optimal financial efficiency across different usage profiles.

Adım Adım Çözüm

1
Analyze workload resource consumption patterns.
Identified two distinct operational patterns: predictable 24/7 steady-state backends and intermittent, fault-tolerant batch workloads.
Cost optimization strategies depend heavily on matching purchasing models (CUDs vs. Spot VMs) to workload predictability and fault tolerance.
2
Select financial management and cost allocation mechanisms.
Exporting billing records to BigQuery and enforcing mandatory resource labeling enables granular cost attribution across business units.
FinOps governance requires automated, queryable billing datasets to establish showback/chargeback models and drive organizational accountability.
3
Apply optimal compute pricing constructs.
Standard CUDs cover baseline compute for maximum discount, while Spot VMs handle bursty processing at heavily discounted rates.
Avoids over-committing to long-term CUDs for variable spikes while maintaining low cost per unit for batch jobs.

Anahtar Kavram

FinOps Cost Governance and Compute Cost Optimization
Soru 185Soru

An enterprise IoT telemetry platform processes high-throughput fleet analytics across Google Cloud. The primary workload runs in `us-central1`, while a secondary disaster recovery environment is staged in `us-east4`. The application tier uses Compute Engine Managed Instance Groups (MIGs) served by a Global External Application Load Balancer, and backend services rely on private inter-VPC communication and dedicated hybrid links to on-premises datacenters. During a complete outage in `us-central1`, the incident response team must execute the disaster recovery failover runbook to restore full operational capacity in `us-east4` within a strict RTO. Which of the following execution steps must the operations team perform to successfully execute this regional failover? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Verify regional compute resource quotas in `us-east4` and request quota increases in advance if required capacity exceeds current limits prior to scaling up target Managed Instance Groups.; Update Cloud DNS routing policies or Load Balancer backend service configurations to direct incoming application traffic exclusively to the healthy MIG backends in `us-east4`.

Cevap

The correct execution steps are verifying and securing necessary regional vCPU and resource quotas in the failover region (`us-east4`) prior to scaling up backend workloads, and updating ingress traffic routing (via Cloud DNS policies or Load Balancer backend configurations) to direct application traffic to the active failover infrastructure.
Executing a successful regional disaster recovery failover requires both infrastructure readiness and traffic redirection. First, regional compute resource quotas in the failover region must be verified and expanded in advance so that scaling up Managed Instance Groups does not fail due to API quota limits. Second, once failover instances are active, ingress routing mechanisms such as Global Load Balancer backend service definitions or Cloud DNS failover routing policies must be updated to route live application traffic to the failover region.

Adım Adım Çözüm

1
Evaluate Regional Resource Quotas
Ensure target compute capacity in `us-east4` can expand to support full operational load without encountering `QUOTA_EXCEEDED` API errors during MIG scale-up.
Google Cloud quotas are enforced regionally. Attempting a rapid failover scale-up without sufficient quota reserved or pre-approved will cause instance creation failures.
2
Perform Ingress Traffic Cutover
Update Load Balancer backend instance groups or Cloud DNS failover routing records to direct all user requests to the operational MIGs in `us-east4`.
Traffic must be explicitly redirected away from the impacted primary region (`us-central1`) to complete operational recovery.

Anahtar Kavram

Disaster Recovery Execution and Regional Failover Validation
Soru 186Soru

A financial media company operates a real-time news analytics system hosted in Google Cloud's us-central1 region. The platform processes high-throughput data streams using Compute Engine Managed Instance Groups (MIGs) and stores user subscription profiles in Cloud SQL for PostgreSQL. The company requires a disaster recovery (DR) strategy for an unrecoverable outage in us-central1. The business mandates a Recovery Point Objective (RPO) of near zero (< 1 minute) and a Recovery Time Objective (RTO) under 15 minutes. To minimize idle infrastructure costs, compute resources in the secondary region (us-east4) should only be scaled up during an actual failover execution. Which disaster recovery execution strategy satisfies these requirements?

Cevabı ve açıklamayı göster

Cevap: Deploy a Pilot Light strategy: maintain cross-region read replicas for Cloud SQL in us-east4, and keep a minimal scaled-down MIG in us-east4; during failover, promote the Cloud SQL replica to primary and autoscaling expands the MIG.

Cevap

Deploying a Pilot Light DR pattern with cross-region Cloud SQL read replicas and a minimal scaled-down Compute Engine MIG in the secondary region meets the near-zero RPO and 15-minute RTO requirements while optimizing cost.
The correct strategy combines continuous cross-region database replication (Cloud SQL read replica in us-east4) with a minimal compute footprint (scaled-down MIG). When a failure occurs in the primary region, promoting the database replica and scaling out the MIG fulfills the near-zero RPO and sub-15 minute RTO requirements without paying for full idle compute capacity.

Adım Adım Çözüm

1
Evaluate RPO requirements against data replication patterns.
Near-zero RPO (< 1 min) requires continuous data replication. Cloud SQL cross-region read replicas provide continuous asynchronous replication to us-east4.
Backup-and-restore or periodic export dump strategies introduce data loss equal to the backup interval.
2
Evaluate RTO and cost requirements against compute failure strategy.
Keeping a minimal MIG footprint in us-east4 (Pilot Light) ensures rapid capacity expansion within minutes while keeping idle compute cost low.
Provisioning full duplicate infrastructure (Hot Standby) would incur unnecessary idle compute cost, while spinning up from scratch (Cold Standby) risks missing the 15-minute RTO.

Anahtar Kavram

Disaster Recovery Patterns (Pilot Light vs Warm/Cold Standby) and RPO/RTO Alignment in GCP
Soru 187Soru

A financial services organization operates a daily batch processing pipeline on a Compute Engine Managed Instance Group (MIG) consuming messages from Cloud Pub/Sub. Every morning at market open, incoming message rates surge by 10×10\times within 30 seconds. Because instance initialization and software warmup take approximately 4 minutes, dynamic auto-scaling policies based on Pub/Sub queue depth or CPU load experience severe queue backlogs and SLA violations during the first 10 minutes of the spike. Which architecture strategy should a Cloud Architect recommend to eliminate initial latency spikes while maintaining cost efficiency during off-peak hours?

Cevabı ve açıklamayı göster

Cevap: Implement scheduled auto-scaling rules on the Managed Instance Group to scale out baseline capacity prior to market open, combined with dynamic target tracking scaling based on Cloud Pub/Sub unacknowledged message depth.

Cevap

Implement scheduled auto-scaling rules on the Managed Instance Group to scale out baseline capacity prior to market open, combined with dynamic target tracking scaling based on Cloud Pub/Sub unacknowledged message depth.
Combining scheduled auto-scaling with queue-based dynamic auto-scaling solves both the predictable instant spike and off-peak elasticity needs. Scheduling ensures instances are provisioned and warm before market open, avoiding the 4-minute boot delay, while Cloud Pub/Sub queue depth scaling dynamically adjusts capacity for unexpected workload variations throughout the day.

Adım Adım Çözüm

1
Analyze the workload scaling bottleneck
Identified that the 4-minute instance initialization delay causes latency spikes during sudden 30-second traffic surges at predictable times.
Reactive auto-scaling cannot provisions compute resources fast enough when workload initialization time exceeds traffic surge speed.
2
Evaluate proactive capacity planning strategies
Scheduled auto-scaling pre-provisions capacity before known spikes, guaranteeing warm instances are available at market open.
Pre-warming compute resources removes startup latency from the critical processing path.
3
Select metric for dynamic off-peak scaling
Cloud Pub/Sub unacknowledged message count provides an accurate measure of pending work for asynchronous queue processors.
Queue depth metrics reflect actual work backlog better than CPU utilization for I/O-bound or message-driven processing.

Anahtar Kavram

Combining scheduled auto-scaling for predictable spikes with custom metric queue-depth scaling for asynchronous workloads.
Tahmini Süre:2m 0s
Soru 188Soru

A cloud administrator regularly manages infrastructure across separate development, staging, and production Google Cloud projects from a single workstation using the gcloud CLI. Currently, the administrator manually re-authenticates or overrides environment variables whenever switching target environments, which increases the risk of executing administrative commands against the wrong project. Which approach aligns with Google Cloud best practices for managing and switching between multiple environment settings cleanly when using the gcloud CLI?

Cevabı ve açıklamayı göster

Cevap: Create separate named gcloud configurations for each environment using gcloud config configurations create, define project and account settings within each configuration, and activate the required profile using gcloud config configurations activate.

Cevap

Create and activate separate named gcloud configurations for each target project environment using the gcloud config configurations command group.
The gcloud CLI provides native support for multiple named configurations via `gcloud config configurations`. Each named configuration maintains its own set of properties, including default project ID, active user account, region, and zone. Activating a specific named configuration instantly switches the active operational context, preventing accidental execution against unintended projects without requiring static credential files.

Adım Adım Çözüm

1
Identify the requirement for isolated, reproducible CLI environment contexts.
Recognize that managing multiple Google Cloud projects requires switching gcloud settings like default project, region, zone, and authentication identity.
Manual overrides via environment variables or continuous re-authentication lead to configuration errors and operational risk.
2
Evaluate the native gcloud CLI features designed for multi-environment context management.
Determine that `gcloud config configurations` provides named profile management for distinct environment settings.
Named configurations isolate settings into discrete profiles that can be created, configured, and activated on demand.
3
Select the correct sequence of gcloud configuration management commands.
Use `gcloud config configurations create <name>` to establish profiles for development, staging, and production, and `gcloud config configurations activate <name>` to switch contexts safely.
This avoids downloading static service account keys, maintains security best practices, and prevents accidental operations in the wrong project environment.

Anahtar Kavram

gcloud Named Configurations for Environment Management
Soru 189Soru

An enterprise online gaming company is launching a global game update expected to triple active connection traffic within minutes. The telemetry ingestion pipeline runs on Google Kubernetes Engine (GKE) worker nodes and is primarily I/O-bound as it handles high-volume persistent WebSocket streams and message queues. During load testing, scaling nodes and pods based on CPU utilization failed to react quickly enough to queue backlog spikes, and sudden autoscaling attempts were rejected due to regional limits. Which TWO architectural and operational actions should a Cloud Architect recommend to ensure auto-scaling reliability and guarantee resource availability during peak launch events?

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

Cevabı ve açıklamayı göster

Cevap: Configure the Kubernetes Horizontal Pod Autoscaler (HPA) using custom Cloud Monitoring metrics based on message queue depth and incoming connection rate instead of CPU utilization.; Submit regional Compute Engine resource quota increase requests well before launch and purchase Compute Engine capacity reservations for the required machine types.

Cevap

The Cloud Architect should configure the Kubernetes Horizontal Pod Autoscaler using custom Cloud Monitoring metrics (such as queue depth and connection rate) and proactively request regional Compute Engine quota increases along with capacity reservations.
For I/O-bound and queue-based workloads, scaling based on CPU utilization is insufficient because memory, network sockets, or message backlogs saturate before CPU usage spikes. Using custom Cloud Monitoring metrics like queue depth or active connection rate allows the HPA to scale workloads accurately. Additionally, cluster autoscaling requires sufficient underlying Compute Engine quotas and physical compute capacity. Proactively requesting regional quota increases and securing capacity reservations ensures that GKE can successfully provision underlying VM nodes when traffic bursts occur.

Adım Adım Çözüm

1
Analyze workload scaling bottlenecks
Identified that the ingestion pipeline is I/O-bound, meaning CPU utilization does not reflect true load backlog.
Scaling on CPU metrics fails for I/O-bound or messaging workloads.
2
Select appropriate autoscaling metrics
Utilize custom Cloud Monitoring metrics (queue depth / incoming connection rate) to drive pod autoscaling.
Allows proactive pod provisioning before processing latency spikes.
3
Evaluate infrastructure capacity constraints
Identify that node autoscaling requires underlying GCP compute quotas and physical instance availability.
Autoscaling attempts will fail if project quotas or zonal compute capacities are exhausted.
4
Implement capacity planning procedures
Request regional quota increases in advance and acquire Compute Engine capacity reservations for the GKE node pools.
Guarantees resource quota approval and physical compute hardware availability during peak demand.

Anahtar Kavram

I/O-Bound Custom Metric Autoscaling and Proactive Capacity Planning
Soru 190Soru

An enterprise retail platform is preparing for an annual flash sale expected to increase incoming order traffic by 500% within minutes. The order processing service runs on a Compute Engine Managed Instance Group (MIG) that consumes messages from a Cloud Pub/Sub topic. Stress testing reveals that scaling the MIG based on CPU utilization is ineffective because workers spend significant time waiting on external database I/O, leading to delayed scale-out and queue backlog buildup. Additionally, the required peak capacity for the event exceeds the project's current regional N2 CPU limits. Which TWO actions should the Cloud Architect take to ensure operational reliability and seamless capacity scaling during the flash sale?

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

Cevabı ve açıklamayı göster

Cevap: Configure the MIG autoscaler to scale based on a custom Cloud Monitoring metric tracking Cloud Pub/Sub unacknowledged message queue depth per instance.; Submit a regional quota increase request for Compute Engine N2 CPUs in the target region well in advance of the sale event.

Cevap

The Cloud Architect should configure the MIG autoscaler using a custom Cloud Monitoring metric for Cloud Pub/Sub unacknowledged message queue depth and submit a regional Compute Engine N2 CPU quota increase request in advance.
For I/O-bound background worker services consuming from message queues, CPU utilization is an unreliable metric because worker threads spend time blocked on external database operations while keeping CPU usage low. Configuring the Managed Instance Group to scale based on a custom Cloud Monitoring metric tracking Cloud Pub/Sub unacknowledged message count ensures scaling responds immediately to queue backlog. Furthermore, GCP resource quotas represent administrative limits that do not expand automatically; submitting a regional N2 CPU quota request prior to the high-traffic event guarantees that Compute Engine can provision the required VM instances during scale-out.

Adım Adım Çözüm

1
Identify the primary autoscaling bottleneck for I/O-bound workloads
Determine that CPU utilization does not reflect worker thread I/O wait times, whereas Cloud Pub/Sub queue depth accurately measures pending backlog.
Queue depth metrics trigger rapid scaling proportional to actual incoming work rather than CPU load.
2
Assess capacity limits and quota requirements
Recognize that anticipated peak instance counts exceed current regional N2 CPU quota limits.
GCP quotas require manual request and approval processes; failure to request quotas in advance will cause instance creation failures when scaling out.

Anahtar Kavram

Custom Metric Autoscaling and Proactive Capacity Quota Planning
Soru 191Soru

A financial services organization is establishing an automated data ingestion pipeline from an external identity platform into Google Cloud. The security team must enforce service account lifecycle security and ensure sensitive database credentials stored in Secret Manager are protected according to Google Cloud security standards. The architecture must eliminate static service account keys, strictly enforce least privilege access, and allow key lifecycle control using Google Cloud KMS. Which TWO security controls should the architecture team implement?

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

Cevabı ve açıklamayı göster

Cevap: Configure Workload Identity Federation with the external identity provider to issue short-lived credentials for pipeline authentication instead of static service account keys.; Grant the service account the Secret Manager Secret Accessor role on target individual secrets and configure Secret Manager to encrypt secret versions using Cloud KMS Customer-Managed Encryption Keys (CMEK).

Cevap

The team should configure Workload Identity Federation to eliminate service account keys, and grant the Secret Manager Secret Accessor role on specific secrets with Cloud KMS CMEK encryption.
Workload Identity Federation allows external workloads to exchange security tokens for short-lived Google Cloud access tokens, removing the need to manage long-lived service account keys. Secret Manager supports encryption using Customer-Managed Encryption Keys (CMEK) managed via Cloud KMS. Enforcing least privilege requires granting the Secret Manager Secret Accessor role on specific secrets rather than granting project-wide or administrative roles.

Adım Adım Çözüm

1
Identify keyless authentication strategy for external workload.
Workload Identity Federation allows external identity providers to federate with Google Cloud IAM and receive short-lived OAuth tokens.
This eliminates the security risk of exporting and managing long-lived service account JSON keys.
2
Determine least privilege access control for Secret Manager.
Granting roles/secretmanager.secretAccessor specifically on the designated secret limits access exclusively to required payload versions.
Applying fine-grained resource-level access enforces strict IAM boundary security.
3
Select encryption control mechanism.
Configuring Customer-Managed Encryption Keys (CMEK) via Cloud KMS enables key rotation, revoking capabilities, and audit control within Google Cloud.
Secret Manager natively integrates with Cloud KMS for customer-managed envelope encryption.

Anahtar Kavram

Secrets Management and Service Account Lifecycle Security
Soru 192Soru

A financial services organization deploys a Go-based microservice on Google Kubernetes Engine (GKE) that programmatically ingests data by publishing messages to Cloud Pub/Sub and writing records to Cloud Bigtable using official Google Cloud Client Libraries. During high-volume market events, the application experiences transient HTTP 429429 (Too Many Requests) rate limit errors and HTTP 503503 (Service Unavailable) errors. The security and platform architecture teams require a solution that adheres to GCP authentication best practices while ensuring resilient API interaction and minimal operational overhead. Which implementation strategy should the cloud architect recommend?

Cevabı ve açıklamayı göster

Cevap: Utilize the built-in retry policies of the Google Cloud Client Libraries configured with truncated exponential backoff and randomized jitter, while authenticating via Application Default Credentials (ADC) bound to a Kubernetes Service Account using Workload Identity.

Cevap

Utilize the built-in retry policies of the Google Cloud Client Libraries configured with truncated exponential backoff and randomized jitter, while authenticating via Application Default Credentials (ADC) bound to a Kubernetes Service Account using Workload Identity.
The option recommending built-in Google Cloud Client Library retry policies with truncated exponential backoff and jitter alongside Workload Identity correctly addresses both API rate limiting and secure authentication. Google Cloud Client Libraries natively support Application Default Credentials (ADC) and automatic retry handling for idempotent requests, avoiding static credential management and preventing thundering herd spikes.

Adım Adım Çözüm

1
Analyze authentication requirements for GKE applications
Workload Identity allows Kubernetes Service Accounts to act as IAM Service Accounts using short-lived tokens via Application Default Credentials (ADC), eliminating the need for service account keys.
Hardcoding or bundling static JSON service account keys introduces security vulnerabilities.
2
Evaluate API resilience strategies for transient HTTP 429 and 503 errors
Official Google Cloud Client Libraries provide standard retry mechanisms that use truncated exponential backoff with randomized jitter.
Exponential backoff prevents overwhelming APIs during overload spikes, while jitter prevents synchronization thundering herd problems.
3
Synthesize the architecture recommendation
Combine Workload Identity for identity management with native Client Library retry logic for programmatic GCP API interaction.
This satisfies both security and operational resilience standards for GCP cloud architecture.

Anahtar Kavram

Programmatic GCP API Resilience and Secure Authentication via ADC
Soru 193Soru

An enterprise financial compliance application deployed on Compute Engine Managed Instance Groups (MIGs) processes continuous streaming network traffic. During high-throughput compliance audit cycles, backend instances experience severe latency and drop connections due to socket allocation exhaustion and memory pressure, while average CPU utilization remains at approximately 35%. Furthermore, upcoming quarterly compliance stress testing requires expanding the infrastructure by 300 instances, but past automated scale-out events failed immediately because the target region exceeded baseline vCPU limits. Which combination of autoscaling policy and capacity planning strategies should the Cloud Architect implement to ensure operational reliability?

Cevabı ve açıklamayı göster

Cevap: Configure the MIG autoscaler to use a custom Cloud Monitoring metric reflecting active open socket connections, submit a regional vCPU quota increase request well before the audit cycle, and create compute capacity reservations.

Cevap

Configure the MIG autoscaler using a custom Cloud Monitoring metric for active socket connections, request regional vCPU quota increases in advance, and create compute capacity reservations.
The workload is limited by open socket connections and memory pressure rather than CPU utilization. Therefore, autoscaling must be configured against a custom Cloud Monitoring metric that measures socket exhaustion. Furthermore, large-scale events require proactive capacity planning, which involves requesting regional vCPU quota increases well in advance and creating zonal capacity reservations to guarantee compute availability.

Adım Adım Çözüm

1
Identify the performance bottleneck
Recognize that CPU utilization is low (~35%) while memory and network sockets are exhausted, indicating an I/O and connection-bound service.
Standard CPU-based autoscaling is ineffective for workloads bound by memory or network socket pool limits.
2
Select the appropriate autoscaling metric
Implement a custom Cloud Monitoring metric tracking open network sockets to trigger MIG autoscaling decisions accurately.
Custom metrics allow autoscaling policies to respond directly to the application's actual resource constraints.
3
Address capacity constraints and quota requirements
Proactively request regional vCPU quota increases from Google Cloud and provision compute capacity reservations prior to stress testing.
Quota increases require lead time for approval, and capacity reservations guarantee VM slot availability in specific zones during large scale-out events.

Anahtar Kavram

Custom metric autoscaling for I/O-bound workloads combined with proactive quota management and capacity reservations
Soru 194Soru

A digital media production enterprise hosts high-value pre-release video assets within Cloud Storage buckets and processes analytics using BigQuery. The security team must ensure that authorized developers and automated pipelines working within the environment cannot exfiltrate raw assets to external Google Cloud resources outside the organization. Additionally, access to Google APIs from on-premises workstations must be strictly constrained to private network paths without exposing traffic to the public internet. Which TWO security controls should you implement to satisfy these requirements?

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

Cevabı ve açıklamayı göster

Cevap: Define a VPC Service Controls perimeter surrounding the project containing the Cloud Storage buckets and BigQuery datasets.; Configure Private Google Access for on-premises hosts by routing traffic destined for restricted.googleapis.com over Cloud VPN or Cloud Interconnect.

Cevap

The architectural requirements are met by establishing a VPC Service Controls perimeter around the project resources to prevent exfiltration, and configuring Private Google Access for on-premises hosts via restricted.googleapis.com over hybrid connectivity.
Combining VPC Service Controls with Private Google Access for on-premises hosts using the restricted VIP creates a complete defense-in-depth perimeter. VPC Service Controls ensures that even authorized credentials cannot copy Cloud Storage or BigQuery data into projects outside the security perimeter. Routing on-premises requests via Cloud Interconnect or VPN to restricted.googleapis.com ensures all API calls stay on private network paths and comply with perimeter restrictions.

Adım Adım Çözüm

1
Evaluate data exfiltration protection requirements for Google Cloud APIs
Identify that IAM permissions alone cannot prevent data movement to external GCP projects, requiring VPC Service Controls perimeter context boundaries.
VPC Service Controls mitigates the risk of insider threats and exfiltration by isolating resource API communication within defined perimeters.
2
Determine private connectivity mechanism for on-premises access to Google APIs
Select Private Google Access for on-premises hosts mapped to restricted.googleapis.com.
Routing on-premises traffic through Cloud Interconnect/VPN to the restricted VIP ensures API calls bypass public internet routes and remain compatible with VPC Service Controls.

Anahtar Kavram

Perimeter Security & Data Exfiltration Prevention
Soru 195Soru

An enterprise logistics company runs a critical real-time inventory reservation service deployed on Google Kubernetes Engine (GKE) backed by Cloud Spanner. The service processes high-throughput synchronous HTTP requests from mobile applications. To balance feature velocity with operational stability, the Site Reliability Engineering (SRE) team needs to define metrics and alerting mechanisms. Which TWO of the following practices should the team implement? (Select TWO)

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

Cevabı ve açıklamayı göster

Cevap: Define the Service Level Indicator (SLI) as the ratio of successful HTTP requests (non-5xx5xx status codes) to total valid requests, evaluated over a rolling 30-day window.; Implement multi-window, multi-burn-rate alerts based on error budget consumption rates rather than static metric thresholds.

Cevap

The team should define the SLI as the ratio of successful HTTP requests to total valid requests over a rolling 30-day window, and implement multi-window, multi-burn-rate alerts based on error budget consumption rates.
Defining the SLI as the ratio of successful requests to total valid requests accurately measures customer-facing reliability. Pairwise, implementing multi-window, multi-burn-rate alerting monitors how quickly the service consumes its error budget, allowing teams to catch both fast outages and slow burn rate trends without generating false-positive alert fatigue.

Adım Adım Çözüm

1
Identify the proper Service Level Indicator (SLI) definition for a synchronous web service.
SLI is defined as the ratio of good events (successful HTTP requests) to total events over a defined window.
SLIs must quantify user experience directly rather than internal server resource metrics.
2
Select the appropriate alerting strategy based on Site Reliability Engineering (SRE) best practices.
Multi-window, multi-burn-rate alerts are chosen to monitor error budget consumption.
Burn-rate alerting triggers based on how fast the error budget is being consumed, preventing unnecessary alerts for transient spikes while ensuring significant outages are paged immediately.
3
Evaluate and eliminate distractors based on common SRE antipatterns.
Reject static CPU utilization alerting and inverted SLI/SLO definitions.
Resource utilization alerts do not directly correlate with user impact, and swapping SLI/SLO concepts causes misconfigured monitoring pipelines.

Anahtar Kavram

Defining SLIs as ratio metrics of user-impacting events and configuring error budget burn-rate alerts.
Tahmini Süre:2m 0s
Soru 196Soru

An enterprise cloud architect is designing a multi-layered security model for a multi-tenant SaaS application hosted on Google Cloud. Match each network security and perimeter requirement on the left with the most appropriate Google Cloud security mechanism on the right.

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

Öğeler

Protect web applications behind an HTTP(S) Load Balancer against Layer 7 attacks such as SQL injection (SQLi) and Cross-Site Scripting (XSS).
Prevent authorized internal users from exfiltrating sensitive BigQuery data to unauthorized external Google Cloud storage locations or projects.
Enforce organization-wide firewall rules across multiple VPC networks using dynamic resource metadata rather than IP subnet ranges.
Provide secure, private cross-tenant API access between VPCs without establishing full network layer IP routability or transitive peering.

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

Layer 7 web attack mitigation matches Cloud Armor WAF Security Policies; BigQuery data exfiltration prevention matches VPC Service Controls Service Perimeters; Organization-wide policy enforcement via dynamic metadata matches Hierarchical Firewall Policies with Secure Tags; Private cross-VPC API access without transitive peering matches Private Service Connect (PSC).
Each security requirement aligns directly with standard Google Cloud perimeter defense products: Cloud Armor handles edge Layer 7 protection, VPC Service Controls restrict managed API data movement, Hierarchical Firewalls with Secure Tags manage organization-wide network policy based on tags, and Private Service Connect facilitates isolated cross-VPC service access.

Adım Adım Çözüm

1
Analyze requirement 1 (Layer 7 web protection against SQLi/XSS at load balancer)
Identify Cloud Armor as the perimeter WAF tool designed specifically for Google Cloud external HTTP(S) Load Balancing.
Cloud Armor evaluates inbound traffic at the edge before reaching backend compute resources.
2
Analyze requirement 2 (Preventing data exfiltration from Google APIs like BigQuery)
Identify VPC Service Controls as the mechanism to build perimeters around GCP managed services.
IAM rules control who can access resources, but VPC Service Controls define where data can be accessed from and transferred to.
3
Analyze requirement 3 (Enforcing organization-level firewalls using metadata instead of IPs)
Identify Hierarchical Firewall Policies combined with Secure Tags.
Hierarchical rules apply top-down from organization/folder levels, while Secure Tags provide access control evaluation based on identity/metadata tags rather than IP addresses.
4
Analyze requirement 4 (Private microservice consumption across VPC boundaries without peering)
Identify Private Service Connect (PSC).
PSC uses producer-consumer endpoint mapping to allow private connection across administrative boundaries without establishing full VPC network peering.

Anahtar Kavram

Google Cloud Perimeter Security and Network Controls (Cloud Armor, VPC Service Controls, Hierarchical Firewalls, Private Service Connect)
Soru 197Soru

A smart grid energy company is designing a hybrid cloud connectivity topology between its primary operational control center on-premises and Google Cloud. The telemetry ingest workload requires a minimum sustained throughput of 12 Gbps and an availability SLA of 99.99%. Furthermore, the on-premises controllers must communicate with resources distributed across multiple workloads in distinct Virtual Private Clouds (VPCs) via a central hub VPC. How should the cloud architect design the hybrid network topology to meet all bandwidth, SLA, and routing requirements?

Cevabı ve açıklamayı göster

Cevap: Provision a 99.99% availability Dedicated Interconnect topology connected to the hub VPC, and deploy Network Connectivity Center (NCC) with Cloud Router to manage hybrid dynamic routing to the spoke VPCs.

Cevap

Provision a 99.99% availability Dedicated Interconnect topology connected to the hub VPC, and deploy Network Connectivity Center (NCC) with Cloud Router to manage hybrid dynamic routing to the spoke VPCs.
Dedicated Interconnect provides 10 Gbps or 100 Gbps physical circuits capable of meeting the sustained 12 Gbps requirement and can be deployed across dual edge availability domains for a 99.99% SLA. Combining this with Network Connectivity Center or Shared VPC enables proper dynamic routing without relying on unsupported VPC Peering transitivity.

Adım Adım Çözüm

1
Evaluate throughput and SLA requirements for hybrid connectivity.
Sustained 12 Gbps throughput exceeds standard Cloud VPN tunnel capacities (3 Gbps per tunnel) and requires Dedicated Interconnect (10 Gbps or 100 Gbps circuits) to achieve enterprise reliability and 99.99% SLA.
Dedicated Interconnect is the recommended GCP solution for bandwidth requirements exceeding 10 Gbps and strict high-availability SLAs.
2
Evaluate multi-VPC routing topology for on-premises access.
VPC Network Peering does not support transitive routing (i.e., on-premises -> Hub VPC -> Peered VPC). Network Connectivity Center (NCC) or a Shared VPC architecture must be used to allow hybrid on-premises access to multiple VPCs.
VPC Network Peering only exchanges routes between directly peered VPCs and blocks transitive traffic from external hybrid connections.

Anahtar Kavram

Hybrid Connectivity Selection & VPC Peering Non-Transitivity
Soru 198Soru

An e-commerce enterprise hosts a public-facing web API on Google Kubernetes Engine (GKE) behind an HTTP(S) Load Balancer and stores sensitive transaction analytics in Cloud Storage and BigQuery. The security team needs to satisfy two core requirements: mitigate Layer 7 web application attacks (such as SQL injection) at the network edge, and prevent authorized users from copying internal datasets to external storage buckets outside the organization perimeter.

Which TWO security and perimeter controls should you implement to fulfill these requirements?

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

Cevabı ve açıklamayı göster

Cevap: Configure VPC Service Controls to establish a service perimeter around the Cloud Storage and BigQuery resources.; Apply Cloud Armor security policies with WAF rules to the backend service of the external HTTP(S) Load Balancer.

Cevap

The two correct controls are establishing VPC Service Controls around Cloud Storage and BigQuery, and applying Cloud Armor security policies to the external HTTP(S) Load Balancer.
Establishing VPC Service Controls builds a perimeter around storage and analytics services to block unauthorized data transfers outside the project boundary. Deploying Cloud Armor security policies on the external HTTP(S) Load Balancer protects GKE web applications against Layer 7 threats like SQL injection at the network edge.

Adım Adım Çözüm

1
Evaluate perimeter exfiltration controls for Google Cloud APIs
VPC Service Controls provides perimeter isolation for Cloud Storage and BigQuery, stopping data egress to external projects even when IAM access is granted.
IAM authorization does not restrict destination buckets, making VPC Service Controls necessary for exfiltration defense.
2
Evaluate edge application security for HTTP services
Cloud Armor security policies attach to external HTTP(S) Load Balancers to inspect incoming web traffic against WAF rules.
Cloud Armor filters Layer 7 threats like SQL injection and mitigates volumetric attacks before traffic reaches GKE workloads.

Anahtar Kavram

Combining Cloud Armor for edge WAF protection and VPC Service Controls for data exfiltration prevention.
Soru 199Soru

A multinational automotive software enterprise is connecting its on-premises build servers to Google Cloud. The workload requires a sustained network throughput of 8 Gbps between on-premises data centers and Google Cloud resources. Additionally, the company operates three separate environments in Google Cloud—Production, Staging, and Shared Services—that all require private connectivity to on-premises resources. The network engineering team wants to centralize network administration, avoid creating separate hybrid connections for each environment, and eliminate routing issues caused by VPC Network Peering non-transitivity. Which network architecture should you recommend?

Cevabı ve açıklamayı göster

Cevap: Design a Shared VPC architecture using a central Host VPC with Dedicated Interconnect and Cloud Router, and attach the Production, Staging, and Shared Services projects as Service Projects sharing the Host VPC subnets.

Cevap

Design a Shared VPC architecture using a central Host VPC with Dedicated Interconnect and Cloud Router, and attach the Production, Staging, and Shared Services projects as Service Projects sharing the Host VPC subnets.
The correct solution uses Shared VPC with Dedicated Interconnect. Shared VPC allows central management of network resources (such as Cloud Routers and Interconnect VLAN attachments) in a Host VPC. Because Service Projects (Production, Staging, Shared Services) share subnets within the same Host VPC network, all resources can communicate directly with on-premises networks over the 8 Gbps Dedicated Interconnect without being blocked by VPC Network Peering non-transitivity.

Adım Adım Çözüm

1
Evaluate throughput requirement against hybrid connectivity options.
Sustained 8 Gbps bandwidth exceeds standard HA VPN single tunnel limits (typically 3 Gbps per tunnel), indicating Dedicated Interconnect or high-bandwidth Partner Interconnect is required.
Choosing the appropriate hybrid connection type prevents bandwidth bottlenecks under heavy load.
2
Evaluate multi-VPC routing requirements and constraints.
VPC Network Peering is non-transitive, meaning peered spokes cannot reach on-premises networks through a central hub's hybrid connection.
Understanding network topology constraints avoids invalid transitive routing designs.
3
Select centralized topology pattern.
Shared VPC allows network admins to maintain Interconnect attachments and Cloud Routers in a Host VPC while letting Service Projects (Production, Staging, Shared Services) utilize those network paths directly within a single logical network perimeter.
Shared VPC eliminates non-transitivity issues and avoids redundant connection provisioning.

Anahtar Kavram

Shared VPC vs VPC Peering with Interconnect for Hybrid Connectivity
Tahmini Süre:2m 0s
Soru 200Soru

An automotive IoT enterprise ingests streaming vehicle telemetry into Cloud Storage buckets located inside Project-Ingest. An analytics team operating out of Project-Analytics requires direct read access to this telemetry to run BigQuery Omni and Dataproc jobs. The chief information security officer (CISO) mandates that raw telemetry data must be strictly prevented from being exfiltrated to external Google Cloud resources or public internet destinations, even by identities holding legitimate read permissions. Additionally, Project-Analytics is connected via VPC Network Peering to a shared Project-Management network, but Project-Ingest has no direct VPC Network Peering connection to Project-Management. Which security architecture should a Cloud Architect implement to satisfy these security and operational requirements?

Cevabı ve açıklamayı göster

Cevap: Configure a single VPC Service Controls perimeter that includes both Project-Ingest and Project-Analytics, restricting Google Cloud Storage and BigQuery API traffic to the restricted.googleapis.com IP range.

Cevap

Configure a single VPC Service Controls perimeter encompassing both projects while routing API traffic through restricted Google APIs.
The correct solution involves creating a VPC Service Controls perimeter containing both Project-Ingest and Project-Analytics, configured with restricted API access. VPC Service Controls isolates sensitive data within specified GCP projects, preventing credentials from being used to copy data to external, non-perimeter storage buckets or locations even if the user has read permissions.

Adım Adım Çözüm

1
Analyze perimeter security and exfiltration requirements
Identified that IAM alone cannot prevent an authorized identity from writing data to an external location.
VPC Service Controls is specifically designed to isolate Google Cloud service resources and mitigate data exfiltration risks.
2
Evaluate network connectivity constraints
Recognized that VPC Network Peering is non-transitive in GCP.
Peering relationships cannot be chained transitively to route traffic between non-directly peered networks.
3
Formulate perimeter architecture
Place Project-Ingest and Project-Analytics inside a VPC Service Controls service perimeter and enforce restricted VIP endpoints (restricted.googleapis.com).
This guarantees that API access between the projects works securely while blocking egress of data outside the defined perimeter.

Anahtar Kavram

VPC Service Controls and Perimeter Defense
ÖncekiSayfa 10 / 80Sonraki
Tüm alıştırma soruları — Google Cloud Professional Cloud Architect | Examkin