Tüm alıştırma soruları

1598 soru

Soru 501Soru

A enterprise compliance team needs to restrict virtual machines from being assigned public IP addresses across a development folder while testing policy impact before enforcing strict blocking. Which TWO actions should a Cloud Architect perform using Google Cloud Organization Policies? (Select TWO)

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

Cevabı ve açıklamayı göster

Cevap: Set the `constraints/compute.vmExternalIpAccess` boolean constraint to enforce policy restriction on the targeted folder.; Configure the organization policy enforcement mode to Dry-Run to audit potential violations without blocking VM creation.

Cevap

To prevent Compute Engine instances from receiving public IP addresses while evaluating impact safely, the architect must apply the `constraints/compute.vmExternalIpAccess` constraint at the target folder level and configure policy enforcement to Dry-Run mode.
Applying the `constraints/compute.vmExternalIpAccess` constraint directly enforces restrictions on external IP provisioning, while setting dry-run mode allows auditing and logging of non-compliant configurations without breaking active workflows.

Adım Adım Çözüm

1
Identify the target resource hierarchy node and constraint for external IP restriction.
Select `constraints/compute.vmExternalIpAccess` and apply it to the development folder node.
Organization policies control specific resource behavior across hierarchy trees.
2
Set the organization policy state to Dry-Run mode.
Violations are logged to Cloud Logging while allowing teams to evaluate impact before full enforcement.
Dry-run mode enables governance verification without disrupting ongoing development operations.

Anahtar Kavram

Organization Policy Constraints and Dry-Run Enforcement
Soru 502Soru

A cloud architect is configuring network connectivity across three independent Google Cloud Virtual Private Cloud (VPC) networks: VPC-1, VPC-2, and VPC-3. Active VPC Network Peering connections exist between VPC-1 and VPC-2, as well as between VPC-2 and VPC-3. Compute instances in VPC-1 are unable to reach instances in VPC-3 using internal IP addresses. Which network topology configuration is required to allow direct private communication between VPC-1 and VPC-3?

Cevabı ve açıklamayı göster

Cevap: Establish a direct VPC Network Peering connection between VPC-1 and VPC-3.

Cevap

Establish a direct VPC Network Peering connection between VPC-1 and VPC-3.
VPC Network Peering in Google Cloud is strictly non-transitive. Although VPC-1 is peered with VPC-2 and VPC-2 is peered with VPC-3, resources in VPC-1 cannot communicate with resources in VPC-3 via VPC-2. Establishing a direct peering connection between VPC-1 and VPC-3 is required to exchange internal IP routes between them.

Adım Adım Çözüm

1
Identify the routing limitation in Google Cloud VPC Network Peering.
Recognize that VPC Network Peering is strictly non-transitive, preventing network traffic from hopping through VPC-2 to reach VPC-3.
Google Cloud peering architecture restricts route propagation exclusively to directly peered VPC networks.
2
Select the correct topology configuration.
Configure a direct VPC Network Peering link between VPC-1 and VPC-3.
Direct peering enables native internal IP address communication and route exchange between the two networks.

Anahtar Kavram

VPC Network Peering Non-Transitivity
Soru 503Soru

A company organizes its Google Cloud resources into dedicated folders per department. The security team needs to grant a developer group read-only access to object content in all Cloud Storage buckets across all projects contained within the 'Data Analytics' folder. The solution must follow Google recommended best practices for least privilege and operational simplicity. Which IAM role assignment strategy should be implemented?

Cevabı ve açıklamayı göster

Cevap: Grant the predefined Storage Object Viewer role (roles/storage.objectViewer) to the group at the 'Data Analytics' folder level.

Cevap

Granting the predefined Storage Object Viewer role at the folder level leverages IAM resource hierarchy inheritance while enforcing the principle of least privilege.
In Google Cloud IAM, permissions defined on parent resources (such as Folders) are inherited downstream by all child resources (such as Projects and Cloud Storage buckets). Granting the predefined Storage Object Viewer role at the target folder level ensures that users receive the exact read permissions required for all present and future projects under that folder without granting unnecessary permissions.

Adım Adım Çözüm

1
Identify the resource scope and target permission requirement.
Access is needed for multiple projects inside a single folder ('Data Analytics'), specifically requiring read access to Cloud Storage objects.
Determining the parent resource container allows using IAM permission inheritance effectively.
2
Select the appropriate IAM role type adhering to least privilege.
The predefined role 'roles/storage.objectViewer' provides exact read permissions for Cloud Storage objects without granting broad administrative privileges.
Predefined roles are preferred over primitive roles (Owner/Editor/Viewer) to restrict access to only what is required.
3
Apply the role binding at the optimal level in the Google Cloud resource hierarchy.
Binding the role at the 'Data Analytics' folder level automatically propagates access to all child projects and buckets via inheritance.
Folder-level binding avoids repetitive per-project or per-bucket configuration, minimizing operational maintenance.

Anahtar Kavram

Resource hierarchy inheritance and fine-grained predefined IAM roles
Soru 504Soru

An enterprise security administrator needs to ensure that virtual machines created inside a specific environment folder cannot be configured with public IP addresses. Which GCP mechanism should be configured at the folder level to enforce this restriction?

Cevabı ve açıklamayı göster

Cevap: Configure an Organization Policy constraint that restricts external IP access for virtual machines.

Cevap

Configure an Organization Policy constraint that restricts external IP access for virtual machines.
Applying an Organization Policy with a constraint to restrict external IP access at the folder level enforces a centralized guardrail across all descendant projects. Organization Policies govern resource configuration properties independent of user IAM permissions.

Adım Adım Çözüm

1
Identify the core requirement
The goal is to restrict a specific compute infrastructure attribute (public IP assignment) across an entire folder hierarchy.
Organization Policies are specifically designed to set centralized constraints on GCP resources at the Organization, Folder, or Project level.
2
Select the appropriate GCP governance tool
Applying an Organization Policy constraint at the Folder level ensures all current and future child projects inherit the restriction.
Organization Policy constraints take precedence over individual user IAM permissions and restrict resource configurations declaratively.

Anahtar Kavram

Organization Policies and Constraints
Soru 505Soru

An infrastructure engineer needs to provision a managed relational database on Google Cloud for a standard regional web application that requires ACID compliance and automatic high-availability failover. The application does not require global multi-region scaling. Which Google Cloud database service should be provisioned?

Cevabı ve açıklamayı göster

Cevap: Cloud SQL

Cevap

Cloud SQL is the correct database service to provision for a standard regional relational workload requiring high availability.
Cloud SQL is Google Cloud's fully managed relational database service supporting PostgreSQL, MySQL, and SQL Server engines. It supports regional high-availability configurations out of the box, making it the standard choice for regional transactional relational workloads.

Adım Adım Çözüm

1
Identify workload characteristics
Workload requires relational database properties (ACID compliance), regional scope, and managed high availability.
Matching technical requirements to the appropriate managed GCP storage and database service.
2
Evaluate GCP database options
Cloud SQL provides managed PostgreSQL, MySQL, and SQL Server database instances with regional high-availability options.
Cloud SQL fits standard regional database workloads cost-effectively without global overhead.

Anahtar Kavram

Provisioning Cloud SQL for regional relational workloads
Tahmini Süre:45s
Soru 506Soru

A financial data organization is modernizing an API endpoint that receives lightweight HTTP validation requests for market transactions. The workload is entirely stateless, experiences severe traffic fluctuations ranging from zero requests at night to thousands of requests per second during market open, and requires automatic scaling to zero. The lead architect wants to minimize operational overhead by eliminating server management while keeping costs strictly proportional to actual execution time. Which compute platform on Google Cloud best fulfills these requirements?

Cevabı ve açıklamayı göster

Cevap: Deploy the containerized service to Cloud Run.

Cevap

Deploy the containerized application to Cloud Run as it offers full serverless management, rapid automatic scaling from zero, and request-based billing.
Cloud Run is the optimal Google Cloud compute platform for stateless HTTP containers with highly variable traffic patterns. It provides zero infrastructure management, scales automatically from zero to meet demand spikes, and charges only when requests are actively being processed.

Adım Adım Çözüm

1
Analyze workload characteristics
Workload is stateless, receives HTTP traffic, experiences extreme burstiness (scaling to zero), and requires zero infrastructure management.
Identifying container, protocol, scaling behavior, and operational overhead requirements determines the target GCP compute tier.
2
Evaluate serverless container options vs cluster/IaaS options
Cloud Run scales containers automatically based on incoming HTTP requests from 0 to thousands of instances without maintaining cluster endpoints or VM infrastructure.
Cloud Run provides true serverless execution with pay-per-use billing down to 100ms granularity.

Anahtar Kavram

Selecting serverless compute platforms based on workload statefulness and operational overhead constraints.
Tahmini Süre:1m 30s
Soru 507Soru

Arrange the levels of the Google Cloud resource hierarchy in sequence from the highest level (broadest IAM policy inheritance scope) to the lowest level (most specific resource scope).

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

Cevabı ve açıklamayı göster

Cevap

The correct hierarchy from top to bottom is Organization Node, followed by Folder Node, Project Node, and finally Resource Node.
In Google Cloud Platform, IAM policies are inherited downwards through the resource hierarchy structure. The hierarchy starts at the Organization level at the top, flows down through Folder levels, then to Project levels, and ultimately applies to individual Resource instances.

Adım Adım Çözüm

1
Identify the top root entity of GCP governance.
The Organization node represents the root of the structure where organization-wide policies and roles are inherited down.
All policies attached at the organization level propagate down to all child nodes.
2
Identify intermediate administrative groupings.
Folder nodes reside below the Organization node to organize projects into departments or environments.
Folders provide an intermediate level to apply IAM permissions across collections of projects.
3
Identify the primary resource container.
Project nodes sit inside folders or directly under the organization.
Projects contain individual services and form the main boundary for billing and access policies.
4
Identify the target service instance level.
Resource nodes (e.g., Cloud Storage buckets, VM instances) sit at the base of the hierarchy inside projects.
Resources inherit all permissions granted at ancestor levels (project, folder, organization).

Anahtar Kavram

Google Cloud Resource Hierarchy and IAM Inheritance
Tahmini Süre:45s
Soru 508Soru

An network administrator is setting up a hub-and-spoke VPC architecture in Google Cloud. The environment consists of three custom mode VPC networks: `vpc-hub`, `vpc-spoke-1`, and `vpc-spoke-2`. Peering is configured between `vpc-hub` and `vpc-spoke-1`, and between `vpc-hub` and `vpc-spoke-2`. No direct peering exists between `vpc-spoke-1` and `vpc-spoke-2`. Which two statements regarding communication and configuration in this VPC network topology are correct? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Virtual machine instances in `vpc-spoke-1` cannot communicate directly with instances in `vpc-spoke-2` through `vpc-hub` because VPC Network Peering is non-transitive.; Establishing a functional VPC Network Peering connection requires explicit peering configuration setup in both participating VPC networks.

Cevap

VPC Network Peering is non-transitive, meaning traffic cannot traverse an intermediate VPC to reach another peered network. Furthermore, VPC Network Peering connections are bidirectional and must be explicitly configured in both VPC networks for route exchange to function.
VPC Network Peering in Google Cloud is non-transitive by design. If VPC A is peered with VPC B, and VPC B is peered with VPC C, instances in VPC A cannot communicate with instances in VPC C unless a direct peering connection between A and C is established. Additionally, peering configuration is bidirectional: both VPC networks must configure a peering request targeting each other for the connection to become active.

Adım Adım Çözüm

1
Analyze the peering topology
`vpc-spoke-1` is peered to `vpc-hub`, and `vpc-hub` is peered to `vpc-spoke-2`.
Identify the network connection pathways and peering endpoints.
2
Evaluate transitivity in GCP VPC Network Peering
Recognize that GCP VPC Peering routes are not advertised transitively from `vpc-spoke-1` through `vpc-hub` to `vpc-spoke-2`.
Google Cloud VPC Network Peering explicitly restricts transitive routing across intermediate VPC networks.
3
Evaluate VPC Network Peering setup requirements
Confirm that a peering relationship requires creating peering connections from both network sides.
Peering is bidirectional and remains in an inactive state until both sides approve and configure the connection.

Anahtar Kavram

VPC Network Peering Non-Transitivity and Bidirectional Setup
Soru 509Soru

A global healthcare technology company is deploying a HIPAA-compliant patient monitoring platform on Google Cloud. As the principal cloud architect, you must provision private Google Kubernetes Engine (GKE) clusters using Terraform in a shared Virtual Private Cloud (VPC) environment, ensuring strict control plane isolation, least-privilege automation, and reliable IaC state management. Which THREE architectural configurations and deployment practices should you implement to satisfy these security and operational requirements?

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

Cevabı ve açıklamayı göster

Cevap: Enable Control Plane Authorized Networks on the GKE private cluster and restrict access to the CIDR blocks of your management bastion hosts and CI/CD runners.; Store the Terraform state in a Cloud Storage backend configured with Object Versioning and state locking enabled via a remote backend configuration.; Grant the deployment pipeline service account the Service Account User role (roles/iam.serviceAccountUser) on the dedicated GKE node service account.

Cevap

The correct implementation requires securing the GKE master endpoint with Control Plane Authorized Networks, using Cloud Storage with versioning and state locking for Terraform state management, and granting the Service Account User role to the CI/CD pipeline service account.
Securing a private GKE cluster deployment with Terraform demands three core architectural controls: restricting control plane administrative access via Control Plane Authorized Networks, configuring centralized Terraform state management in Cloud Storage with locking and versioning enabled, and delegating service account usage rights to CI/CD pipelines via the dedicated Service Account User role instead of elevated admin or primitive roles.

Adım Adım Çözüm

1
Configure GKE control plane security bounds
Control Plane Authorized Networks limits master endpoint reachability to explicitly listed internal or management IP addresses.
Prevents unauthorized administrative access to the Kubernetes control plane endpoint.
2
Implement secure IaC state management
Terraform backend uses Cloud Storage with object versioning and state locking.
Ensures concurrent deployment safety and disaster recovery capability for infrastructure state.
3
Apply least-privilege IAM permissions for pipeline execution
The deployment service account receives roles/iam.serviceAccountUser to impersonate and assign node service accounts.
Adheres to enterprise compliance by withholding broad Service Account Admin or primitive project roles.

Anahtar Kavram

Provisioning secure GKE private clusters using Infrastructure as Code (Terraform) requires enforcing control plane authorized networks, centralized remote state locking, and least-privilege IAM role assignments for deployment service accounts.
Soru 510Soru

A global supply chain organization is architecting a new containerized route-optimization service on Google Cloud. The service receives stateless HTTP requests from mobile dispatch devices, executes short-lived algorithms requiring less than 15 seconds per request, experiences dramatic traffic fluctuations ranging from 0 to over 50,000 requests per minute during peak operational hours, and must scale down to zero during inactive periods to minimize costs. The organization enforces strict security policies prohibiting unmanaged server infrastructure, and the devops team aims to eliminate Kubernetes control plane management overhead while ensuring minimal cost for idle resources. Which compute platform design should you recommend?

Cevabı ve açıklamayı göster

Cevap: Deploy the containerized service to Cloud Run, configuring container concurrency and scaling limits to automatically scale instances down to zero when idle.

Cevap

Deploy the containerized service to Cloud Run with automatic scaling down to zero when idle.
Cloud Run is the optimal Google Cloud platform for containerized, stateless HTTP workloads with bursty request patterns. It abstracts away all server infrastructure and cluster management while providing seamless automatic scaling from zero to tens of thousands of requests per minute, charging strictly for resources consumed during request execution.

Adım Adım Çözüm

1
Analyze workload characteristics and constraints
The application is stateless, containerized, handles short-lived HTTP requests (<15 seconds), experiences extreme traffic bursts (0 to 50,000 requests/min), and requires scaling to zero.
Identifying statefulness, protocol, latency, and scaling requirements dictates the optimal compute platform selection.
2
Evaluate Google Cloud compute platform options against operational overhead limits
Cloud Run handles arbitrary containers via stateless HTTP, provides automated scaling to zero, charges per millisecond of execution, and requires zero control plane management.
Eliminating server and cluster management aligns directly with the requirement to minimize DevOps operational overhead.
3
Compare against Kubernetes and VM-based alternatives
GKE Standard introduces master node management overhead and static node costs. Compute Engine MIGs cannot scale to true zero efficiently and incur baseline OS maintenance.
Selecting GKE or Compute Engine MIGs represents compute misallocation for stateless bursty microservices.

Anahtar Kavram

Selecting Serverless Container Compute Platforms based on Workload Characteristics
Soru 511Soru

An enterprise cloud engineering team is establishing design documentation standards for new Google Cloud solutions. The lead architect requires team members to clearly differentiate between conceptual, logical, and physical architectural representations during the design phase. Which of the following best describes the core responsibility of a logical architecture in this framework?

Cevabı ve açıklamayı göster

Cevap: Defining technology-agnostic functional components, service boundaries, and data flows required to satisfy business capabilities.

Cevap

The core responsibility of a logical architecture is to define technology-agnostic functional components, service boundaries, and data flows required to satisfy business capabilities.
The correct answer accurately characterizes a logical architecture: it structures system functionality, service boundaries, and data flow patterns without tying the design to specific provider hardware or managed cloud products.

Adım Adım Çözüm

1
Identify the role of each architectural abstraction layer in cloud solution design.
Conceptual architectures focus on high-level business goals; logical architectures define functional tiers and relationships; physical architectures specify concrete GCP services and infrastructure resources.
Clear layer separation ensures business requirements map cleanly into technology design before committing to specific cloud provider services.
2
Evaluate the option defining technology-agnostic functional tiers.
This correctly captures the logical architecture's scope by focusing on WHAT functions are needed and HOW they interact, without tying them to specific product implementations.
Logical architectures provide the bridge between abstract business needs and physical cloud resource choices.

Anahtar Kavram

Separation of Conceptual, Logical, and Physical Architecture Views
Soru 512Soru

A cloud architect needs to provision a new relational database using Cloud SQL with Customer-Managed Encryption Keys (CMEK) enabled. What is the correct chronological sequence of steps required to successfully provision this encrypted database infrastructure?

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

Cevabı ve açıklamayı göster

Cevap

The correct sequence begins with creating the Cloud KMS Key Ring and CryptoKey, followed by granting the Cloud SQL Service Agent the required Encrypter/Decrypter role on that key, then provisioning the Cloud SQL instance referencing the CMEK, and finally creating the logical database inside the instance.
Provisioning CMEK-encrypted managed services on Google Cloud requires creating the encryption key first, delegating `roles/cloudkms.cryptoKeyEncrypterDecrypter` to the Cloud SQL service account second, provisioning the encrypted instance third, and finally creating the logical database.

Adım Adım Çözüm

1
Create the Cloud KMS key resource
A regional Cloud KMS Key Ring and CryptoKey are available.
Encryption keys must exist before permissions can be assigned or services configured to use them.
2
Assign IAM roles to the service account
The Cloud SQL service agent is authorized to use the KMS key.
Provisioning will fail if the Cloud SQL service account cannot access the key during instance creation.
3
Provision the Cloud SQL database instance
An encrypted Cloud SQL instance is running.
The underlying disk storage is encrypted using the specified CMEK during initial instance creation.
4
Create the application database
The target relational database is ready for data ingestion.
Logical database structures exist on top of the already provisioned and encrypted storage instance.

Anahtar Kavram

Customer-Managed Encryption Key (CMEK) Provisioning Sequence for Managed Storage and Databases
Soru 513Soru

An enterprise e-commerce platform is refactoring its data storage architecture on Google Cloud to support a global expansion across North America and Europe. The new architecture must satisfy two distinct workload requirements:

1. A core transactional order-processing database requiring relational schema support, multi-region active-active write capabilities across continents, sub-10 millisecond latencies, and strict global ACID compliance.
2. A centralized audit logging repository requiring tamper-proof, immutable WORM (write once, read many) storage to satisfy strict regulatory compliance rules for 7 years.

Which TWO architecture decisions should you include in your storage and database design to satisfy these requirements? (Select TWO answers.)

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

Cevabı ve açıklamayı göster

Cevap: Provision a multi-region Cloud Spanner instance configuration to host the transactional order-processing database.; Configure Cloud Storage buckets with a Retention Policy and enforce Bucket Lock for storing immutable audit logs.

Cevap

Selecting a multi-region Cloud Spanner instance for globally distributed relational ACID transactions and configuring Cloud Storage buckets with locked Retention Policies (Bucket Lock) for immutable WORM compliance logging.
Provisioning Cloud Spanner with a multi-region configuration provides horizontally scalable relational storage capable of executing active-active transactional writes across global regions while guaranteeing external consistency (ACID). Furthermore, implementing a Cloud Storage Retention Policy with Bucket Lock guarantees WORM compliance by permanently preventing object modification or deletion prior to retention expiry.

Adım Adım Çözüm

1
Analyze database requirements for the transactional order-processing engine.
Identified the need for relational schema, multi-region active-active writes, and global ACID consistency.
Cloud SQL only supports single-region primary nodes with cross-region read replicas, whereas Cloud Spanner is designed specifically for globally distributed relational transactions with multi-region write availability.
2
Analyze compliance storage requirements for raw audit logs.
Identified the need for long-term immutable object storage enforcing WORM compliance.
Cloud Storage Bucket Lock locks a bucket retention policy so that no user, including project owners and administrators, can delete or overwrite objects until the retention timer expires.

Anahtar Kavram

Selecting Cloud Spanner for global multi-region relational ACID workloads and Cloud Storage Bucket Lock for WORM compliance.
Soru 514Soru

A enterprise security team is implementing governance guardrails across a multitenant Google Cloud environment. They plan to restrict the activation of unauthorized service APIs using the `constraints/gcp.restrictServiceUsage` Organization Policy. However, to avoid disrupting existing workloads currently undergoing active development, the team wants to monitor potential violations in real time and evaluate the impact of the policy without blocking resource creation. Which configuration approach meets these requirements?

Cevabı ve açıklamayı göster

Cevap: Configure the Organization Policy constraint using a dry-run policy specification at the target resource hierarchy node.

Cevap

Configure the Organization Policy constraint using a dry-run policy specification at the target resource hierarchy node.
Configuring a dry-run policy specification allows administrators to simulate and log compliance violations without blocking deployment operations. Non-compliant API activations generate audit logs, giving visibility into compliance readiness before enforcing the constraint strictly.

Adım Adım Çözüm

1
Identify the requirement to test policy impact without enforcement
Recognize that blocking actions directly in a live environment risks breaking operational workloads.
Organization Policies support dry-run specifications specifically for auditing potential policy violations prior to enforcement.
2
Evaluate Google Cloud Organization Policy capabilities
Dry-run specifications evaluate requests against proposed policy rules and write violation audit logs to Cloud Logging while allowing the API call to proceed.
This provides real-time visibility into non-compliant activity across folders or projects without breaking existing application pipelines.

Anahtar Kavram

Organization Policy Dry-Run Mode and Audit Logging
Soru 515Soru

A financial services organization is establishing an automated deployment framework using Terraform to manage core Google Cloud infrastructure across multiple enterprise projects. To ensure environment stability, state integrity, and adherence to security best practices, the security team requires that the pipeline prevents concurrent modifications, maintains state history, and operates under least privilege. Which combination of actions should the architecture team implement?

Cevabı ve açıklamayı göster

Cevap: Configure a Cloud Storage remote backend with object versioning and state locking enabled, and assign the pipeline service account fine-grained predefined roles along with the Service Account User role on required resource service accounts.

Cevap

Configure a Cloud Storage remote backend with object versioning and state locking enabled, and assign the pipeline service account fine-grained predefined roles along with the Service Account User role on required resource service accounts.
The correct architecture uses Google Cloud Storage as a remote Terraform backend with versioning and object locking to protect infrastructure state consistency across continuous deployment runs. Concurrently, security best practices dictate using minimal predefined IAM roles and assigning roles/iam.serviceAccountUser when resources need to be provisioned with attached service accounts.

Adım Adım Çözüm

1
Establish secure Terraform remote state storage
Configured a Google Cloud Storage bucket backend with object versioning enabled to preserve state history and state locking enabled via GCP native object lock mechanisms to prevent concurrent state modifications.
Centralized remote state management in Cloud Storage ensures consistency, multi-user safety, and disaster recovery capabilities for IaC workflows.
2
Apply identity and access control best practices to the deployment pipeline
Granted specific, fine-grained predefined IAM roles to the pipeline service account along with roles/iam.serviceAccountUser where resource impersonation/attachment is required.
Avoids over-privilege (such as Owner or Service Account Admin) while ensuring the pipeline has exact permissions required to provision components.

Anahtar Kavram

Terraform Cloud Storage Remote Backend State Locking and IAM Least Privilege
Soru 516Soru

A financial data organization is setting up an automated pipeline to provision a cluster of custom Compute Engine virtual machines in the us-east4 region for nightly risk calculation workloads. During the initial deployment execution, the orchestration system fails immediately with a quota constraint error regarding N2_CPUS before any instances can be created. Which action should the Cloud Architect take to resolve this provisioning failure?

Cevabı ve açıklamayı göster

Cevap: Submit a request to increase the regional N2_CPUS quota for the us-east4 region via the Google Cloud Console before running the deployment.

Cevap

Submit a request to increase the regional N2_CPUS quota for the us-east4 region via the Google Cloud Console before running the deployment.
Compute Engine enforces quota limits on CPU cores per region and machine family. When a planned deployment exceeds the available quota, the architect must proactively request a quota increase for that specific region and resource type prior to launching the compute resources.

Adım Adım Çözüm

1
Identify the cause of the failure
The failure occurred due to an exceeded regional N2_CPUS quota in us-east4 during instance creation.
Compute Engine enforces per-region and per-machine-family quotas to prevent unexpected resource allocation.
2
Determine the appropriate remediation path
Request a regional quota increase for N2 vCPUs in us-east4 through the Quotas page in the Google Cloud Console.
Quotas cannot be bypassed using IAM roles or workload platform wrappers like GKE.

Anahtar Kavram

Compute Engine Regional Resource Quotas
Soru 517Soru

An enterprise cloud architecture team is implementing governance controls for a newly acquired business unit organized under a dedicated Google Cloud folder. The compliance mandate requires that all resource creation be strictly limited to specified approved regions (`us-central1` and `us-east4`). To prevent operational disruptions to ongoing automated deployments, the security team needs to evaluate existing infrastructure and incoming requests for non-compliance without actively blocking deployments during the initial phase. Which TWO actions should the cloud architect take to satisfy these requirements?

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

Cevabı ve açıklamayı göster

Cevap: Configure an Organization Policy at the target folder level using the `constraints/gcp.resourceLocations` list constraint with allowed values set to the approved regions, and enable dry-run mode.; Monitor Cloud Audit Logs for dry-run Organization Policy violation events to audit non-compliant resource creation attempts before changing the policy enforcement mode to active denial.

Cevap

The cloud architect should set the list constraint `constraints/gcp.resourceLocations` in dry-run mode at the folder level and analyze Cloud Audit Logs for dry-run policy violations before enforcing strict denial.
To restrict resource deployment locations across a folder hierarchy without disrupting live operations, Google Cloud recommends using the `constraints/gcp.resourceLocations` list constraint in dry-run mode. This approach logs violations to Cloud Audit Logs so administrators can identify non-compliant workloads before enforcing active denial.

Adım Adım Çözüm

1
Identify the appropriate policy constraint and scope for location restrictions.
Selected `constraints/gcp.resourceLocations` applied at the designated folder level.
Organization Policy list constraints dictate allowed physical deployment locations for GCP resources across all projects inherited under a specific folder.
2
Enable non-disruptive testing mode for the Organization Policy.
Policy configured with dry-run enforcement mode.
Dry-run mode evaluates incoming deployment requests against the policy without blocking execution, allowing pipelines to remain active while gathering compliance telemetry.
3
Establish visibility into compliance violations.
Audited policy violation entries via Cloud Audit Logs.
When dry-run mode is enabled, violations generate audit log entries that allow security teams to inspect non-compliant workloads and prepare remediation plans before enforcing hard restrictions.

Anahtar Kavram

Organization Policy List Constraints and Dry-Run Enforcement
Soru 518Soru

A multinational enterprise manages a multi-tier Google Cloud resource hierarchy containing active production workloads across several folders. To comply with new data sovereignty regulations, the security team must restrict all future resource deployments to specified US regions (`in:us-locations`). They need to identify existing non-compliant resources across all projects without disrupting running workloads or blocking active CI/CD deployments during a 30-day evaluation period. Furthermore, once evaluation completes, the restriction must be globally enforced across the entire organization hierarchy while preventing project owners from overriding the constraint. Which Google Cloud strategy achieves these governance objectives?

Cevabı ve açıklamayı göster

Cevap: Configure an Organization Policy at the organization root using the `gcp.resourceLocations` constraint configured in dry-run mode. Monitor compliance violations in Cloud Audit Logs during the evaluation period, and then update the policy enforcement state to active across the organization root.

Cevap

Configure an Organization Policy using the `gcp.resourceLocations` constraint in dry-run mode at the organization root, audit violations via Cloud Audit Logs, and subsequently switch the policy to active enforcement.
The correct strategy uses Google Cloud Organization Policies with the `gcp.resourceLocations` constraint set to dry-run mode. Dry-run enforcement allows administrators to audit and evaluate potential policy violations via Cloud Audit Logs without blocking active operations or breaking CI/CD pipelines. Once the audit period concludes, enabling active enforcement at the organization root enforces strict compliance across all child folders and projects through hierarchical inheritance.

Adım Adım Çözüm

1
Identify the governance requirement and select the appropriate constraint.
The `gcp.resourceLocations` list constraint centralized at the organization root restricts regional creation of supported GCP resources.
Organization Policies provide centralized, policy-driven control over cloud resources across the entire resource hierarchy.
2
Apply the policy in dry-run mode across the organization root.
Deployment requests that violate `in:us-locations` write audit log entries but are allowed to succeed without breaking production pipelines or existing infrastructure.
Dry-run policy evaluation enables risk-free compliance testing and auditing across active environments.
3
Transition from dry-run to enforced status after the 30-day evaluation window.
The constraint actively prevents any new non-US resource creation across all child folders and projects, overriding any project-level configurations.
Hierarchical inheritance ensures root-level enforcement applies universally unless explicit allowed overrides exist.

Anahtar Kavram

Organization Policy dry-run mode and resource location constraints
Soru 519Soru

An enterprise SaaS platform is provisioning a private Google Kubernetes Engine (GKE) cluster to execute secure background analytics workloads. Organization security policy mandates that worker nodes must not be assigned public IP addresses and that management access to the GKE control plane must be strictly restricted to an internal management subnet (10.200.0.0/24). During automated deployment, node provisioning completes successfully, but administrators report that kubectl commands issued from bastion hosts within 10.200.0.0/24 are blocked when reaching the control plane. Additionally, the CI/CD pipeline service account used for deployment has been granted roles/iam.serviceAccountAdmin to allow compute instances to attach to custom service accounts. Which combination of architectural modifications should you recommend to resolve the control plane connectivity failure while enforcing least privilege IAM access?

Cevabı ve açıklamayı göster

Cevap: Enable Control Plane Authorized Networks on the GKE cluster, adding 10.200.0.0/24 to the allowed IP ranges, and replace roles/iam.serviceAccountAdmin on the deployment service account with roles/iam.serviceAccountUser targeting the node service account.

Cevap

Enable Control Plane Authorized Networks on the GKE cluster specifying 10.200.0.0/24, and grant roles/iam.serviceAccountUser to the deployment pipeline service account.
Enabling Control Plane Authorized Networks with the management subnet CIDR 10.200.0.0/24 allows management traffic from internal bastion hosts to reach the private GKE control plane API endpoint. Replacing the Service Account Admin role with the Service Account User role enforces the principle of least privilege, providing the deployment pipeline with the necessary permission to attach the node service account without granting full IAM management rights.

Adım Adım Çözüm

1
Identify the cause of control plane access blocking on a private GKE cluster
Recognize that private GKE clusters block master endpoint access by default unless authorized network CIDR ranges are explicitly configured.
Control Plane Authorized Networks allows specific CIDRs (such as 10.200.0.0/24) to reach the Kubernetes API master endpoint.
2
Evaluate IAM permissions required for service account attachment during compute provisioning
Determine that roles/iam.serviceAccountUser is the exact minimal permission required for a provisioning identity to attach a target service account to compute instances or node pools.
Granting roles/iam.serviceAccountAdmin provides excessive administrative capabilities over service account keys and IAM policies.

Anahtar Kavram

Private GKE Cluster Endpoint Security and Service Account IAM Privilege Boundaries
Tahmini Süre:2m 0s
Soru 520Soru

An enterprise platform engineering team is establishing an automated pipeline to deploy a private Google Kubernetes Engine (GKE) cluster and a fleet of Compute Engine virtual machines in a designated Virtual Private Cloud (VPC). The security compliance policy dictates two requirements: administrative traffic to the GKE control plane must be restricted strictly to specified internal subnet IP ranges, and the CI/CD pipeline's service account must be allowed to configure compute resources to run under dedicated workload service accounts without granting administrative control over those service accounts. Which two configuration actions should you implement to meet these requirements? (Select TWO)

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 add the internal management subnet CIDR blocks to the authorized list.; Grant the deployment pipeline service account the Service Account User role (roles/iam.serviceAccountUser) on the target workload service accounts.

Cevap

To enforce control plane network boundaries and follow least privilege for deployment accounts, enable Control Plane Authorized Networks on the private GKE cluster with internal CIDR ranges and grant the CI/CD service account the Service Account User role on the workload service accounts.
The solution requires configuring network security and IAM authorization according to GCP best practices. Enabling Control Plane Authorized Networks restricts cluster API master endpoint access to explicit internal subnet ranges. Concurrently, granting the Service Account User role (roles/iam.serviceAccountUser) allows the deployment service account to attach workload identities to provisioned compute resources while adhering strictly to the principle of least privilege.

Adım Adım Çözüm

1
Configure network access controls for the GKE cluster control plane endpoint.
Control Plane Authorized Networks limits master endpoint access exclusively to specified internal management subnet CIDRs.
Preventing unauthorized network ingress to the cluster master endpoint requires network-level access control via authorized network settings.
2
Assign IAM roles for service account usage to the deployment pipeline account.
Granting roles/iam.serviceAccountUser allows the pipeline to attach service accounts to VMs and GKE node pools without granting permissions to manage service account keys or policies.
This satisfies least privilege by separating service account administration from service account usage.

Anahtar Kavram

Provisioning private GKE clusters with control plane authorized networks and least-privilege IAM service account usage controls.
ÖncekiSayfa 26 / 80Sonraki
Tüm alıştırma soruları — Google Cloud Professional Cloud Architect | Examkin