Tüm alıştırma soruları

1598 soru

Soru 481Soru

An energy utility company is migrating its smart grid analytics and operations workload to Google Cloud. The current environment consists of 3.5 PB3.5\text{ PB} of historical smart meter reading archives stored on an on-premises Storage Area Network (SAN) and an active 8 TB8\text{ TB} operational MySQL database used for billing. The enterprise has a 1 Gbps1\text{ Gbps} Dedicated Interconnect link with a policy capping cloud migration bandwidth to 300 Mbps300\text{ Mbps}. The target architecture requires minimal downtime for the operational database during cutover (under 1 hour1\text{ hour}) and complete data integrity across all systems. In what sequence should the Cloud Architect execute these steps to perform the migration?

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

Cevabı ve açıklamayı göster

Cevap

The correct migration sequence is: 1) Order and seed bulk historical archives (3.5 PB3.5\text{ PB}) offline using Transfer Appliance; 2) Configure Database Migration Service (DMS) with CDC to continuously replicate the active 8 TB8\text{ TB} MySQL database over Dedicated Interconnect; 3) Execute Storage Transfer Service delta sync for incremental updates accrued during shipping; 4) Stop on-premises write traffic and wait for DMS replication lag to reach zero; 5) Promote Cloud SQL to primary and update application connection endpoints.
The correct operational sequence begins by addressing the largest migration bottleneck offline via Transfer Appliance (3.5 PB3.5\text{ PB} bulk historical data). Next, continuous online replication for the active database (8 TB8\text{ TB} MySQL) is established using Database Migration Service with CDC over the Dedicated Interconnect. Once the physical appliance data is loaded in GCP, Storage Transfer Service updates any delta changes accrued during appliance shipping. Finally, write traffic to the source database is stopped during the cutover window to achieve zero replication lag before promoting Cloud SQL and updating application endpoints.

Adım Adım Çözüm

1
Seed bulk offline archive data (3.5 PB3.5\text{ PB}) via Transfer Appliance.
Initial 3.5 PB3.5\text{ PB} archive is safely shipped and loaded into Cloud Storage without choking the 300 Mbps300\text{ Mbps} network cap.
Petabyte-scale transfers over limited bandwidth require physical appliance offloading to meet project schedules.
2
Establish continuous online database replication using DMS with CDC for the 8 TB8\text{ TB} MySQL workload.
Database replication runs in the background while production write operations continue uninterrupted on-premises.
Continuous CDC minimizes cutover downtime to just the time needed for final log flush and endpoint redirection.
3
Perform delta catch-up sync using Storage Transfer Service.
Incremental SAN updates generated during Appliance transit are synced to Cloud Storage.
Guarantees complete file storage sync before cutting over application workflows.
4
Initiate cutover window by stopping writes on-premises and confirming zero DMS replication lag.
Ensures no un-replicated transactions remain in the pipeline.
Prevents split-brain scenarios and data loss before database promotion.
5
Promote Cloud SQL to primary and update application configurations.
Application traffic resumes pointing directly to Google Cloud services within the 1-hour1\text{-hour} downtime limit.
Final step to complete workload migration and switch over production operations.

Anahtar Kavram

Combining offline bulk transfer (Transfer Appliance) for multi-petabyte historical datasets with online continuous replication (DMS with CDC) for transactional databases to minimize cutover downtime and network saturation.
Tahmini Süre:2m 30s
Soru 482Soru

A cloud administrator is setting up access controls for a departmental team in Google Cloud across multiple projects inside a designated folder. Which TWO access management strategies follow Google Cloud recommended best practices for resource hierarchy and Identity and Access Management (IAM)?

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

Cevabı ve açıklamayı göster

Cevap: Grant predefined IAM roles at the folder level to allow permissions to automatically inherit down to all child projects within that department.; Assign fine-grained predefined roles matching specific job responsibilities rather than using primitive roles.

Cevap

The correct access management strategies are granting predefined IAM roles at the folder level to leverage resource hierarchy inheritance, and assigning fine-grained predefined roles tailored to specific job responsibilities instead of primitive roles.
In Google Cloud IAM, permissions inherit downward through the resource hierarchy. Applying predefined roles at the folder level simplifies administration while automatically applying permissions to child projects. Furthermore, assigning fine-grained predefined roles guarantees that identities receive only the specific access required for their operational tasks.

Adım Adım Çözüm

1
Evaluate the inheritance mechanism of the Google Cloud resource hierarchy.
Permissions applied at parent resource nodes (such as Folders) automatically propagate down to child resources (such as Projects).
Binding roles at the folder level centralizes access management for all projects within that folder.
2
Determine the appropriate IAM role type to satisfy least privilege requirements.
Predefined roles offer fine-grained control for specific workloads, whereas primitive roles grant overly broad permissions.
Using predefined roles minimizes potential security risks by granting only required permissions.

Anahtar Kavram

IAM Resource Hierarchy Inheritance and Fine-Grained Predefined Roles
Soru 483Soru

An industrial equipment manufacturer needs to migrate 50 TB50\text{ TB} of unstructured binary firmware archives from on-premises network-attached storage (NAS) to Cloud Storage. The company maintains an existing 1 Gbps1\text{ Gbps} Dedicated Interconnect connection to Google Cloud, with 700 Mbps700\text{ Mbps} of available bandwidth dedicated to the transfer. Corporate security policy dictates that data must be transferred strictly over private networking without traversing the public internet, and the migration must complete in under 88 days. Which data transfer architecture should you recommend?

Cevabı ve açıklamayı göster

Cevap: Deploy Storage Transfer Service on-premises agents within the local network to transfer the files directly to Cloud Storage via private Google access over the Dedicated Interconnect.

Cevap

Deploy Storage Transfer Service on-premises agents within the local network to transfer the files directly to Cloud Storage via private Google access over the Dedicated Interconnect.
Storage Transfer Service agents installed on-premises efficiently orchestrate scale-out file reads and stream them directly over Private Google Access via the existing Dedicated Interconnect. Based on the available 700 Mbps bandwidth, 50 TB transfers in roughly 6.6 days, satisfying both the 8-day deadline and the strict private networking requirement.

Adım Adım Çözüm

1
Calculate network throughput and required transfer time
Converting 50 TB50\text{ TB} to bits yields 50×1,000×8=400,000 Gb50 \times 1,000 \times 8 = 400,000\text{ Gb}. At 700 Mbps700\text{ Mbps} (0.7 Gbps0.7\text{ Gbps}), total transfer time is 400,0000.7571,428 seconds6.61 days\frac{400,000}{0.7} \approx 571,428\text{ seconds} \approx 6.61\text{ days}.
Verifies that online data transfer over the existing connection fits comfortably inside the 8-day deadline.
2
Evaluate network route and security constraints
Using Storage Transfer Service on-premises agents routes traffic through the Dedicated Interconnect using Private Google Access endpoints.
Satisfies the security requirement that data must not traverse the public internet.
3
Compare online transfer efficiency against offline hardware appliance options
Online transfer completes in approximately 6.6 days automatically, whereas ordering and shipping a Transfer Appliance adds logistics latency.
Confirms Storage Transfer Service over Cloud Interconnect is the optimal architectural selection.

Anahtar Kavram

Selecting Online vs. Offline Data Migration Strategies in GCP
Soru 484Soru

An enterprise cloud architect needs to prevent developers from assigning external IP addresses to any new Compute Engine instances created within a specific organizational folder. Which Google Cloud solution should be implemented to enforce this restriction across all projects in the folder?

Cevabı ve açıklamayı göster

Cevap: Configure an Organization Policy with the `constraints/compute.vmExternalIpAccess` constraint applied at the folder level.

Cevap

Configure an Organization Policy with the `constraints/compute.vmExternalIpAccess` constraint applied at the folder level.
Applying an Organization Policy with the `constraints/compute.vmExternalIpAccess` constraint at the folder level ensures that all current and future child projects inherit the restriction, preventing any VM instance from being provisioned with an external IP address.

Adım Adım Çözüm

1
Identify the governance requirement.
The requirement is to restrict Compute Engine VM instances from being provisioned with external IP addresses within a folder.
Centralized resource configuration restrictions across resource hierarchy nodes require Organization Policy constraints.
2
Select the appropriate constraint and target node.
Applying `constraints/compute.vmExternalIpAccess` at the folder level restricts external IP assignments for all child projects.
Organization Policies control resource configurations independently of IAM identity permissions and inherit down the resource hierarchy.

Anahtar Kavram

Organization Policies provide centralized programmatic control over organizational resources by enforcing policy constraints across the GCP resource hierarchy.
Soru 485Soru

An online media company is preparing to launch a live video transcoding service using Terraform to provision Compute Engine regional Managed Instance Groups (MIGs). The architecture requires scaling up to 400 N2 vCPUs in the us-central1 region during peak events. However, new GCP projects have a default regional vCPU quota well below this requirement. What architectural action should be taken prior to the initial production deployment to prevent provisioning failures?

Cevabı ve açıklamayı göster

Cevap: Request a regional vCPU quota increase in advance for the target region and wait for approval before executing the automated infrastructure provisioning.

Cevap

Request a regional vCPU quota increase in advance for the target region and wait for approval before executing the automated infrastructure provisioning.
Google Cloud enforces resource quotas on projects to prevent unexpected resource consumption and ensure cloud capacity. Default quotas for new projects are intentionally limited. To deploy large instance pools, cloud architects must submit quota increase requests in advance for the target region.

Adım Adım Çözüm

1
Assess the peak capacity requirements of the workload
Identified requirement of 400 N2 vCPUs in region us-central1.
Large deployments must be compared against default project quota allocations.
2
Verify current regional quotas in Google Cloud Console or via gcloud CLI
Found that default regional vCPU quota is insufficient for peak scaling.
Resource creation will fail at runtime if requested capacity exceeds existing quota.
3
Submit a quota increase request for regional vCPUs prior to deployment
GCP quota team reviews and approves the regional capacity increase.
Quota increases require lead time for approval before Infrastructure as Code automation can provision resources.

Anahtar Kavram

Compute Engine Resource Quotas and Provisioning Prerequisites
Soru 486Soru

A DevOps team is preparing to provision additional Compute Engine instances for a seasonal analytics workload in a newly enabled Google Cloud region. Which action should the team take prior to deployment to prevent provisioning failures caused by resource limits?

Cevabı ve açıklamayı göster

Cevap: Evaluate current regional Compute Engine quota limits and request necessary limit increases in advance of provisioning.

Cevap

Evaluating regional Compute Engine quota limits and requesting necessary limit increases prior to provisioning.
Proactively evaluating regional capacity demands and requesting quota adjustments prior to deployment prevents provisioning scripts from failing due to default quota constraints.

Adım Adım Çözüm

1
Assess workload capacity requirements against default project quota allocations in the target region.
Identified potential quota shortfalls prior to deployment.
Default quota limits may not satisfy full workload requirements in a new region.
2
Submit quota increase requests via the Google Cloud Console or Service Usage API ahead of execution.
Quotas are approved and increased by Google Cloud before automated scripts run.
Quota increases require evaluation and processing time by GCP.

Anahtar Kavram

Proactive Service Quotas Management
Soru 487Soru

A global logistics enterprise needs to connect its primary on-premises data center to a Google Cloud environment containing resources across two regions: us-east1 and europe-west3. The connection requires a guaranteed bandwidth of 8 Gbps to support continuous telemetry processing and sub-50ms latency. The organization does not have a physical presence in a Google colocation facility and must rely on a third-party network service provider. Additionally, on-premises workloads must seamlessly reach resources in both Google Cloud regions over the private connection. Which hybrid connectivity architecture should you implement?

Cevabı ve açıklamayı göster

Cevap: Provision Partner Interconnect VLAN attachments through a supported service provider and enable Global Dynamic Routing on the VPC network.

Cevap

Provision Partner Interconnect VLAN attachments through a supported service provider and enable Global Dynamic Routing on the VPC network.
The correct approach provisions Partner Interconnect because the organization cannot colocate directly at a Google facility for Dedicated Interconnect and requires bandwidth (>3 Gbps) beyond standard HA VPN capabilities. Enabling Global Dynamic Routing on the VPC allows Cloud Routers connected to the Partner Interconnect VLAN attachments to dynamically learn and propagate routes across both us-east1 and europe-west3 regions.

Adım Adım Çözüm

1
Evaluate bandwidth and physical facility constraints
Requirements specify 8 Gbps throughput and no direct colocation facility presence. Partner Interconnect is selected over Dedicated Interconnect (requires colocation) and HA VPN (capped at 3 Gbps per tunnel).
Partner Interconnect provides high-bandwidth private connectivity through partner service providers when direct colocation at a Google edge location is not possible.
2
Determine multi-region routing configuration within the VPC
Set VPC dynamic routing mode from Regional to Global.
Global Dynamic Routing allows Cloud Routers in us-east1 and europe-west3 to exchange BGP routes dynamically with the on-premises router and advertise VPC subnets in all regions.

Anahtar Kavram

Selecting and configuring high-throughput hybrid connectivity via Partner Interconnect with Global Dynamic Routing
Soru 488Soru

An enterprise organization maintains a Google Cloud VPC network with subnets provisioned in both `us-central1` and `europe-west1`. The organization establishes a Dedicated Interconnect connection attached to a Cloud Router residing in `us-central1` to link their on-premises data center. Virtual machine instances deployed in `europe-west1` must dynamically receive on-premises routes advertised via BGP and route egress traffic to the on-premises network through the `us-central1` Cloud Router without establishing additional physical interconnects or manually managing static routes. Which VPC network routing configuration should you implement to satisfy this requirement?

Cevabı ve açıklamayı göster

Cevap: Set the dynamic routing mode of the VPC network from Regional to Global.

Cevap

Setting the VPC network's dynamic routing mode from Regional to Global enables Cloud Routers in us-central1 to share learned BGP routes with resources across all regions in the VPC, including europe-west1.
In Google Cloud VPC networks, the dynamic routing mode determines the scope in which Cloud Routers share routes. In Regional dynamic routing mode (the default for auto-mode networks), a Cloud Router only learns and advertises routes for resources in its local region. By configuring the dynamic routing mode to Global, Cloud Routers share learned BGP routes (such as on-premises subnets learned over Cloud Interconnect) with all subnets across all regions in the VPC.

Adım Adım Çözüm

1
Analyze the network requirement for cross-region dynamic route propagation.
Identified that resources in `europe-west1` need access to routes learned by a Cloud Router in `us-central1`.
By default, Google Cloud VPC networks use Regional dynamic routing mode, restricting Cloud Router BGP routes to resources in the Cloud Router's local region.
2
Evaluate Google Cloud VPC dynamic routing mode options.
Changing the dynamic routing mode to Global allows BGP routes learned by Cloud Router in any region to be propagated to all subnets in the VPC network globally.
Global dynamic routing enables global visibility of learned routes without needing extra hardware, static routes, or additional VPN tunnels.

Anahtar Kavram

VPC Dynamic Routing Modes (Regional vs. Global)
Soru 489Soru

An organization plans to establish a Dedicated Interconnect connection between its on-premises network and a Google Cloud Virtual Private Cloud (VPC) network. Which TWO configuration steps are required to set up this hybrid connectivity solution? (Select two.)

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

Cevabı ve açıklamayı göster

Cevap: Provision physical cross-connects between the on-premises router and Google edge router at a supported colocation facility.; Configure a Cloud Router and create VLAN attachments (interconnect attachments) in the target GCP VPC network.

Cevap

The two required steps are provisioning physical cross-connects at a supported colocation facility and configuring a Cloud Router with VLAN attachments in the GCP VPC network.
Establishing a Dedicated Interconnect requires physical cross-connects between the on-premises router and Google edge routers at a colocation facility. Additionally, logically connecting the VPC requires establishing VLAN attachments and configuring a Cloud Router to manage BGP sessions for dynamic route exchanges.

Adım Adım Çözüm

1
Identify the physical connection requirements for Dedicated Interconnect.
Determine that physical cross-connect cables must be ordered and provisioned at a supported Google colocation facility.
Dedicated Interconnect requires direct physical fiber connectivity to Google edge infrastructure.
2
Identify the logical routing requirements in Google Cloud.
Create a Cloud Router and construct VLAN attachments within the target VPC network.
VLAN attachments allocate private VLANs on the connection, and Cloud Router manages BGP dynamic routing sessions to exchange routes.

Anahtar Kavram

Configuring Dedicated Interconnect physical cross-connects and logical Cloud Router BGP attachments
Soru 490Soru

Match each application workload access pattern and architectural requirement to the most appropriate Google Cloud storage or database service.

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

Öğeler

High-throughput time-series metric ingestion exceeding 1,000,0001,000,000 writes per second requiring low single-digit millisecond latency key-value reads by timestamp.
Globally distributed relational OLTP database requiring full ANSI SQL support, multi-region ACID transactions, and a 99.999%99.999\% availability SLA.
Sub-millisecond latency in-memory data store supporting complex data structures, geospatial queries, and session caching.
Serverless document store offering automatic offline client sync, live query snapshot listeners, and multi-region atomic transactions for web and mobile frontends.

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

High-throughput time-series metric ingestion matches Cloud Bigtable. Globally distributed relational OLTP with multi-region ACID guarantees matches Cloud Spanner. Sub-millisecond in-memory caching with geospatial support matches Memorystore for Redis. Serverless document storage with offline sync matches Firestore.
Each workload specification aligns directly with the architectural design principles of GCP database offerings: Cloud Bigtable for high-scale write-heavy time-series, Cloud Spanner for globally distributed relational ACID transactions, Memorystore for Redis for sub-millisecond in-memory operations, and Firestore for serverless real-time document synchronization.

Adım Adım Çözüm

1
Analyze high-throughput time-series ingestion requirement (>1,000,000 writes/sec)
Identify Cloud Bigtable as the optimal scalable NoSQL wide-column store designed for time-series metrics and heavy write throughput.
Cloud Bigtable scales linearly to handle millions of IOPS with consistent low-latency key lookups.
2
Evaluate global relational OLTP requirement with a 99.999% availability SLA
Identify Cloud Spanner as the target managed relational database.
Cloud Spanner uses TrueTime hardware clocks and Paxos consensus to deliver multi-region strong consistency and five-nines availability.
3
Examine sub-millisecond caching requirement with geospatial query capabilities
Identify Memorystore for Redis.
Memorystore for Redis delivers ultra-low latency in-memory data management supporting advanced Redis primitives like GEO indexing.
4
Review mobile/web frontend document store requirement with offline sync and live listeners
Identify Firestore.
Firestore client SDKs natively support real-time data sync, offline data caching, and automatic scaling for app developers.

Anahtar Kavram

Evaluating workload access patterns, consistency requirements, scale, and latency targets to select optimal GCP storage and database resources.
Soru 491Soru

A healthcare enterprise is modernizing its telemetry processing service on Google Cloud. The application receives persistent WebSocket connections streaming real-time metric updates from medical IoT devices. The workload is stateless and packaged as a Docker container. During nighttime off-peak hours, device traffic drops to zero, and the platform must automatically scale down to zero active instances to eliminate infrastructure costs. During daytime operational hours, the service experiences sudden traffic spikes and must eliminate cold-start latency for incoming connections while minimizing operational overhead by using a fully managed serverless infrastructure. Which compute architecture should the Lead Cloud Architect recommend?

Cevabı ve açıklamayı göster

Cevap: Deploy the containerized service on Cloud Run, configuring request concurrency to accommodate multiple WebSocket connections per instance, setting minimum instances during operational hours, and allowing autoscaling to zero instances during off-peak hours.

Cevap

Deploying the containerized service on Cloud Run with high request concurrency, minimum instances configured during operational hours, and scale-to-zero enabled off-peak meets all technical, operational, and cost requirements.
Cloud Run is the optimal Google Cloud compute platform for stateless containerized applications that require zero operational infrastructure management. It natively supports WebSockets and allows multiple concurrent requests per instance. By configuring minimum instances during peak operational hours, cold starts are eliminated. During off-peak hours, setting minimum instances to zero allows Cloud Run to scale down completely, incurring zero compute cost.

Adım Adım Çözüm

1
Analyze operational overhead requirements
Fully managed serverless platforms (such as Cloud Run) eliminate cluster management and node provisioning overhead compared to GKE or Compute Engine MIGs.
The enterprise requirement specifies zero VM or cluster management overhead.
2
Evaluate workload scaling and protocol requirements
Cloud Run natively supports stateless containerized workloads, WebSocket protocols, multi-concurrency per instance, and autoscaling down to zero instances.
Persistent WebSocket connections demand high concurrency per instance and seamless scale-to-zero support during off-peak hours.
3
Address latency and cold-start constraints during peak hours
Setting Cloud Run minimum instances during daytime operational hours ensures pre-warmed instances handle incoming traffic without cold-start spikes.
Minimum instances maintain baseline readiness during operational hours while permitting complete scale-to-zero overnight.

Anahtar Kavram

Selecting Cloud Run for stateless containerized workloads requiring serverless operations, WebSocket protocol support, custom concurrency, and cold-start mitigation via minimum instances.
Soru 492Soru

A financial software firm uses Google Cloud Deploy to automate releases across multiple staging and production Kubernetes clusters. To meet strict regulatory auditing standards, all deployment target definitions and pipeline release manifests must be immutably tracked and automatically applied without manual interventions. However, an operator recently modified target cluster endpoints directly using the gcloud CLI to resolve an emergency outage, causing subsequent automated pipeline runs to fail due to state inconsistency. Which architectural practice should the Cloud Architect implement to eliminate configuration drift and ensure compliant pipeline provisioning?

Cevabı ve açıklamayı göster

Cevap: Define Cloud Deploy pipelines and targets declaratively in version-controlled YAML manifests managed by Terraform, applying changes exclusively through an automated CI/CD pipeline while restricting direct write IAM permissions.

Cevap

Define Cloud Deploy pipelines and target resources declaratively using version-controlled manifests managed via Infrastructure as Code (Terraform) in an automated pipeline, revoking manual write permissions.
Managing Cloud Deploy pipelines and targets declaratively through version-controlled Infrastructure as Code (such as Terraform) ensures all infrastructure changes are peer-reviewed, reproducible, and auditable. Revoking direct write access from human operators prevents imperative CLI drift and maintains continuous deployment reliability.

Adım Adım Çözüm

1
Analyze the root cause of pipeline failures
Identified that imperative manual updates using gcloud created configuration drift between the environment state and the automated release definitions.
Manual modifications bypass source control and break automated deployment synchronization.
2
Establish declarative Infrastructure as Code governance
Define all Cloud Deploy delivery pipelines and target resources in version-controlled configuration files managed by Terraform.
Declarative manifests stored in version control serve as the single source of truth for deployment infrastructure.
3
Enforce least privilege access controls on infrastructure modification
Restrict user IAM roles to prevent direct write operations on Cloud Deploy targets and restrict target management to automated service accounts.
Prevents unauthorized or out-of-band imperative CLI changes, guaranteeing audit compliance and pipeline stability.

Anahtar Kavram

Continuous Deployment Infrastructure Automation and Drift Prevention
Tahmini Süre:2m 0s
Soru 493Soru

An operations engineering team is setting up real-time operational monitoring for a web application hosted on Google Cloud. The team needs to track HTTP 500 internal server error occurrences logged by the web server and automatically trigger incident alerts whenever the error count exceeds 50 occurrences within a 5-minute rolling window. Which TWO actions must be configured to achieve this operational observability setup? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Create a counter log-based metric in Cloud Logging filtered by log entries matching severity level ERROR and HTTP response status code 500.; Create an alerting policy in Cloud Monitoring conditioned on the custom log-based metric exceeding a threshold of 50 over a 5-minute alignment period.

Cevap

To configure real-time error alerting based on application log events, you must create a counter log-based metric in Cloud Logging filtered for HTTP 500 error logs, and then configure a Cloud Monitoring alerting policy that monitors this log-based metric against the threshold of 50 errors per 5 minutes.
Defining a counter log-based metric in Cloud Logging allows specific log event criteria (HTTP 500 errors) to be tracked as numerical time-series data. Setting up a Cloud Monitoring alerting policy conditioned on this metric threshold enables automated incident alerts when the error threshold is breached within the specified 5-minute window.

Adım Adım Çözüm

1
Define a counter log-based metric in Cloud Logging.
Cloud Logging starts counting log entries that match the filter criteria (severity ERROR and HTTP status code 500) and exposes them as a metric stream in Cloud Monitoring.
Log-based metrics convert unstructured or structured log event counts into numerical time-series data suitable for monitoring and alerting.
2
Create an alerting policy in Cloud Monitoring based on the newly created log-based metric.
The alerting policy measures the rate of incoming HTTP 500 error metrics over a 5-minute rolling aggregation window.
Setting the threshold condition to 50 triggers automated notifications whenever high error rates violate operational requirements.

Anahtar Kavram

Log-based Metrics and Operational Alerting in Google Cloud Observability
Soru 494Soru

An enterprise software team is provisioning a private Google Kubernetes Engine (GKE) cluster in Google Cloud to process internal HR data. The cluster control plane must be isolated from public network access, allowing administrative gcloud and kubectl commands strictly from designated on-premise management subnet ranges via Cloud VPN. Additionally, automated deployment pipelines provisioning the node pools must adhere to the principle of least privilege when configuring service account bindings. Which TWO actions should you take to provision this cluster environment securely?

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 the designated on-premise CIDR blocks.; Grant the deployment pipeline identity the Service Account User role (roles/iam.serviceAccountUser) on the custom node service account.

Cevap

To configure a private GKE cluster isolated to corporate management subnets under least privilege, you must enable Control Plane Authorized Networks with designated on-premise CIDR blocks and grant the deployment pipeline identity the Service Account User role on the custom node service account.
Enabling Control Plane Authorized Networks restricts API server endpoint access to explicit CIDR blocks (such as corporate subnets reaching Google Cloud over VPN). For identity management, granting the Service Account User role to the provisioning pipeline satisfies least privilege by permitting the pipeline to assign the custom service account to GKE nodes without giving administrative authority to modify IAM service accounts.

Adım Adım Çözüm

1
Identify network security controls for private GKE control plane endpoints.
Control Plane Authorized Networks must be enabled to filter incoming cluster management traffic down to approved corporate CIDR ranges.
IAM authentication alone does not prevent network-level reachability; authorized networks establish an endpoint IP firewall.
2
Determine the minimal IAM permissions required for infrastructure pipelines to attach compute identities.
Assign roles/iam.serviceAccountUser to the deployment identity.
This allows the pipeline to bind the service account to compute instances/node pools without granting administrative control over IAM resources.

Anahtar Kavram

Private GKE Cluster Endpoint Security and IAM Least Privilege Service Account Delegation
Soru 495Soru

A cloud administrator is provisioning database and storage resources for a regional web application. The application requires a standard relational database to support regional OLTP operations, and organization policies mandate that encryption key management must be handled within Google Cloud without requiring administrators to store or pass raw key material. Which of the following provisioning decisions should be implemented? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Provision a Cloud SQL instance to serve the regional relational database workload.; Configure Customer-Managed Encryption Keys (CMEK) using Cloud KMS to manage data encryption keys.

Cevap

The correct provisioning choices are to deploy a Cloud SQL instance for the regional relational workload and to configure Customer-Managed Encryption Keys (CMEK) via Cloud KMS for key governance.
Selecting Cloud SQL fits standard regional relational requirements without the cost and complexity of global scaling services. Utilizing CMEK via Cloud KMS satisfies encryption governance requirements by allowing organizations to control key lifecycle and rotation policies natively without holding raw encryption key material.

Adım Adım Çözüm

1
Select the appropriate database engine for regional scope
Choose Cloud SQL because it efficiently supports standard single-region relational OLTP workloads.
Cloud Spanner is meant for globally distributed multi-region scale, making Cloud SQL the optimal choice for regional needs.
2
Select the appropriate encryption key configuration
Choose Customer-Managed Encryption Keys (CMEK) using Cloud KMS.
CMEK permits key lifecycle control inside Google Cloud without requiring raw key management as CSEK does.

Anahtar Kavram

Provisioning Cloud SQL for regional relational databases and applying CMEK with Cloud KMS for managed encryption key control.
Soru 496Soru

A fintech company is designing the architecture for a multi-tenant payment platform on Google Cloud. The application architecture consists of two distinct workloads:

1. A stateless HTTP microservice that receives incoming webhook events from payment gateways, experiences unpredictable bursty traffic patterns, and must automatically scale down to zero when idle to minimize costs.
2. A stateful financial transaction streaming engine that maintains persistent TCP/WebSocket connections, requires low-level Linux kernel parameter tuning (`sysctl`), and relies on local state storage across connections.

Which TWO compute platform architectural choices should the cloud architect recommend to satisfy the technical requirements of both workloads while minimizing operational overhead?

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

Cevabı ve açıklamayı göster

Cevap: Deploy the stateless webhook service to Cloud Run to leverage serverless autoscaling to zero and eliminate infrastructure management.; Deploy the stateful transaction streaming engine to Compute Engine virtual machines in a Managed Instance Group (MIG) to allow custom Linux kernel parameter modifications.

Cevap

The optimal solution is to deploy the stateless webhook service to Cloud Run and deploy the stateful transaction streaming engine to Compute Engine virtual machines in a Managed Instance Group.
Cloud Run is the recommended platform for stateless HTTP webhooks because it automatically scales containers based on incoming requests, scales to zero during idle periods, and removes server management overhead. Compute Engine is required for the stateful streaming engine because serverless and fully managed container environments do not allow low-level Linux kernel (`sysctl`) modifications or local state persistence required by custom TCP socket engines.

Adım Adım Çözüm

1
Analyze the requirements for the stateless webhook workload.
Identified that the service processes incoming HTTP webhooks, experiences unpredictable traffic spikes, requires autoscaling to zero, and has no stateful OS requirements.
Cloud Run provides fully managed serverless container execution for HTTP requests, scaling down to zero when idle and abstracting cluster maintenance.
2
Analyze the requirements for the stateful transaction streaming workload.
Identified that the streaming service requires custom Linux kernel tuning (`sysctl`), persistent state, and long-lived TCP/WebSocket connections.
Compute Engine VMs provide direct operating system access required for custom kernel parameters and stateful streaming architectures.
3
Evaluate candidate platforms against operational overhead and technical feasibility.
Select Cloud Run for the stateless microservice and Compute Engine MIGs for the stateful kernel-dependent service.
This combination avoids unnecessary cluster management for stateless services while supplying OS-level control where strictly required.

Anahtar Kavram

Selecting GCP Compute Platforms based on Statefulness, Operating System Controls, and Operational Overhead
Soru 497Soru

An enterprise architecture team is designing governance and billing controls for a multi-project GCP organization running large-scale, intermittent batch processing workloads across multiple regions. The team needs to establish proactive quota management to prevent capacity exhaustion and implement automated cost controls without risking hard cut-offs of critical production data pipelines. Which TWO architectural actions should the Cloud Architect recommend?

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

Cevabı ve açıklamayı göster

Cevap: Set up Cloud Monitoring alerting policies based on regional quota allocation usage metrics to trigger notifications when utilization crosses defined thresholds prior to limit saturation.; Export Cloud Billing data to BigQuery at the billing account level and configure Cloud Billing Budget Pub/Sub notifications to trigger automated Cloud Functions for alerting and soft remediation.

Cevap

The Cloud Architect should recommend setting up Cloud Monitoring alerting policies based on quota allocation usage metrics and exporting Cloud Billing data to BigQuery with Budget Pub/Sub notifications triggering Cloud Functions.
Proactive quota governance requires monitoring usage metrics through Cloud Monitoring and creating alerts prior to saturation. For automated billing governance, exporting billing data to BigQuery provides deep visibility, and connecting Budget Pub/Sub notifications to Cloud Functions allows custom, non-disruptive remediation actions.

Adım Adım Çözüm

1
Evaluate proactive quota management requirements.
Identify that Cloud Monitoring provides metrics for quota allocation usage, allowing threshold alerting prior to hitting limits.
Quota increases require manual or automated request workflows and processing time, making proactive threshold alerts essential.
2
Evaluate cost governance and budget automation requirements.
Identify that billing export to BigQuery combined with Budget Pub/Sub notifications enables automated soft-remediation workflows.
Direct Pub/Sub budget notifications allow programmatic responses without hard-stopping production workloads.
3
Analyze distractors against GCP best practices.
Reject primitive role assignment (violates IAM least privilege and cannot override quotas) and 3-year CUDs for peak intermittent workloads (causes severe over-spending).
Security governance and FinOps principles require least privilege IAM and flexible commitments aligned with actual workload patterns.

Anahtar Kavram

Proactive Quota Alerting, BigQuery Billing Export, and Programmatic Budget Remediation
Soru 498Soru

An enterprise organization enforces strict data residency rules across its Google Cloud environment. The lead cloud architect applies an Organization Policy list constraint (`constraints/gcp.resourceLocations`) at the Production Folder level, restricting resource creation strictly to `us-central1` and `us-east1`. A project team managing an isolated application inside this Production Folder requires deploying Compute Engine instances in `europe-west1` to satisfy European regulatory requirements. How should the architect configure Google Cloud governance to permit `europe-west1` deployment for this specific project while maintaining the folder-level policy for all other projects?

Cevabı ve açıklamayı göster

Cevap: Set an Organization Policy override on the specific Project resource node that modifies the allowed values list to include `europe-west1`.

Cevap

Set an Organization Policy override directly at the Project level that updates the allowed locations list to include `europe-west1`.
The correct option correctly leverages Google Cloud's resource hierarchy inheritance rules. Organization Policies inherit down from Organization to Folder to Project. When a specific project requires an exception to a parent folder's list constraint, defining a local policy override on that project node allows specifying custom allowed values (`europe-west1`) for that project while leaving the rest of the folder protected by the original rule.

Adım Adım Çözüm

1
Analyze resource hierarchy inheritance
Organization Policies defined at parent nodes (Folder) inherit down to child nodes (Projects) by default.
Understanding hierarchy evaluation is essential for determining where policy adjustments take effect.
2
Evaluate mechanisms for policy exceptions
Lower-level nodes in the hierarchy can override inherited policies by defining explicit policy rules at that specific level.
Setting an override at the Project level replaces or merges the inherited policy for that project specifically without altering the policy inherited by sibling projects.

Anahtar Kavram

Organization Policy Resource Hierarchy Inheritance and Overrides
Soru 499Soru

A digital media organization is provisioning a private Google Kubernetes Engine (GKE) cluster in a dedicated Virtual Private Cloud (VPC) to run containerized video processing microservices. To comply with strict corporate governance, administrative access to the cluster control plane must be restricted exclusively to a specified corporate network CIDR block (172.16.50.0/24172.16.50.0/24). Additionally, automated continuous integration/continuous delivery (CI/CD) worker virtual machines running in Compute Engine must be permitted to attach a dedicated service account to workloads without having privileges to alter service account IAM policies. Which combination of configuration steps should the cloud architect perform to provision this environment correctly?

Cevabı ve açıklamayı göster

Cevap: Enable control plane authorized networks on the private GKE cluster configured with 172.16.50.0/24172.16.50.0/24, and grant the Service Account User role (`roles/iam.serviceAccountUser`) on the target service account to the CI/CD worker instances.

Cevap

Enable control plane authorized networks on the private GKE cluster specifying the designated subnet range (172.16.50.0/24172.16.50.0/24), and grant the Service Account User role (`roles/iam.serviceAccountUser`) to the CI/CD worker instances.
Enabling control plane authorized networks on a private GKE cluster ensures that only specified CIDR blocks (such as 172.16.50.0/24172.16.50.0/24) can reach the cluster's API server. Coupling this network security control with the Service Account User role (`roles/iam.serviceAccountUser`) allows compute workers to act as or attach the service account to deployed resources without giving them authority to alter service account configurations or security policies.

Adım Adım Çözüm

1
Configure Control Plane Endpoint Security
Control plane authorized networks are enabled on the private GKE cluster with CIDR 172.16.50.0/24172.16.50.0/24.
This restricts HTTPS access to the GKE cluster master endpoint so that only traffic originating from the authorized corporate network range can communicate with the Kubernetes API server.
2
Apply Least-Privilege IAM Roles for Workload Provisioning
The CI/CD worker instances are granted `roles/iam.serviceAccountUser` on the deployment service account.
This enables the CI/CD pipeline to bind and use the dedicated service account when creating pods or compute instances while withholding administrative management permissions over the service account object.

Anahtar Kavram

Provisioning Private GKE Clusters with Control Plane Authorized Networks and Least-Privilege IAM Roles
Tahmini Süre:2m 0s
Soru 500Soru

A healthcare organization is migrating its electronic health record (EHR) system to Google Cloud. The architecture team requires a hybrid network solution connecting their on-premises data centers to a Virtual Private Cloud (VPC) network. To support continuous data replication, the architecture must deliver at least 20 Gbps of bandwidth and satisfy Google Cloud's 99.99% uptime Service Level Agreement (SLA) for Dedicated Interconnect. Which two architectural configurations must be implemented to achieve this SLA requirement? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Provision at least four Dedicated Interconnect connections distributed across two distinct edge availability domains (metropolitan areas).; Configure redundant Cloud Routers in the VPC network and attach VLAN attachments from separate edge locations to different Cloud Routers.

Cevap

To meet Google Cloud's 99.99% availability SLA for Dedicated Interconnect, the architecture requires provisioning four Dedicated Interconnect connections across two edge availability domains (metropolitan areas) and configuring redundant Cloud Routers with VLAN attachments distributed across them.
Google Cloud defines explicit architecture requirements to achieve a 99.99% SLA for Dedicated Interconnect: organizations must deploy four Dedicated Interconnect connections distributed across two edge availability domains (metropolitan areas) and configure redundant Cloud Routers in the VPC network with VLAN attachments connecting to each edge domain.

Adım Adım Çözüm

1
Analyze high-availability topology requirements for GCP Dedicated Interconnect 99.99% SLA.
GCP topology rules specify that 99.99% availability requires 4 Dedicated Interconnect connections split evenly across 2 distinct edge availability domains.
Redundancy across multiple edge facilities protects against metro-level or facility-level hardware outages.
2
Determine Cloud Router and control plane redundancy requirements.
Two Cloud Routers must be deployed in the VPC network, each hosting VLAN attachments linked to different edge availability domains.
This guarantees that BGP dynamic routing sessions remain active even if one Cloud Router or edge location fails.
3
Evaluate bandwidth and network service boundaries.
Dedicated Interconnect provides 10 Gbps or 100 Gbps physical circuits per connection, easily meeting the 20 Gbps requirement, whereas Cloud VPN is limited to 3 Gbps per tunnel.
HA Cloud VPN cannot handle 20 Gbps throughput as a single primary link.

Anahtar Kavram

Dedicated Interconnect 99.99% High Availability Topology Requirements
ÖncekiSayfa 25 / 80Sonraki
Tüm alıştırma soruları — Google Cloud Professional Cloud Architect | Examkin