Tüm alıştırma soruları

1598 soru

Soru 421Soru

A financial services institution is migrating its reporting warehouse and transactional workloads from an on-premises data center to Google Cloud. The dataset consists of 1.2 PB1.2\text{ PB} of historical raw analytics logs stored on Network-Attached Storage (NAS) and an active 4 TB4\text{ TB} operational MySQL database. The institution has a dedicated WAN bandwidth of 200 Mbps200\text{ Mbps} available for migration activities, and business requirements mandate a maximum downtime window of 4 hours during the final cutover.

Which TWO architectural decisions should the Cloud Architect incorporate into the migration plan to satisfy these requirements?

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

Cevabı ve açıklamayı göster

Cevap: Order GCP Transfer Appliance devices to perform an offline bulk data transfer of the 1.2 PB1.2\text{ PB} historical analytics logs into Cloud Storage.; Use Database Migration Service (DMS) with continuous Change Data Capture (CDC) to replicate the 4 TB4\text{ TB} operational MySQL database prior to cutover.

Cevap

The correct architecture requires utilizing GCP Transfer Appliance for the offline bulk transfer of the 1.2 PB1.2\text{ PB} historical files and Database Migration Service (DMS) with Change Data Capture (CDC) for continuous database synchronization prior to final cutover.
For the 1.2 PB1.2\text{ PB} raw analytics logs, an online transfer over 200 Mbps200\text{ Mbps} would take over 550 days. Transfer Appliance provides an offline physical hardware shipping model that ingests petabyte-scale data into Cloud Storage efficiently. For the active 4 TB4\text{ TB} MySQL database, Database Migration Service (DMS) with CDC continuously streams change logs to Cloud SQL in real time, allowing a seamless cutover within the 4-hour window.

Adım Adım Çözüm

1
Calculate network throughput feasibility for the bulk historical dataset transfer
At 200 Mbps200\text{ Mbps}, transferring 1.2 PB1.2\text{ PB} (1.2×1015 bytes1.2 \times 10^{15}\text{ bytes}) requires 1.2×1015×8200×106×86400555 days\frac{1.2 \times 10^{15} \times 8}{200 \times 10^6 \times 86400} \approx 555\text{ days}, confirming that an online transfer is impossible.
Petabyte-scale datasets on limited bandwidth connections mandate an offline physical appliance ingestion model using Transfer Appliance.
2
Evaluate operational database migration and cutover constraints
Continuous replication via Database Migration Service (DMS) with CDC performs the bulk load online and keeps the destination synchronized until cutover.
DMS minimizes cutover time down to a simple DNS/connection swap, easily satisfying the 4-hour downtime constraint.

Anahtar Kavram

Selecting appropriate GCP data migration tools based on network bandwidth calculations, dataset size, and database downtime windows.
Soru 422Soru

A cloud administrator creates a VPC Network Peering connection between VPC-A and VPC-B, and another VPC Network Peering connection between VPC-B and VPC-C. A user attempts to ping a Compute Engine virtual machine in VPC-C directly from a virtual machine in VPC-A, but the traffic is dropped. What is the fundamental VPC networking rule causing this behavior?

Cevabı ve açıklamayı göster

Cevap: VPC Network Peering is non-transitive, so traffic cannot transit through VPC-B to reach VPC-C.

Cevap

VPC Network Peering is non-transitive, so traffic cannot transit through VPC-B to reach VPC-C.
In Google Cloud, VPC Network Peering is non-transitive. Routes established between VPC-A and VPC-B are not passed along to VPC-C through VPC-B's peering connection. As a result, virtual machines in VPC-A cannot communicate directly with virtual machines in VPC-C.

Adım Adım Çözüm

1
Examine the peering layout between the three VPC networks.
VPC-A is peered with VPC-B, and VPC-B is peered with VPC-C.
Understand the direct peering connections established.
2
Evaluate Google Cloud VPC Network Peering routing behavior.
Routes learned from a peered network are not re-advertised to other peered networks.
VPC Network Peering is non-transitive by design.
3
Identify why communication between VPC-A and VPC-C fails.
Because VPC-B cannot act as a transit router for peered traffic, VPC-A has no route to reach VPC-C.
Direct communication between VPC-A and VPC-C requires either direct peering between VPC-A and VPC-C or a transit architecture using Cloud VPN or Cloud Router.

Anahtar Kavram

VPC Network Peering Transitivity
Tahmini Süre:1m 0s
Soru 423Soru

An enterprise organization operates two separate Google Cloud Virtual Private Cloud (VPC) networks: vpc-production and vpc-analytics. The vpc-production network is connected to the company's on-premises data center using an High Availability (HA) Cloud VPN gateway paired with a Cloud Router running dynamic BGP routing. The two VPCs are connected using VPC Network Peering with custom route import and export enabled. Network administrators discover that on-premises hosts can successfully reach workloads in vpc-production, but cannot communicate with resources in vpc-analytics. You must enable private on-premises connectivity to both VPC environments without introducing redundant IPSec tunnels or increasing administrative overhead. Which architectural modification should you implement?

Cevabı ve açıklamayı göster

Cevap: Migrate to a Shared VPC architecture by establishing a Host Project containing the HA Cloud VPN and Cloud Router, and attach the analytics workloads as a Service Project within subnets of the Host VPC.

Cevap

Migrate the environment to a Shared VPC architecture where a designated Host Project owns the HA Cloud VPN gateway, Cloud Router, and network subnets, while the analytics workloads reside in an attached Service Project.
Migrating to a Shared VPC architecture resolves the connectivity issue because all subnets belong to the same Host VPC network. The HA Cloud VPN gateway and Cloud Router in the Host VPC can directly route traffic to subnets allocated for service projects (such as analytics), bypassing the non-transitive limitations of VPC Network Peering.

Adım Adım Çözüm

1
Analyze why on-premises traffic cannot reach the peered analytics VPC.
Identify that Google Cloud VPC Network Peering is non-transitive, meaning packets arriving from an on-premises hybrid connection (VPN or Interconnect) into one VPC cannot be forwarded across a peering connection to a second VPC.
VPC Network Peering explicitly restricts third-party transitivity for hybrid connectivity resources.
2
Evaluate solutions that consolidate subnets under a single network boundary without multiplying VPN tunnels.
Determine that a Shared VPC topology allows the organization to centralize network infrastructure (HA Cloud VPN, Cloud Router, subnets) in a Host Project.
Shared VPC eliminates the need for peering between internal projects because all service projects share subnets defined in the single Host VPC.
3
Verify traffic routing for service project resources in a Shared VPC.
On-premises routers establish BGP sessions with the Host VPC's Cloud Router, routing traffic directly into subnets used by service project workloads without encountering transitivity barriers.
All traffic flows natively within the same VPC network control plane.

Anahtar Kavram

VPC Network Peering Non-Transitivity & Shared VPC Hybrid Routing
Soru 424Soru

A DevOps team needs to provision a new Google Kubernetes Engine (GKE) cluster for an enterprise application while adhering to basic security and administrative access best practices. Which of the following configurations should the team implement when creating the cluster? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Enable Control Plane Authorized Networks to restrict administrative endpoint access to authorized IP ranges.; Create a dedicated custom IAM service account with minimal required roles to serve as the node pool identity.

Cevap

The team should enable Control Plane Authorized Networks to restrict API server access to specific IP addresses and create a custom IAM service account with minimal permissions for the GKE nodes.
Enabling Control Plane Authorized Networks restricts API master endpoint access to verified IP blocks, and using a dedicated minimal custom service account for GKE node pools upholds security best practices.

Adım Adım Çözüm

1
Configure control plane network security
Authorized IP ranges are enforced for cluster master access.
Restricting control plane access prevents unauthorized external access to Kubernetes administration APIs.
2
Configure node identity
Nodes run under a specific custom service account with minimal IAM roles.
Following least privilege prevents workloads running on nodes from abusing broad compute default permissions.

Anahtar Kavram

Provisioning secure GKE clusters with control plane authorized networks and least-privilege node service accounts.
Soru 425Soru

A DevOps team is setting up an automated Infrastructure as Code (IaC) pipeline using Terraform to provision Compute Engine resources and service accounts for a new analytics platform. The team must ensure secure state management and adhere to the principle of least privilege for the deployment pipeline's service account. Which two actions should the team take to meet these security and operational requirements?

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

Cevabı ve açıklamayı göster

Cevap: Configure a Cloud Storage backend with object versioning enabled to store the Terraform state file securely.; Grant the deployment pipeline service account the Service Account User role (roles/iam.serviceAccountUser) on the target workload service account.

Cevap

The correct architectural decisions are configuring a Cloud Storage backend with object versioning for storing the Terraform state file, and granting the deployment pipeline service account the Service Account User role (roles/iam.serviceAccountUser) on the target workload service account.
To safely provision compute resources in an automated pipeline, remote state management using Cloud Storage with versioning prevents state loss and race conditions. Furthermore, following least privilege requires assigning `roles/iam.serviceAccountUser` to the deployment service account so it can attach the target identity to virtual machines without granting administrative power over the service account lifecycle or broad project resources.

Adım Adım Çözüm

1
Evaluate state storage strategy for Infrastructure as Code (IaC).
Using a Cloud Storage bucket backend with object versioning ensures state durability, concurrency locking, and auditability across team and CI/CD runs.
Local unversioned storage on CI/CD nodes leads to state corruption, drift, and lost state files.
2
Evaluate IAM permissions for the deployment pipeline service account to attach workload service accounts to Compute Engine instances.
Granting `roles/iam.serviceAccountUser` allows impersonation/attachment without administrative modification rights.
Assigning primitive roles like Editor or administrative roles like Service Account Admin violates least privilege and exposes security vulnerabilities.

Anahtar Kavram

Provisioning Compute Infrastructure using IaC Best Practices and IAM Least Privilege
Soru 426Soru

A global media enterprise is redesigning its video processing pipeline on Google Cloud. The architecture requires deploying two distinct workloads:

1. A legacy video transcoding service that depends on custom OS kernel parameter tuning (`sysctl` network buffer settings) and requires POSIX-compliant high-performance local disk access.
2. A lightweight REST API service that receives unpredictable, bursty HTTP traffic, requires automatic scaling to zero instances to minimize costs during idle hours, and must require minimal operational management overhead.

Which TWO compute platform architectural decisions should the Cloud Architect recommend to satisfy these requirements? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Provision Compute Engine virtual machines using Managed Instance Groups for the legacy video transcoding service.; Deploy the REST API service on Cloud Run.

Cevap

The optimal architecture combines Compute Engine virtual machines (in Managed Instance Groups) for the OS-dependent transcoding workload and Cloud Run for the stateless, bursty REST API service.
The solution requires matching specific compute characteristics to workload demands. Provisioning Compute Engine virtual machines is necessary for the transcoding engine because it grants root access to modify Linux kernel `sysctl` network buffer parameters and attach high-throughput local storage. Deploying the REST API on Cloud Run is optimal because it natively handles HTTP request traffic, automatically scales to zero during inactivity, and eliminates server management overhead.

Adım Adım Çözüm

1
Analyze the technical requirements of the first workload (legacy transcoding engine).
Identified rigid OS dependencies: need for custom kernel `sysctl` tuning and local POSIX storage performance.
Serverless and managed application platforms (Cloud Run, Cloud Functions) restrict OS-level kernel tuning and raw block/local POSIX storage configurations, necessitating Infrastructure as a Service (Compute Engine).
2
Analyze the technical requirements of the second workload (REST API gateway).
Identified serverless fit: stateless HTTP handling, unpredictable spikes, scale-to-zero requirement, and zero operational overhead goal.
Cloud Run natively satisfies HTTP request handling with automatic scaling down to zero instances and zero cluster lifecycle management.
3
Evaluate and eliminate candidate compute misallocations.
Rejected GKE for the lightweight API due to management overhead, and rejected serverless options for the transcoding engine due to OS constraints.
Architectural selection must balance feature support, operational simplicity, and cost efficiency based on Google Cloud best practices.

Anahtar Kavram

Selecting and Designing Compute and Application Platforms
Soru 427Soru

A logistics enterprise is deploying an automated CI/CD pipeline using Infrastructure as Code to provision Compute Engine virtual machines and Google Kubernetes Engine (GKE) node pools across multiple projects. The deployment pipeline runs under a dedicated service account and must support rapid scaling without encountering deployment failures, while strictly adhering to the principle of least privilege. Which TWO configuration steps should the cloud architect recommend to meet these requirements?

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

Cevabı ve açıklamayı göster

Cevap: Submit regional vCPU and compute resource quota increase requests in advance of major infrastructure deployment events.; Grant the Service Account User role to the CI/CD deployment service account on the specific service accounts attached to compute instances.

Cevap

The cloud architect should recommend submitting regional compute quota increase requests in advance and granting the Service Account User role on workload service accounts to the deployment service account.
Proactively requesting quota increases ensures that automated pipelines do not fail due to regional vCPU bottlenecks when provisioning GKE nodes or Compute Engine instances. Granting the Service Account User role allows the deployment pipeline to assign identity service accounts to virtual machines and node pools while following least privilege guidelines.

Adım Adım Çözüm

1
Evaluate infrastructure scaling prerequisites for automated provisioning pipelines.
Identified that compute resource provisioning can fail if regional vCPU limits are reached, requiring proactive quota requests.
Default quotas in new regions or projects often do not accommodate multi-node GKE clusters or large MIG deployments.
2
Evaluate IAM privilege requirements for service account impersonation during compute creation.
Determined that `roles/iam.serviceAccountUser` is necessary to allow the runner to attach service accounts to VMs.
Least privilege mandates binding the user role on specific target service accounts rather than granting broad primitive roles.

Anahtar Kavram

Provisioning Compute Resources and Identity Scoping
Tahmini Süre:2m 0s
Soru 428Soru

A DevOps team is establishing an automated continuous delivery pipeline for a mission-critical web application on Google Kubernetes Engine (GKE) using Cloud Build, Artifact Registry, Binary Authorization, and Google Cloud Deploy. The deployment requirements mandate zero downtime, automated container security gates, and progressive canary traffic shifting with automated rollback capabilities. In what chronological sequence should the pipeline stages be executed to implement this secure release process?

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

Cevabı ve açıklamayı göster

Cevap

The correct execution sequence for the deployment pipeline is: 1) Build container image and generate Binary Authorization attestation signature in Cloud Build, 2) Create Cloud Deploy release and validate attestation via GKE Binary Authorization admission control, 3) Route 10% traffic to canary target with Cloud Monitoring metric validation, and 4) Advance rollout to route 100% of traffic to the production targets.
The correct release sequence begins with artifact compilation, vulnerability scanning, and Binary Authorization attestation signing during the build stage. Next, Cloud Deploy creates the release, triggering GKE Binary Authorization admission control to verify image signatures before scheduling pods. Once admitted, Cloud Deploy initiates canary deployment by shifting 10% of traffic while monitoring SLO metrics. Finally, upon metric validation, the rollout is advanced to shift 100% of production traffic.

Adım Adım Çözüm

1
Build and Security Attestation
Container image created, scanned, and signed by a trusted attestor key.
Binary Authorization policy enforcement requires vulnerability scanning and valid cryptographically signed attestations before container deployment.
2
Release Delivery & Admission Control
Cloud Deploy release created and admitted into the GKE cluster.
Binary Authorization operates as a Kubernetes admission controller, evaluating container signatures prior to pod scheduling.
3
Canary Deployment & SLO Verification
Partial traffic (10%) directed to canary instances with active health verification.
Progressive delivery minimizes blast radius by testing real user traffic against canary instances before full release.
4
Full Production Promotion
Rollout advanced to 100% production traffic.
Once automated metrics confirm zero SLO regressions, the release is safely promoted across all production endpoints.

Anahtar Kavram

Automated Continuous Delivery Pipeline Sequencing with Security Attestation and Canary Delivery
Tahmini Süre:2m 0s
Soru 429Soru

A global fintech firm is designing the compute architecture on Google Cloud for a payment processing system consisting of two distinct workloads. Workload 1 is a stateless microservice that receives gRPC requests from external gateways, experiences unpredictable bursty traffic with periods of complete idle time, and requires automatic scale-to-zero capability with minimal operational overhead. Workload 2 is a stateful stream-enrichment engine that requires ultra-low latency access to local NVMe storage and custom Linux kernel tuning (`sysctl` network parameter modifications) at the operating system level. Which TWO compute platform strategies should you select to meet these technical requirements while adhering to Google Cloud best practices?

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

Cevabı ve açıklamayı göster

Cevap: Deploy Workload 1 on Cloud Run configured with end-to-end HTTP/2 (gRPC) support.; Deploy Workload 2 on Compute Engine instances managed by a Managed Instance Group (MIG) with attached Local SSDs.

Cevap

Select Cloud Run with gRPC support for Workload 1, and Compute Engine Managed Instance Groups with Local SSDs for Workload 2.
Cloud Run provides serverless scale-to-zero capabilities with native gRPC/HTTP2 support for stateless microservices, satisfying Workload 1. Compute Engine virtual machines managed via MIGs provide full administrative control to configure host OS kernel sysctl parameters and attach Local SSD NVMe disks, satisfying Workload 2.

Adım Adım Çözüm

1
Analyze Workload 1 requirements
Workload 1 is stateless, containerized, uses gRPC, has unpredictable bursty traffic, and requires scale-to-zero with minimum management overhead.
Cloud Run natively supports containerized gRPC applications, scales down to zero instances when idle to minimize costs, and removes infrastructure management responsibility.
2
Analyze Workload 2 requirements
Workload 2 requires custom kernel tuning (`sysctl` network modifications) and ultra-low latency local NVMe storage.
Serverless containers (Cloud Run / App Engine) do not permit host kernel modifications. Compute Engine virtual machines provide root-level access for OS customization and direct attachment of Local SSD (NVMe) drives.
3
Combine compute platforms according to workload characteristics
Pairing Cloud Run for the stateless microservice with Compute Engine MIGs for the OS-customized stateful workload delivers optimal performance and cost efficiency.
Matching each service to its specific operational constraint avoids both compute over-provisioning and platform capability limitations.

Anahtar Kavram

Compute Platform Selection Strategy based on Statefulness, Control, and Scaling Constraints
Soru 430Soru

An energy Grid IoT analytics company is modernizing its telemetry processing platform on Google Cloud. The system must support two distinct workloads with separate operational characteristics:

1. Event Ingestion Microservice: An HTTP REST service that receives telemetry webhooks from smart meters. Traffic fluctuates unpredictable throughout the day and drops to zero overnight in specific regions. The service must scale rapidly, minimize management overhead, and scale down to zero when idle.
2. Batch Spatial Simulation Engine: An intensive data pipeline requiring custom Linux kernel parameters (`sysctl` network tuning) and direct `/dev/shm` shared memory allocations. The workload processes batched data chunks periodically, tolerates unexpected instance terminations, and must run at the lowest possible infrastructure cost.

Which TWO compute architecture decisions should the Cloud Architect recommend to satisfy these requirements? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Deploy the Event Ingestion Microservice on Cloud Run.; Deploy the Batch Spatial Simulation Engine on Compute Engine Managed Instance Groups (MIGs) utilizing Spot VMs.

Cevap

The optimal solution uses Cloud Run for the Event Ingestion Microservice and Compute Engine Managed Instance Groups with Spot VMs for the Batch Spatial Simulation Engine.
Cloud Run provides serverless HTTP execution that scales to zero for fluctuating REST webhook workloads without infrastructure management. Compute Engine Managed Instance Groups running Spot VMs provide the required OS-level access for custom kernel sysctl parameters and shared memory while maximizing cost efficiency for fault-tolerant batch jobs.

Adım Adım Çözüm

1
Analyze the Event Ingestion Microservice requirements
Identified stateless HTTP REST protocol, rapid auto-scaling demands, requirement to scale down to zero idle instances, and desire for low management overhead.
Cloud Run is purpose-built for stateless HTTP container workloads, managing server provisioning and scaling to zero automatically.
2
Analyze the Batch Spatial Simulation Engine requirements
Identified low-level OS configuration needs (sysctl, shared memory), fault-tolerant processing, and cost minimization goals.
Compute Engine VMs permit custom Linux kernel modifications and shared memory configuration. Spot VMs offer up to 60-91% savings for fault-tolerant workloads.
3
Evaluate alternative options for misallocations
GKE adds unnecessary control plane management overhead for simple microservices, Cloud Functions lacks host kernel parameter access, and CUDs misalign with variable/preemptible workload profiles.
Architecting GCP compute solutions requires matching technical constraints and cost profiles to the correct execution platform.

Anahtar Kavram

Selecting GCP Compute Platforms based on operational overhead, scaling behavior, host OS customization needs, and cost optimization.
Soru 431Soru

An Site Reliability Engineering (SRE) team is designing a centralized operational observability and compliance log routing framework across an entire Google Cloud Organization. They need to aggregate all admin activity audit logs from all project workloads into a dedicated Security Operations project's BigQuery dataset for long-term retention. Additionally, they must monitor application severity levels and receive real-time notifications whenever high-priority application errors spike across services. Which TWO actions should the team perform to meet these requirements following Google-recommended best practices and least-privilege security principles? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Create an organization-level aggregated log sink with an inclusion filter matching audit logs targeting the BigQuery dataset, and grant the sink's service account identity the BigQuery Data Editor (roles/bigquery.dataEditor) role on the target dataset.; Create a custom log-based metric matching log entries with severity level ERROR or higher, and configure a Cloud Monitoring alerting policy based on the rate of change of this log-based metric.

Cevap

The correct architecture requires creating an organization-level aggregated log sink targeted to the BigQuery dataset with the BigQuery Data Editor role assigned to the sink writer identity, along with creating a custom log-based metric for ERROR severity logs to trigger a Cloud Monitoring alerting policy.
To centralize log retention securely across an entire enterprise, Google Cloud recommends using an organization aggregated log sink targeting a central sink destination (BigQuery dataset) with least-privilege dataset roles (`roles/bigquery.dataEditor`) granted specifically to the sink's generated writer identity. To detect application error spikes in real-time, creating a log-based metric filtered by `ERROR` severity coupled with a Cloud Monitoring alerting policy allows SRE teams to be notified dynamically on metric threshold breaches.

Adım Adım Çözüm

1
Configure Centralized Audit Log Routing
An organization-level aggregated sink captures audit logs across all projects and sends them to the destination BigQuery dataset in the Security Operations project.
Aggregated sinks provide centralized governance without requiring per-project log sink maintenance.
2
Apply Least-Privilege IAM Roles to the Log Sink Identity
The sink's unique writer service account is assigned `roles/bigquery.dataEditor` on the specific destination dataset.
This guarantees the log sink can ingest data into BigQuery without granting broad project-level primitive roles.
3
Define Log-Based Metric and Alerting Policy
A log-based metric tallies log entries with severity `ERROR` or higher, and a Cloud Monitoring alerting policy triggers when the metric exceeds defined threshold rates.
Log-based metrics bridge Cloud Logging data into Cloud Monitoring for operational alerting.

Anahtar Kavram

Organization Log Aggregation, Least-Privilege Sink Service Accounts, and Log-Based Metric Alerting
Tahmini Süre:2m 30s
Soru 432Soru

An organization needs to establish an encrypted connection over the public internet between their on-premises network and a Google Cloud Virtual Private Cloud (VPC) for a low-bandwidth workload requiring 500 Mbps throughput. Which Google Cloud hybrid connectivity service should they implement?

Cevabı ve açıklamayı göster

Cevap: HA Cloud VPN

Cevap

HA Cloud VPN is the appropriate solution because it provides secure, IPsec-encrypted connectivity over the public internet suitable for workloads under 3 Gbps per tunnel.
HA Cloud VPN is specifically designed to extend an on-premises network to Google Cloud over an IPsec connection via the public internet. Since the bandwidth requirement is 500 Mbps, it comfortably fits within the 3 Gbps per tunnel capacity limit of Cloud VPN.

Adım Adım Çözüm

1
Analyze connectivity requirements
Transport must be IPsec encrypted over the public internet, supporting 500 Mbps bandwidth.
Understanding transport media and bandwidth limits dictates the appropriate hybrid networking product.
2
Evaluate Google Cloud hybrid connectivity options
HA Cloud VPN operates over the public internet using IPsec and handles up to 3 Gbps per tunnel, matching the 500 Mbps requirement.
Dedicated Interconnect is meant for high-bandwidth private connections, whereas Cloud VPN is designed for lower-bandwidth internet transport.

Anahtar Kavram

Cloud VPN vs Cloud Interconnect selection based on bandwidth and connection type requirements
Soru 433Soru

An enterprise organization is designing a multi-tier e-commerce system on Google Cloud and translating conceptual business requirements into logical and physical architecture components.

The conceptual architecture specifies four primary requirements:
1. A stateless HTTP API ingress layer to accept lightweight order payloads with minimal operational management overhead.
2. A relational data tier storing order transactions restricted strictly to a single GCP region with cost-effective, standard relational database capacity.
3. A hybrid network topology capable of delivering 10 Gbps predictable, low-latency bandwidth between on-premises systems and GCP VPCs.
4. A data security boundary that prevents authorized internal users from exfiltrating sensitive storage data to external, unauthorized Google Cloud projects.

Which TWO physical architecture decisions correctly implement these requirements while avoiding architectural anti-patterns? (Select TWO)

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

Cevabı ve açıklamayı göster

Cevap: Deploy Cloud Run for the stateless HTTP API ingress tier, and implement Cloud SQL for the regional transactional relational database tier.; Establish a Dedicated Interconnect connection for hybrid connectivity, and configure VPC Service Controls perimeters around Google Cloud Storage resources.

Cevap

The correct physical architecture choices are deploying Cloud Run for stateless HTTP APIs paired with Cloud SQL for regional relational data, and establishing Dedicated Interconnect for 10 Gbps connectivity alongside VPC Service Controls for exfiltration prevention.
Translating conceptual requirements to physical GCP components requires choosing the optimal service for operational efficiency, network throughput, and security. Cloud Run efficiently handles stateless HTTP APIs without cluster maintenance, while Cloud SQL provides cost-effective regional relational data storage. Dedicated Interconnect provides the physical 10 Gbps bandwidth needed for high-throughput hybrid networking, and VPC Service Controls defines security boundaries that prevent data exfiltration even if IAM privileges are compromised.

Adım Adım Çözüm

1
Analyze Compute Ingress and Relational Storage Requirements
Cloud Run satisfies stateless HTTP ingestion with zero server management. Cloud SQL satisfies single-region relational ACID requirements without unnecessary global Spanner overhead.
Matching conceptual tier requirements to the correct physical GCP product prevents over-provisioning and excessive operational costs.
2
Evaluate Network and Security Requirements
Dedicated Interconnect delivers physical 10 Gbps pipeline capacity (beyond HA VPN tunnel limits), while VPC Service Controls establishes network perimeters around Cloud Storage to block data exfiltration.
HA VPN cannot support 10 Gbps per tunnel, and IAM permissions alone cannot prevent data exfiltration to external GCP resources.

Anahtar Kavram

Translating Logical to Physical Architectures in GCP
Soru 434Soru

A healthcare enterprise is provisioning a private Google Kubernetes Engine (GKE) cluster in GCP to execute clinical processing workloads. The architecture must enforce strict security controls: administrative API access to the GKE control plane must be restricted exclusively to the corporate management subnet (192.168.10.0/24192.168.10.0/24) routed over Dedicated Interconnect, and pods must authenticate to Google Cloud SQL instances without using static service account keys or relying on node-level identities. Which TWO configuration actions should the Cloud Architect execute to satisfy these security requirements?

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

Cevabı ve açıklamayı göster

Cevap: Enable Control Plane Authorized Networks on the GKE cluster and specify 192.168.10.0/24192.168.10.0/24 as an authorized IP range.; Enable Workload Identity on the GKE cluster and bind the Kubernetes service account to a Google Cloud service account with minimal IAM roles.

Cevap

The Cloud Architect must enable Control Plane Authorized Networks specifying the corporate subnet 192.168.10.0/24192.168.10.0/24, and enable Workload Identity to map Kubernetes service accounts to GCP service accounts for keyless Cloud SQL authentication.
Enabling Control Plane Authorized Networks restricts administrative endpoint access strictly to specified IP ranges like the corporate management subnet (192.168.10.0/24192.168.10.0/24). Enabling Workload Identity provides secure pod-level authentication to Google Cloud SQL using IAM service accounts without downloading or managing static security keys.

Adım Adım Çözüm

1
Configure GKE control plane access security controls.
Enable Control Plane Authorized Networks on the GKE cluster and add CIDR block 192.168.10.0/24192.168.10.0/24.
This blocks unauthorized endpoints from reaching the Kubernetes master API server, restricting access solely to the dedicated corporate management subnet.
2
Configure pod-level identity and IAM access.
Enable Workload Identity on the GKE cluster, create a dedicated GCP Service Account with Cloud SQL Client permissions, and bind it to the Kubernetes Service Account.
This allows containerized applications to authenticate to GCP APIs seamlessly without embedding or managing long-lived JSON service account keys.

Anahtar Kavram

Private GKE Cluster Hardening and Workload Identity Federation
Tahmini Süre:2m 30s
Soru 435Soru

An enterprise engineering team is deploying a secure subnetwork for internal Compute Engine virtual machines that are configured without external IP addresses. The applications running on these instances require access to Google Cloud APIs (such as Cloud Storage) and also require outbound access to external third-party repositories for software updates without allowing inbound connections from the internet. Which TWO network topology configurations must be implemented in the Virtual Private Cloud (VPC) network to satisfy these connectivity requirements?

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

Cevabı ve açıklamayı göster

Cevap: Enable Private Google Access on the subnetwork where the virtual machines are deployed.; Configure Cloud NAT associated with a Cloud Router on the VPC network for outbound internet connectivity.

Cevap

The required configurations are enabling Private Google Access on the subnetwork and configuring Cloud NAT with a Cloud Router on the VPC network.
Enabling Private Google Access on the subnet provides private connectivity to Google Cloud APIs for instances without public IPs. Configuring Cloud NAT with Cloud Router allows these instances to establish outbound-only connections to third-party repositories on the internet for updates without exposing them to inbound internet traffic.

Adım Adım Çözüm

1
Identify the mechanism for internal instances to access Google Cloud services.
Enabling Private Google Access at the subnet level allows instances lacking external IP addresses to reach default Google API endpoints.
Internal VMs need a secure, managed route to access Google Cloud services like Cloud Storage without requiring public IP assignments.
2
Identify the mechanism for internal instances to send outbound traffic to external third-party endpoints.
Deploying Cloud NAT mapped to a Cloud Router provides network address translation for outbound internet connections.
Cloud NAT allows internal instances to initiate outbound connections for software updates while restricting inbound connections from external sources.

Anahtar Kavram

Configuring Private Google Access and Cloud NAT for internal VPC network topologies
Tahmini Süre:1m 0s
Soru 436Soru

A DevOps engineering team is setting up an Infrastructure as Code workflow using Terraform to provision Google Cloud storage buckets and database instances. They need to configure a remote backend that supports automatic state locking and prevents state corruption during concurrent deployments by multiple engineers. Which storage configuration should they implement?

Cevabı ve açıklamayı göster

Cevap: Configure a Google Cloud Storage (GCS) backend with Object Versioning enabled for storing the state file.

Cevap

Configure a Google Cloud Storage (GCS) backend with Object Versioning enabled for storing the state file.
Configuring a Google Cloud Storage (GCS) backend with Object Versioning enabled is the standard best practice for managing Terraform state in GCP environments. GCS natively supports state locking via Cloud Storage API lock mechanisms, preventing concurrent modifications and protecting state integrity.

Adım Adım Çözüm

1
Identify the state locking and concurrency requirement for Terraform provisioning on GCP.
Recognize that team collaboration requires a remote backend with automatic locking mechanisms.
Local state files do not lock state when multiple operators attempt concurrent provisioning.
2
Select the native Google Cloud storage service designed for Terraform state management.
Choose Google Cloud Storage (GCS) bucket configured as the backend.
GCS integrates directly with Terraform to provide automatic object locking and durability.
3
Apply object versioning on the GCS bucket.
Ensure past versions of state files can be restored if a state corruption event occurs.
Object Versioning adds an extra layer of recovery for critical infrastructure state files.

Anahtar Kavram

Terraform Remote Backend Provisioning on Google Cloud Storage
Soru 437Soru

A principal cloud architect is designing an enterprise infrastructure automation strategy using HashiCorp Terraform for a logistics enterprise on Google Cloud. Multiple automated runner instances executing within Cloud Build must perform `terraform apply` operations concurrently across distinct operational pipelines targeting shared staging environments. The architectural mandate requires protecting infrastructure state against concurrency race conditions, enabling immediate state recovery from accidental corruptions, and adhering to strict least-privilege security without storing long-lived service account keys in repositories. Which implementation strategy meets all of these requirements?

Cevabı ve açıklamayı göster

Cevap: Configure a Google Cloud Storage remote backend with Object Versioning enabled, rely on native GCS object locking for state concurrency control, and configure Cloud Build worker service accounts to impersonate dedicated deployment service accounts via short-lived IAM tokens.

Cevap

The correct architecture uses a Google Cloud Storage backend with Object Versioning enabled for automatic state history, relies on native GCS state locking for concurrency safety, and uses short-lived Service Account Impersonation for least-privilege pipeline authentication.
The solution combining a Google Cloud Storage remote backend with Object Versioning enabled, native state locking, and service account impersonation meets all architectural requirements. GCS prevents simultaneous state modifications through atomic object locks, object versioning maintains a historical ledger of state generations for rapid rollback, and service account impersonation provides secure, short-lived credential access without storing static keys.

Adım Adım Çözüm

1
Evaluate state storage security and concurrency controls
Google Cloud Storage natively supports state locking using strong consistency and object generation checks. Enabling Object Versioning ensures previous state generations remain recoverable in case of corruption or bad applies.
Remote state management in collaborative enterprise environments requires lock acquisition during writes and versioning for disaster recovery.
2
Determine identity and authentication requirements for CI/CD runners
Cloud Build runners should authenticate to target project resources by impersonating designated deployment service accounts using short-lived IAM tokens rather than static JSON service account keys.
Service account impersonation adheres to security best practices by eliminating static credentials in code repositories and limiting access scopes via fine-grained IAM roles.

Anahtar Kavram

Enterprise Infrastructure as Code state management, concurrency control, and least-privilege pipeline authentication on Google Cloud
Tahmini Süre:2m 30s
Soru 438Soru

An enterprise retail corporation is modernizing its global order processing ecosystem on Google Cloud. The architecture consists of two core workloads with distinct operational parameters:

1. A stateless HTTP REST microservice that processes user checkout requests. Traffic is extremely bursty, experiencing 50x spikes during seasonal promotions and dropping to zero overnight. The organization mandates minimal operational overhead and zero infrastructure maintenance.
2. A legacy stateful inventory synchronization service that requires custom Linux kernel socket parameter tuning (`sysctl`), direct access to attached persistent disk volumes for local file locking, and fixed internal IP addresses.

Which compute platform architecture should you recommend to meet the requirements of both workloads while minimizing operational complexity?

Cevabı ve açıklamayı göster

Cevap: Deploy the stateless HTTP REST microservice on Cloud Run, and deploy the legacy stateful inventory synchronization service on Compute Engine using stateful Managed Instance Groups (MIGs).

Cevap

Deploy the stateless HTTP REST microservice on Cloud Run, and deploy the legacy stateful inventory synchronization service on Compute Engine using stateful Managed Instance Groups (MIGs).
Deploying the stateless HTTP REST microservice on Cloud Run fulfills the requirement for zero server management overhead while scaling automatically from zero to handle 50x traffic spikes. Deploying the legacy inventory synchronization service on Compute Engine using stateful Managed Instance Groups satisfies all technical constraints of the legacy app, including custom kernel network tuning (`sysctl`), direct POSIX file locking on attached persistent disks, and fixed internal IP address preservation across VM restarts.

Adım Adım Çözüm

1
Analyze the requirements for Workload 1 (Stateless REST API)
Identified requirements: HTTP protocol, bursty traffic with scale-to-zero capability, and minimal operational overhead. Cloud Run is the optimal Google Cloud serverless container platform for stateless HTTP services.
Cloud Run automatically scales instances up and down based on traffic (including scale-to-zero) without requiring VM or cluster lifecycle management.
2
Analyze the requirements for Workload 2 (Legacy Stateful Inventory Daemon)
Identified constraints: Custom kernel tuning (`sysctl`), POSIX persistent disk file locking, and fixed IP addresses. Compute Engine provides full OS and kernel level control.
Fully managed serverless platforms (Cloud Run, Cloud Functions) isolate container environments and do not permit low-level OS/kernel parameter modifications or stateful static IP persistence.
3
Select the optimal compute combination
Combine Cloud Run for the stateless web component and Compute Engine stateful MIGs for the legacy stateful daemon.
This workload segregation ensures each component runs on the compute abstraction best suited to its operational constraints while keeping total operational overhead as low as possible.

Anahtar Kavram

Selecting GCP compute platforms based on workload statefulness, operational overhead limitations, and kernel/OS modification constraints
Soru 439Soru

An enterprise financial service relies on automated scripts to provision a temporary managed instance group (MIG) of Compute Engine virtual machines every midnight to process end-of-day ledger reconciliations. During scale testing for an upcoming release requiring 500500 N2 vCPUs in the `us-central1` region, the deployment script fails to scale up beyond 100100 vCPUs, despite using valid credentials and validated Infrastructure as Code templates. Which action should the Cloud Architect take to resolve this provisioning failure?

Cevabı ve açıklamayı göster

Cevap: Request a regional N2 vCPU quota increase for `us-central1` through Cloud Quotas before running the large-scale batch workload.

Cevap

Request a regional N2 vCPU quota increase for `us-central1` through Cloud Quotas before running the large-scale batch workload.
The correct answer correctly identifies that Google Cloud projects have default regional quotas for machine families (such as N2 vCPUs). When automated provisioning fails at a specific numeric ceiling despite correct IAM permissions and IaC code, the limiting factor is regional quota. Proactively requesting a quota increase for the target region resolves the provisioning ceiling.

Adım Adım Çözüm

1
Identify the root cause of the provisioning cap at 100 vCPUs.
Recognize that default regional Compute Engine quota limits for specific machine families (such as N2 vCPUs in `us-central1`) restrict resource allocation regardless of IAM permissions.
Google Cloud enforces default resource quotas on projects to prevent unexpected spend and ensure fair resource distribution across regions.
2
Evaluate potential solutions to allow scaling to 500 vCPUs.
Determine that submitting a quota increase request for regional N2 vCPUs in `us-central1` directly addresses the provisioning constraint.
Quota adjustments must be requested and approved ahead of large-scale provisioning events.

Anahtar Kavram

Compute Engine Regional Resource Quotas
Soru 440Soru

A financial enterprise is re-architecting its nightly batch risk calculation system on Google Cloud. The system executes containerized, stateless tasks triggered on a fixed schedule. Each batch task requires up to 45 minutes of processing time, requires custom CPU and memory allocations, and must scale to zero when no jobs are running to avoid idle infrastructure costs. Which TWO architectural decisions should the team make to meet these requirements with minimal operational overhead?

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

Cevabı ve açıklamayı göster

Cevap: Execute the batch workloads using Cloud Run jobs, configuring the execution timeout to accommodate the 45-minute task duration.; Configure Cloud Scheduler to trigger the Cloud Run job executions directly using service account authentication.

Cevap

The team should execute the batch workloads using Cloud Run jobs with appropriate execution timeouts and trigger them via Cloud Scheduler with service account authentication.
Cloud Run jobs are purpose-built for containerized tasks that run to completion without serving incoming web requests. They support execution times up to 24 hours and charge only for resources consumed during execution, automatically scaling down to zero when idle. Paired with Cloud Scheduler, the entire solution operates seamlessly without requiring persistent server infrastructure, minimizing both operational overhead and costs.

Adım Adım Çözüm

1
Analyze the workload characteristics and operational constraints.
Workload is stateless, containerized, scheduled, requires up to 45 minutes of run time, and needs to scale to zero to minimize idle costs.
Matching workload execution patterns to the appropriate GCP compute platform ensures cost efficiency and low management overhead.
2
Evaluate compute platforms against task execution duration and cost requirements.
Cloud Run jobs support tasks running up to 24 hours and scale to zero completely when idle, avoiding GKE cluster overhead or always-on VM costs.
Cloud Run services cap HTTP request timeouts at 60 minutes, but Cloud Run jobs are designed specifically for long-running batch tasks.
3
Select the serverless orchestration mechanism for triggering scheduled executions.
Cloud Scheduler provides a fully managed serverless cron service that securely triggers Cloud Run jobs via IAM authentication.
Combining serverless scheduling with serverless execution provides an end-to-end architecture with zero persistent infrastructure management.

Anahtar Kavram

Selecting serverless compute platforms for scheduled long-running batch workloads
ÖncekiSayfa 22 / 80Sonraki
Tüm alıştırma soruları — Google Cloud Professional Cloud Architect | Examkin