Tüm alıştırma soruları

1598 soru

Soru 1321Soru

An international retail company is architecting a new global e-commerce order management platform. The platform has two critical requirements: 1) A highly available database that supports multi-region, strongly consistent ACID transactions for customer orders across North America and Europe, and 2) A scalable object storage system for product image assets that integrates with Cloud KMS for automated key lifecycle management. Which TWO storage and database configurations should you choose to satisfy these requirements?

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

Cevabı ve açıklamayı göster

Cevap: Deploy Cloud Spanner with a multi-region instance configuration to host the transactional order database.; Store product media assets in Cloud Storage buckets encrypted using Customer-Managed Encryption Keys (CMEK) managed via Cloud KMS.

Cevap

Select Cloud Spanner with a multi-region configuration for multi-region transactional writes, and store product media in Cloud Storage encrypted with Customer-Managed Encryption Keys (CMEK) via Cloud KMS.
Cloud Spanner natively delivers multi-region, horizontally scalable, strongly consistent ACID transactions for relational databases across multiple continents. Cloud Storage with Customer-Managed Encryption Keys (CMEK) provides scalable object storage while integrating with Google Cloud KMS for automated key creation, rotation, and lifecycle policy enforcement.

Adım Adım Çözüm

1
Evaluate transactional database requirements for multi-region global consistency.
Determine that Cloud Spanner is required for multi-region, strongly consistent relational ACID transactions.
Cloud SQL only supports primary writes within a single region and cannot provide multi-region write consistency.
2
Evaluate object storage and key management requirements for product media assets.
Identify Cloud Storage configured with Customer-Managed Encryption Keys (CMEK) via Cloud KMS.
CMEK integrates with Cloud KMS for key rotation and access policies, whereas Customer-Supplied Keys (CSEK) require manually passing raw keys with each request.

Anahtar Kavram

Selecting multi-region relational database services and managed key storage solutions based on consistency and operational requirements.
Soru 1322Soru

An aerospace engineering enterprise is architecting a mission-critical global flight telematics platform on Google Cloud. The architecture requires a relational database that guarantees multi-region strong consistency, a zero Recovery Point Objective (RPO), and a near-zero Recovery Time Objective (RTO) during a regional outage. Additionally, the application tier consists of containerized stateless HTTP microservices that must automatically scale with traffic spikes while requiring minimal operational infrastructure management overhead. Which solution architecture satisfies these technical requirements and high availability objectives?

Cevabı ve açıklamayı göster

Cevap: Deploy the containerized stateless microservices on Cloud Run across multiple regions behind a Global External HTTP(S) Load Balancer, and store the relational telemetry data in a multi-region Cloud Spanner instance.

Cevap

Deploying the stateless containerized microservices to Cloud Run across multiple regions behind a Global External HTTP(S) Load Balancer combined with a multi-region Cloud Spanner database instance fulfills all high availability, operational, and consistency requirements.
The combination of Cloud Run and multi-region Cloud Spanner delivers an architecture that meets all specified operational and recovery constraints. Cloud Run provides serverless management for stateless HTTP containers, scaling dynamically with demand. Multi-region Cloud Spanner provides synchronous replication across regions using Paxos consensus, ensuring multi-region strong consistency, zero RPO, and automatic near-zero RTO failover.

Adım Adım Çözüm

1
Evaluate the database tier requirements for consistency and availability
The requirements demand a relational database with multi-region strong consistency, RPO = 0, and RTO near zero.
Cloud Spanner uses TrueTime and synchronous multi-region replication to provide strong global transactional consistency and automatic failover with zero RPO.
2
Evaluate the compute tier requirements for operational overhead and workload type
The workload consists of containerized stateless HTTP microservices that require minimal management overhead and automatic scaling.
Cloud Run is a fully managed serverless container platform that automatically scales HTTP workloads from zero to peak demand without requiring infrastructure cluster management.
3
Synthesize the compute and database choices into a unified architecture
Combining Cloud Run with a Global External HTTP(S) Load Balancer and multi-region Cloud Spanner satisfies all technical constraints.
This end-to-end architecture guarantees global high availability, zero RPO regional failover, and serverless compute efficiency.

Anahtar Kavram

Multi-region high availability design using Cloud Run serverless compute and Cloud Spanner synchronous relational database storage.
Soru 1323Soru

Match each enterprise data requirement on the left with the most appropriate Google Cloud storage or database service on the right based on access patterns, scaling, and architectural capabilities.

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

Öğeler

Global OLTP application requiring horizontal scalability, strong consistency across multiple geographic regions, and relational SQL support.
High-throughput IoT sensor data ingestion requiring single-digit millisecond read/write latency and seamless scaling for key-value time-series data.
Regional relational database workload needing full PostgreSQL compatibility, ACID compliance, managed backups, and high-availability failover.
Enterprise analytical data warehouse capable of querying petabyte-scale structured data using SQL without managing underlying infrastructure.

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

Global multi-region strong consistency matches Cloud Spanner; high-throughput IoT time-series data matches Cloud Bigtable; regional PostgreSQL relational OLTP matches Cloud SQL for PostgreSQL; petabyte-scale analytics matches BigQuery.
Each GCP database service is optimized for specific workload profiles: Cloud Spanner handles globally scalable relational OLTP; Cloud Bigtable handles massive throughput NoSQL key-value streams; Cloud SQL handles standard regional relational databases; and BigQuery handles large-scale analytics and data warehousing.

Adım Adım Çözüm

1
Analyze workload requirements for transactional scope and geographical distribution.
Identified global multi-region transactional needs versus regional single-instance requirements.
Global relational workloads requiring horizontal scale map directly to Cloud Spanner, whereas single-region relational workloads map to Cloud SQL.
2
Differentiate non-relational high-throughput operational storage from analytical warehousing.
Categorized key-value IoT ingestion as operational NoSQL and large SQL reporting as analytical OLAP.
Cloud Bigtable provides low-latency key-value NoSQL capabilities for high-speed write streams, while BigQuery provides serverless OLAP capabilities for petabyte-scale analysis.
3
Pair each requirement to its optimal Google Cloud database product based on best-practice design patterns.
All four workload patterns are mapped to their corresponding Google Cloud target services.
Matching access patterns and SLAs ensures optimal performance, reliability, and cost-efficiency.

Anahtar Kavram

Selecting GCP Database and Storage Resources by Access Pattern and Workload Characteristics
Tahmini Süre:1m 30s
Soru 1324Soru

An enterprise software company is migrating an internal billing platform to Google Cloud. The workload operates strictly within a single GCP region and requires a managed relational database with full PostgreSQL compatibility, automatic multi-zone high availability, and data encryption at rest managed through Cloud KMS. Which database architecture should you recommend to meet these requirements with minimal operational cost and complexity?

Cevabı ve açıklamayı göster

Cevap: Deploy Cloud SQL for PostgreSQL configured with high availability across multiple zones and Customer-Managed Encryption Keys (CMEK).

Cevap

The optimal architecture is to deploy Cloud SQL for PostgreSQL configured with high availability across zones and Customer-Managed Encryption Keys (CMEK) via Cloud KMS.
Cloud SQL for PostgreSQL provides a fully managed relational database engine tailored for single-region workloads. Enabling high availability provisions a standby instance in a secondary zone within the same region, and integrating Cloud KMS satisfies Customer-Managed Encryption Key (CMEK) compliance with minimal cost and management effort.

Adım Adım Çözüm

1
Analyze database workload geographic scope and engine requirements
The application operates strictly within a single region and requires PostgreSQL compatibility, eliminating the need for globally distributed databases like Cloud Spanner.
Matching workload scope prevents over-provisioning cost and architectural complexity.
2
Evaluate high availability and key management requirements
Cloud SQL natively supports multi-zone regional high availability failover and integrates directly with Cloud KMS for CMEK data encryption at rest.
CMEK allows central security administration via standard GCP key management tools.

Anahtar Kavram

Selecting appropriate managed GCP database services based on regional scale and encryption requirements.
Tahmini Süre:1m 30s
Soru 1325Soru

A regional freight logistics company is designing a high-availability backend on Google Cloud for its shipment management platform within a single GCP region. The architecture requires a stateless HTTP microservice tier that automatically scales during peak hours without server management overhead. The relational database tier requires strict ACID compliance, a zero Recovery Point Objective (RPO=0RPO = 0) in the event of a single zonal outage, and automated multi-zone failover to maintain a 99.99% availability target. Which architecture meets these technical requirements with the lowest operational complexity?

Cevabı ve açıklamayı göster

Cevap: Deploy the stateless microservices to Cloud Run, and store relational data in a regional Cloud SQL for PostgreSQL instance with High Availability (HA) enabled across dual zones.

Cevap

Deploying stateless microservices on Cloud Run backed by a regional Cloud SQL for PostgreSQL instance with High Availability (HA) enabled across dual zones provides serverless autoscaling and zero-RPO zonal redundancy with minimum operational overhead.
Combining serverless Cloud Run for the compute tier with dual-zone Cloud SQL HA for the storage tier fulfills all stateless scaling and database zero-RPO (RPO=0RPO = 0) failover requirements while keeping operational complexity low.

Adım Adım Çözüm

1
Evaluate compute tier requirements
Cloud Run is selected because it delivers fully managed serverless autoscaling for stateless HTTP workloads, eliminating node/cluster management overhead.
The scenario requires zero server management overhead for stateless HTTP microservices.
2
Evaluate database availability and RPO requirements
Cloud SQL with High Availability (HA) enabled is selected.
Cloud SQL HA uses synchronous replication to a standby instance in a secondary zone within the same region, guaranteeing RPO=0RPO = 0 and automated failover during a zonal outage.
3
Assess architectural complexity and scope
Cloud SQL HA satisfies the single-region 99.99% availability goal without needing multi-region services like Cloud Spanner.
Selecting globally distributed database services for a single-region deployment adds unnecessary cost and operational complexity.

Anahtar Kavram

Single-Region High Availability and DR Alignment
Soru 1326Soru

A global genomics research enterprise receives daily batch uploads totaling 50 TB50\text{ TB} of raw DNA sequencing data from partner laboratories around the world. The uploads occur unpredictably throughout the day. Each file requires a 20-minute containerized processing pipeline to extract variant metadata before storing the results. The raw files must remain instantly available for audit for 30 days, after which they are accessed less than once per year but must be retained for 7 years to meet compliance laws. The business goal is to minimize compute and storage infrastructure costs while avoiding server maintenance overhead. Which two architectural decisions should you recommend? (Select TWO)

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

Cevabı ve açıklamayı göster

Cevap: Execute the processing workload using Cloud Run jobs triggered automatically by Eventarc Cloud Storage object creation events.; Implement Cloud Storage Object Lifecycle Management to transition raw data from Standard to Nearline storage after 30 days, and to Archive storage after 365 days.

Cevap

The optimal architecture combines Cloud Run jobs triggered by Eventarc Cloud Storage events for serverless, cost-effective batch execution, alongside Cloud Storage Object Lifecycle Management to transition raw data to Nearline after 30 days and Archive after 1 year.
Combining Cloud Run jobs (triggered via Eventarc on Cloud Storage object creation) with Cloud Storage Object Lifecycle Management minimizes total cost of ownership (TCO). Cloud Run jobs scale dynamically per file execution without incurring idle compute expenses for the 20-minute processing tasks, while Lifecycle Management automatically shifts 50 TB50\text{ TB} of daily uploads into lower-cost Nearline and Archive tiers as data ages.

Adım Adım Çözüm

1
Analyze compute requirements and cost profile.
The processing task runs for 20 minutes per file upon unpredictable file upload events.
Cloud Run jobs support executions up to 24 hours and scale to zero when no jobs are running, eliminating idle compute costs compared to continuous GKE deployments.
2
Analyze storage access patterns and retention rules.
Files require immediate availability for 30 days, rare access for 7 years, and long-term retention.
Transitioning objects via lifecycle rules to Nearline after 30 days (fast retrieval, lower storage cost) and to Archive after 1 year optimizes cost across the 7-year lifecycle.
3
Evaluate and eliminate sub-optimal architectural options.
Reject GKE and Cloud Spanner recommendations.
GKE introduces unnecessary cluster overhead and baseline costs for event-driven batch jobs, while Cloud Spanner is designed for relational transactional data and is extremely expensive for storing petabytes of raw un-structured files.

Anahtar Kavram

Serverless Event-Driven Batch Architecture & Storage Lifecycle Cost Optimization
Soru 1327Soru

An enterprise financial organization is deploying a globally distributed relational database using Cloud Spanner to process cross-border transactions. Security compliance mandates that all database storage must be encrypted using Customer-Managed Encryption Keys (CMEK) managed in a dedicated central security project, and the database schema must be initialized prior to attaching automated backup policies. In what sequential order should the cloud engineering team execute the provisioning and configuration workflow?

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

Cevabı ve açıklamayı göster

Cevap

The correct operational sequence begins by granting the Cloud Spanner Service Agent the Cloud KMS CryptoKey Encrypter/Decrypter IAM role on the central KMS key. Next, provision the multi-region Cloud Spanner instance. Follow this by creating the Cloud Spanner database while specifying the CMEK key URI. Then, execute DDL statements to populate tables and schema definitions. Finally, establish the automated database backup schedule and Point-in-Time Recovery policy.
The correct workflow adheres to cloud security dependency management and resource hierarchy principles. First, pre-requisite IAM permissions must be granted to the Cloud Spanner Service Agent on the Cloud KMS key in the security project. Second, the parent Cloud Spanner instance must be provisioned. Third, the Cloud Spanner database is created while passing the CMEK key URI so that initial storage allocation is encrypted with the custom key. Fourth, DDL statements are executed against the running database to establish tables and indexes. Fifth, automated backup schedules and PITR retention policies are configured to protect the initialized schema and incoming data.

Adım Adım Çözüm

1
Grant Cloud KMS IAM Role to Service Agent
The Spanner Service Agent receives permission to call Cloud KMS encrypt and decrypt operations.
If permissions are missing when database creation is invoked, the CMEK authorization check fails immediately.
2
Provision Cloud Spanner Instance
Compute node/processing unit resources and multi-region replication topology are allocated.
Cloud Spanner databases exist logically within a parent Cloud Spanner instance environment.
3
Create Spanner Database with CMEK Parameter
An encrypted database container is initialized with underlying storage bound to the specified Cloud KMS key.
CMEK settings in Cloud Spanner cannot be applied retroactively after standard Google-managed key creation.
4
Apply DDL Schema Definitions
Tables, interleave relationships, indexes, and database-level IAM access roles are created.
Database schema definition requires an active, accessible database target.
5
Attach Automated Backup Schedule Policy
Recurring snapshot backups and PITR windows are activated for operational disaster recovery.
Backup policies protect populated data structures and rely on the complete schema setup.

Anahtar Kavram

Cloud Spanner Provisioning and CMEK Integration Workflow
Soru 1328Soru

An enterprise organization is designing a continuous integration and continuous delivery (CI/CD) pipeline on Google Cloud using Cloud Build to automate infrastructure provisioning via Terraform. The security team requires that the build process prevents data exfiltration during execution and enforces least privilege without relying on static credentials or broad access permissions. Which two configuration choices should you implement in your pipeline design to satisfy these requirements?

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

Cevabı ve açıklamayı göster

Cevap: Configure Cloud Build to execute within Private Pools integrated with VPC Service Controls to restrict external network egress during build execution.; Use service account impersonation with fine-grained predefined IAM roles for Cloud Build pipeline execution steps instead of using exported service account JSON keys.

Cevap

The optimal pipeline design requires executing Cloud Build inside Private Pools protected by VPC Service Controls to prevent exfiltration, while enforcing service account impersonation with fine-grained IAM roles to eliminate static keys and primitive permissions.
Executing Cloud Build within Private Pools enclosed by VPC Service Controls isolates network traffic to prevent data exfiltration, while adopting service account impersonation ensures short-lived access with fine-grained IAM roles.

Adım Adım Çözüm

1
Address network exfiltration risk during build execution
Configuring Cloud Build Private Pools with VPC Service Controls restricts build network egress to authorized perimeter endpoints.
Default Cloud Build worker environments run in a multi-tenant network that cannot be bound to VPC perimeter rules.
2
Enforce least privilege access and secure authentication
Using service account impersonation with fine-grained roles provides temporary scoped access for pipeline tasks.
Primitive IAM roles grant excess privileges, and stored JSON key files introduce severe credential leakage risks.
3
Verify state management best practices
Terraform state must be stored in a remote backend like Cloud Storage with versioning enabled rather than local worker storage.
Ephemeral build workers lose local files upon completion, leading to state corruption.

Anahtar Kavram

Secure CI/CD Pipeline Design with Cloud Build Private Pools and IAM Impersonation
Soru 1329Soru

An enterprise deployment server running on-premises executes automated bash scripts using the gcloud CLI to manage resources across multiple Google Cloud projects. The enterprise security policy strictly prohibits storing or generating long-lived service account JSON keys on local disk. The scripts must perform management operations under specific workload service accounts residing in each target project. How should the cloud architect configure the gcloud CLI authentication and execution flow to meet these compliance requirements?

Cevabı ve açıklamayı göster

Cevap: Establish Workload Identity Federation to authenticate the on-premises environment with short-lived tokens, and set the gcloud CLI configuration property auth/impersonate_service_account to the target service account email.

Cevap

Establish Workload Identity Federation to authenticate the on-premises environment with short-lived tokens, and set the gcloud CLI configuration property auth/impersonate_service_account to the target service account email.
Combining Workload Identity Federation with gcloud service account impersonation eliminates the need for downloadable service account JSON keys. Workload Identity Federation provides keyless authentication for external workloads, while configuring gcloud auth/impersonate_service_account ensures all CLI operations execute under the security context of the target service account using short-lived credentials.

Adım Adım Çözüm

1
Identify key management compliance constraints
Local JSON service account key creation and storage are strictly forbidden by enterprise security policy.
Security governance requires keyless authentication using short-lived tokens.
2
Select keyless authentication mechanism for on-premises environment
Use Workload Identity Federation to federate on-premises credentials with GCP Security Token Service (STS).
Workload Identity Federation enables on-premises workloads to authenticate securely without downloadable service account keys.
3
Configure gcloud CLI service account impersonation
Configure gcloud auth/impersonate_service_account or pass the --impersonate-service-account flag.
This instructs gcloud CLI to automatically generate short-lived OAuth 2.0 access tokens for the target service account via the IAM Service Account Credentials API.

Anahtar Kavram

Keyless authentication via Workload Identity Federation and gcloud Service Account Impersonation
Soru 1330Soru

A financial services company hosts containerized microservices on Google Kubernetes Engine (GKE) and stores container images in Artifact Registry. The lead security architect must establish a multi-layered security strategy that prevents untrusted container images from being deployed to production clusters and detects anomalous runtime execution behaviors, such as unauthorized reverse shell attempts within running containers. Which TWO actions should the architect recommend to satisfy these requirements? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Configure Binary Authorization policy on the GKE cluster to enforce image signature validation and attestation checks before deployment.; Enable Container Threat Detection in Security Command Center to monitor container logs and runtime behavior for suspicious process activity.

Cevap

The target security posture requires enforcing Binary Authorization policies on the GKE cluster to validate container image attestations prior to deployment, and enabling Container Threat Detection in Security Command Center to continuously monitor runtime behaviors for threats such as reverse shells.
Implementing Binary Authorization enforces signature-based attestations before pods are deployed to GKE. Combining this with Container Threat Detection in Security Command Center delivers continuous runtime detection for process anomalies and reverse shell attempts inside container workloads.

Adım Adım Çözüm

1
Identify the deployment prevention control.
Binary Authorization acts as a deployment gate in GKE to block unauthorized or unverified container images based on digital signatures.
Prevents unvalidated container images from reaching production environments.
2
Identify the runtime threat monitoring control.
Container Threat Detection within Security Command Center analyzes runtime behavior at the hypervisor and container levels to detect suspicious processes.
Provides continuous runtime observability and alerting for threats like reverse shell executions.

Anahtar Kavram

Multi-layered container security using Binary Authorization for deployment gating and Security Command Center Container Threat Detection for runtime monitoring.
Tahmini Süre:1m 30s
Soru 1331Soru

An engineering team is deploying an updated version of a stateless microservice to Cloud Run. The update requires modifying a Cloud SQL PostgreSQL table schema by adding a new required column and removing an obsolete column. The team plans to perform a canary deployment using Cloud Run revision traffic splitting over 24 hours. How should the cloud architect structure the deployment strategy to maintain zero downtime and ensure immediate rollback capability throughout the release?

Cevabı ve açıklamayı göster

Cevap: Apply the schema migration using an expand-and-contract pattern by first adding the new column as optional, deploying the new Cloud Run revision to handle both old and new schema structures, and deferring the removal of the obsolete column until after traffic is 100% shifted and validated.

Cevap

Structure the database migration using an expand-and-contract strategy: add the new column as optional first, deploy the dual-compatible application revision via Cloud Run traffic splitting, and remove the deprecated column only after full rollout verification.
Executing database schema updates via an expand-and-contract approach ensures backward compatibility throughout the traffic shifting process. During a canary deployment, both old and new application revisions query the database simultaneously; keeping schema changes non-breaking allows both revisions to operate without downtime and guarantees safe rollback capability if anomalies occur.

Adım Adım Çözüm

1
Analyze the database schema dependencies between active and new revisions during canary traffic splitting.
Identified that both application revisions will run concurrently and write to the same database instance during the rollout window.
Traffic splitting routes user requests to both revisions simultaneously, requiring database schema backward compatibility.
2
Design an expand-and-contract migration strategy for Cloud SQL.
Database changes are executed in multi-phase backward-compatible steps rather than a single breaking DDL script.
Allows the legacy revision to function correctly while the canary revision validates the new application logic.
3
Execute the final cleanup contract phase after successful canary validation.
Obsolete database columns are removed only when no active traffic relies on the old schema.
Ensures zero-downtime operations and enables frictionless rollback during the canary observation window.

Anahtar Kavram

Expand-and-contract database schema migration pattern during canary deployments
Tahmini Süre:2m 0s
Soru 1332Soru

A retail company needs to deploy a simple, stateless HTTP web microservice that experiences low and unpredictable traffic patterns throughout the day. The primary business requirement is to minimize operational management overhead and infrastructure cost by ensuring resources only incur charges during active processing. Which deployment strategy should you choose?

Cevabı ve açıklamayı göster

Cevap: Deploy the microservice container to Cloud Run so compute instances automatically scale to zero during idle periods.

Cevap

Deploying the microservice container to Cloud Run allows the application to automatically scale to zero during idle periods, matching the business goal of minimizing compute costs and operational overhead.
Cloud Run provides a serverless execution environment specifically engineered for stateless HTTP containers. Because it scales down to zero active instances when no requests are being processed, it avoids idle infrastructure costs and requires zero cluster configuration or operational management.

Adım Adım Çözüm

1
Analyze the application characteristics and business goals
The application is a stateless HTTP microservice with low, unpredictable traffic requiring minimized infrastructure costs and minimal management overhead.
Understanding application state and traffic patterns dictates the optimal compute architecture.
2
Evaluate GCP compute options against scale-to-zero capabilities
Cloud Run automatically scales container instances up or down based on traffic, down to zero instances when no HTTP requests arrive.
Scale-to-zero ensures the organization only pays for the exact CPU and memory consumed while processing incoming requests.

Anahtar Kavram

Serverless compute right-sizing for cost optimization and low operational overhead
Tahmini Süre:45s
Soru 1333Soru

A retail company is migrating a legacy web application to Google Cloud. The application consists of a stateless HTTP API backend and a regional relational database that processes standard CRUD transactions. The business requirement is to minimize operational overhead, eliminate baseline infrastructure costs during idle periods, and optimize monthly expenditure while maintaining automatic scaling for peak sales events. Which architectural design best satisfies these requirements?

Cevabı ve açıklamayı göster

Cevap: Deploy the stateless HTTP API on Cloud Run and host the relational database on Cloud SQL for PostgreSQL with high availability.

Cevap

Deploying the stateless HTTP API backend on Cloud Run combined with hosting the relational database on Cloud SQL for PostgreSQL best meets the cost optimization and low operational overhead requirements.
Pairing Cloud Run for stateless HTTP services with Cloud SQL for standard regional relational databases optimizes spend by using scale-to-zero serverless compute while avoiding over-provisioned infrastructure or high-cost global database engines.

Adım Adım Çözüm

1
Analyze workload compute characteristics and cost model
The API backend is stateless HTTP with fluctuating traffic; Cloud Run scales down to zero instances, eliminating idle compute costs.
Serverless containers suit stateless web APIs with variable load without requiring node management or fixed cluster overhead.
2
Evaluate database requirements against Google Cloud managed database options
The workload requires standard regional relational transactions; Cloud SQL satisfies business requirements cost-effectively.
Cloud Spanner is designed for globally distributed relational databases requiring high horizontal scale and is cost-prohibitive for standard regional workloads.
3
Assess commitment and sizing strategies for cost optimization
Sizing fixed Compute Engine instances with Committed Use Discounts for peak demand causes wasteful spending during normal traffic periods.
Dynamic serverless autoscaling ensures expenditure scales directly with actual request volume.

Anahtar Kavram

Selecting cost-effective serverless compute and right-sized managed databases based on workload demand, scale-to-zero capabilities, and operational overhead bounds.
Soru 1334Soru

A financial services enterprise needs to archive historical transaction audit logs to Google Cloud for compliance. The logs are accessed very rarely (less than once per year) but must be retained for seven years. The primary business requirement is to minimize storage costs while automating data lifecycle governance. Which TWO actions should the team take to achieve these business and cost requirements? (Select TWO)

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

Cevabı ve açıklamayı göster

Cevap: Configure Cloud Storage Lifecycle Management rules to transition objects from Standard to Archive Storage class after 30 days of inactivity.; Use Cloud Storage Lifecycle Management to automatically delete noncurrent object versions after the mandatory seven-year retention period expires.

Cevap

Transitioning logs to Archive Storage via Object Lifecycle Management and automatically deleting expired object versions after the seven-year retention period minimize storage costs and eliminate manual management overhead.
Transitioning infrequently accessed objects to Archive Storage provides the lowest per-gigabyte storage cost, and configuring lifecycle rules to automatically remove objects past their 7-year retention period prevents paying for unnecessary storage after compliance obligations end.

Adım Adım Çözüm

1
Analyze access frequency and retention requirements
Infrequent access (<1/year) points to the Archive Storage class as the most cost-effective tier.
Selecting the lowest cost storage class matching access frequency reduces unit cost per GB.
2
Evaluate lifecycle automation options
Automating storage tier transitions and final object deletions using Object Lifecycle Management prevents manual intervention and avoids storing expired data.
Automation enforces business compliance while preventing unexpected storage cost accumulation.

Anahtar Kavram

Cloud Storage Class Tiering and Lifecycle Management for Cost Optimization
Tahmini Süre:1m 0s
Soru 1335Soru

A financial analytics firm processes daily transaction reconciliation jobs that run for only 3 hours every midnight, requiring high CPU for processing but zero compute capacity for the remaining 21 hours of the day. Additionally, their operational relational dataset is approximately 400 GB400\text{ GB} in size with standard regional availability requirements. The company wants to minimize baseline compute and database costs while ensuring automated scaling and minimal management overhead. Which TWO architectural decisions should you recommend to meet these business requirements? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Containerize the daily reconciliation workload and execute it using Cloud Run jobs triggered by Cloud Scheduler.; Provision a Cloud SQL for PostgreSQL instance with automatic storage increase enabled to store the relational dataset.

Cevap

The organization should containerize the batch workload using Cloud Run jobs triggered by Cloud Scheduler, and host the regional 400 GB400\text{ GB} relational database on Cloud SQL.
The solution minimizes operational costs by aligning compute usage strictly with execution time using serverless Cloud Run jobs (which incur zero charges when idle) and right-sizing the relational database using Cloud SQL, which meets regional 400 GB400\text{ GB} storage needs efficiently without the node overhead of Cloud Spanner.

Adım Adım Çözüm

1
Analyze compute cost requirements for short-duration batch workloads
Identified that compute runs only 3 hours per day (12.5%12.5\% duty cycle), making serverless scale-to-zero compute (Cloud Run jobs) optimal over continuous VMs or baseline Kubernetes clusters.
Running dedicated VMs or GKE nodes continuously results in paying for 21 hours of unused compute time daily.
2
Evaluate database requirements against data scale and SLA
The dataset is 400 GB400\text{ GB} within a single region, which falls within standard regional relational database boundaries.
Cloud SQL delivers required performance and high availability at significantly lower cost than multi-region Cloud Spanner.

Anahtar Kavram

Selecting serverless compute for bursty/scheduled batch jobs and cost-effective regional relational storage for moderate data volumes.
Tahmini Süre:1m 30s
Soru 1336Soru

A financial analytics enterprise processes a continuous low-volume stream of transactional data that requires a regional relational database with low administrative overhead. Additionally, the platform executes high-throughput batch analysis jobs for 48 hours once per month, requiring immense compute capacity that remains idle for the rest of the month. The enterprise wants to optimize Google Cloud infrastructure costs while maintaining high availability and scaling dynamically during peak processing. Which TWO architectural decisions should the cloud architect implement to satisfy these business requirements? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Deploy the transactional database on Cloud SQL for PostgreSQL with automatic storage increase enabled.; Execute the monthly 48-hour batch analysis jobs using Compute Engine Spot VMs in a Managed Instance Group with checkpointing.

Cevap

Deploy the transactional database on Cloud SQL for PostgreSQL with automatic storage scaling, and execute the monthly 48-hour batch analysis workloads on Compute Engine Spot VMs with checkpointing.
Selecting Cloud SQL for PostgreSQL satisfies the requirement for a low-overhead regional relational database at minimal baseline cost. Utilizing Compute Engine Spot VMs with job checkpointing for the 48-hour monthly batch workload achieves dramatic cost reductions compared to standard provisioned instances while supporting fault tolerance.

Adım Adım Çözüm

1
Analyze database requirements
Identified a low-volume regional relational database requirement with low administrative overhead.
Cloud SQL for PostgreSQL fits regional relational needs without paying the premium multi-region node costs associated with Cloud Spanner.
2
Analyze batch compute workload pattern
Identified an intermittent, fault-tolerant batch workload operating only 48 hours per month.
Spot VMs offer maximum cost savings for short-lived batch jobs. CUDs are cost-prohibitive for short intermittent spikes because CUDs commit to continuous hourly billing over 1 or 3 years.
3
Synthesize cost and architecture strategy
Combine managed Cloud SQL with Spot VM auto-scaling.
Meets all operational requirements while significantly lowering both baseline running costs and batch compute costs.

Anahtar Kavram

Selecting cost-effective compute and storage architectures matching workload intermittency and regional constraints.
Soru 1337Soru

A healthtech company is migrating an internal administrative tool to Google Cloud. The application requires a standard relational database with SQL transactions for a 50 GB dataset hosted in a single region. Primary business requirements are to minimize operational management overhead and baseline compute costs while providing high availability across zones. Which database solution best meets these requirements?

Cevabı ve açıklamayı göster

Cevap: Cloud SQL configured with high availability (HA) enabled across two zones in the target region

Cevap

Cloud SQL configured with high availability (HA) enabled across two zones in the target region is the optimal choice.
Cloud SQL offers a fully managed relational database service ideal for single-region workloads up to several terabytes. Enabling high availability (HA) provides automatic cross-zone failover while keeping operational overhead low and maintaining cost efficiency for a 50 GB database.

Adım Adım Çözüm

1
Analyze workload relational requirements and dataset scale
The application requires a standard SQL relational database for a modest 50 GB dataset in a single region.
Determining scale prevents selecting globally distributed database services designed for petabyte scale.
2
Evaluate business constraints regarding cost and operational overhead
Fully managed Cloud SQL minimizes operational burden (backups, maintenance, failover) at a low baseline cost compared to Cloud Spanner or custom GKE/Compute Engine deployments.
Choosing a fully managed regional database service matches the business goal of low cost and low management effort.

Anahtar Kavram

Selecting Cloud SQL over Cloud Spanner or self-managed database infrastructure for small-to-medium regional relational workloads minimizes cost and operational overhead.
Soru 1338Soru

A healthcare provider relies on a mission-critical patient record processing backend running on Compute Engine regional Managed Instance Groups (MIGs) behind a Global External Application Load Balancer. The engineering team is preparing to execute a blue-green deployment strategy for a major release that includes database structure updates. Which TWO technical steps must be executed to ensure zero downtime and prevent deployment failure?

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

Cevabı ve açıklamayı göster

Cevap: Implement an expand-contract database schema migration pattern to ensure the database layer maintains backwards compatibility with both blue and green application instances concurrently.; Assess regional compute quotas in the target deployment region ahead of time and request quota increases to accommodate running duplicate MIG capacity during the release window.

Cevap

The engineering team must implement an expand-contract database schema migration pattern to ensure schema compatibility across versions, and assess and request regional compute quota increases prior to deployment to support running concurrent blue and green environments.
Blue-green releases require two key safeguards when handling stateful or database-backed applications: first, database schema changes must be backward-compatible (expand-contract method) so both application revisions run cleanly against the shared database. Second, because blue and green MIGs run simultaneously at 100% capacity during validation, regional resource quotas must be checked and increased prior to initiating the deployment.

Adım Adım Çözüm

1
Analyze capacity requirements for blue-green deployment
Identify that total regional instance count and CPU demand will temporarily double during the rollout.
Blue-green deployment models require provisioning a complete green environment while keeping the active blue environment at full production capacity.
2
Verify GCP quota availability
Request regional Compute Engine quota increases in advance if current limits are lower than the combined blue + green peak footprint.
Insufficient quota causes instance creation failures when scaling up the green Managed Instance Group.
3
Design database migration using expand-contract pattern
Apply additive schema changes (expand phase) that support both old and new code structures.
Ensures that active requests hitting blue instances and newly cut-over requests hitting green instances succeed without database constraint violations.

Anahtar Kavram

Executing zero-downtime blue-green deployments requires database schema backward compatibility and pre-provisioned regional infrastructure quotas for concurrent environments.
Soru 1339Soru

A smart grid energy enterprise needs to migrate 800 TB of historical sensor log files from an on-premises network-attached storage (NAS) system to Google Cloud Storage within a strict 2-week maintenance window. The company's facility connects to the internet via a shared 100 Mbps uplink that is heavily utilized for daily business operations. To meet compliance, the business requires that the transfer completes on time, does not disrupt ongoing operational traffic, and minimizes overall cost. Which strategy should a cloud architect recommend?

Cevabı ve açıklamayı göster

Cevap: Order a Google Cloud Transfer Appliance, copy the data locally over the high-speed local network, and ship the physical appliance to Google for ingestion into Cloud Storage.

Cevap

Order a Google Cloud Transfer Appliance, copy the data locally over the high-speed local network, and ship the physical appliance to Google for ingestion into Cloud Storage.
Transferring 800 TB of data over a 100 Mbps uplink requires over 740 days. An offline transfer using Google Cloud Transfer Appliance allows copying data locally at high speed, shipping the device, and ingesting it into Cloud Storage within days, meeting the 2-week requirement at minimal cost without impacting production internet traffic.

Adım Adım Çözüm

1
Calculate required transfer throughput for 800 TB over a 2-week (14-day) window.
Network speed needed: (800 TB×8×1012 bits)/(14×86400 seconds)5.29 Gbps(800 \text{ TB} \times 8 \times 10^{12} \text{ bits}) / (14 \times 86400 \text{ seconds}) \approx 5.29 \text{ Gbps}.
Determines whether an online transfer over the existing 100 Mbps network connection is feasible.
2
Compare available WAN capacity against required throughput.
The available 100 Mbps WAN uplink is significantly lower than the required 5.29 Gbps continuous throughput.
Eliminates all online transfer strategies over the existing WAN connection.
3
Select the offline data transfer appliance solution.
Using a Google Cloud Transfer Appliance allows local high-speed ingestion (up to multi-Gbps locally) and physical shipping within the 14-day constraint at a minimal cost.
Satisfies the deadline, avoids network saturation, and optimizes migration costs.

Anahtar Kavram

Selecting physical transfer appliances versus online network transfer based on data volume, network bandwidth, and time constraints.
Soru 1340Soru

A digital media archiving enterprise needs to migrate 1.8 PB1.8\text{ PB} of historical video assets from an on-premises storage area network (SAN) to Cloud Storage Coldline for compliance retention. The company's on-premises site has a single 100 Mbps100\text{ Mbps} dedicated internet uplink, which is consistently utilized at 70%70\% capacity by core daily business operations. The project timeline strictly requires completing the full data transfer within 30 days30\text{ days} while minimizing overall transfer costs and preventing any impact on existing operational network traffic. Which data transfer strategy should the cloud architect recommend?

Cevabı ve açıklamayı göster

Cevap: Order Google Cloud Transfer Appliance devices, copy the data locally on-premises, ship the encrypted appliances to Google for ingestion into Cloud Storage, and configure Object Lifecycle Management rules.

Cevap

Order Google Cloud Transfer Appliance devices to perform an offline migration, ship them to Google for ingestion into Cloud Storage Coldline, and enforce lifecycle rules.
Transferring 1.8 PB1.8\text{ PB} over a constrained 100 Mbps100\text{ Mbps} link (with only 30 Mbps30\text{ Mbps} available capacity) would take over 15 years to complete online. Utilizing Google Cloud Transfer Appliance allows the enterprise to securely copy data locally at multi-gigabit speeds on-premises and ship the physical hardware to Google for rapid ingestion into Cloud Storage Coldline within the 30-day requirement, while avoiding long-term network infrastructure expenditure and preventing operational network degradation.

Adım Adım Çözüm

1
Calculate available online bandwidth and required transfer duration for the dataset.
Remaining network capacity is 30% of 100 Mbps=30 Mbps30\% \text{ of } 100\text{ Mbps} = 30\text{ Mbps}. Uploading 1.8 PB1.8\text{ PB} (1.44×1016 bits1.44 \times 10^{16}\text{ bits}) at 30 Mbps30\text{ Mbps} requires approximately 1.44×101630×106=4.8×108 seconds5,555 days\frac{1.44 \times 10^{16}}{30 \times 10^6} = 4.8 \times 10^8\text{ seconds} \approx 5,555\text{ days}, far exceeding the 30 day30\text{ day} limit.
Online transfer strategies over the existing link cannot meet the time constraint.
2
Evaluate offline vs online high-speed dedicated connection alternatives for cost and timing.
Provisioning a Dedicated Interconnect circuit incurs high setup fees and requires long provisioning lead times often exceeding 30 days. Transfer Appliance enables rapid local rack-and-copy deployment without long-term commitments.
Offline hardware appliance ingestion eliminates network bottlenecking and long-term financial commitments for one-time migrations.
3
Select the optimal product for cost and business requirement alignment.
Transfer Appliance handles petabyte-scale offline moves securely within days while avoiding network saturation and unnecessary long-term interconnect commitments.
Meets RTO/timeline requirements with lowest total cost of ownership.

Anahtar Kavram

Selecting Data Transfer Strategies based on Bandwidth, Dataset Size, and Cost
ÖncekiSayfa 67 / 80Sonraki
Tüm alıştırma soruları — Google Cloud Professional Cloud Architect | Examkin