Tüm alıştırma soruları

1591 soru

Soru 301Soru

An enterprise architecture team is configuring a custom-mode Virtual Private Cloud (VPC) network in Google Cloud. The primary subnet in `us-east4` is currently assigned the IPv4 CIDR block 10.240.0.0/2210.240.0.0/22. The team plans to deploy a Google Kubernetes Engine (GKE) cluster in this subnet and must define a secondary IPv4 CIDR range for Pod IP address allocation. Furthermore, long-term capacity requirements mandate that the primary subnet range must be expandable to 10.240.0.0/2010.240.0.0/20 in the future without recreating the subnet, modifying existing secondary ranges, or creating IP range overlaps. Which secondary IPv4 CIDR range should be assigned to the Pods to satisfy all requirements?

Cevabı ve açıklamayı göster

Cevap: 10.240.16.0/2110.240.16.0/21

Cevap

Assigning the secondary Pod range to 10.240.16.0/2110.240.16.0/21 ensures that the primary IP range can be seamlessly expanded to 10.240.0.0/2010.240.0.0/20 without IP overlap.
The range 10.240.16.0/2110.240.16.0/21 spans from 10.240.16.010.240.16.0 to 10.240.23.25510.240.23.255. Because expanding the primary subnet from 10.240.0.0/2210.240.0.0/22 to 10.240.0.0/2010.240.0.0/20 encompasses the IP span from 10.240.0.010.240.0.0 to 10.240.15.25510.240.15.255, placing the secondary range at 10.240.16.0/2110.240.16.0/21 leaves the entire 10.240.0.0/2010.240.0.0/20 block unobstructed for future expansion.

Adım Adım Çözüm

1
Calculate the IP range boundaries for the target expanded primary subnet.
Expanding 10.240.0.0/2210.240.0.0/22 to 10.240.0.0/2010.240.0.0/20 requires a contiguous block spanning from 10.240.0.010.240.0.0 to 10.240.15.25510.240.15.255.
GCP subnet primary expansion requires lowering the prefix length (e.g., /22 to /20) while maintaining the original network address alignment.
2
Evaluate secondary IP range constraints against GCP VPC networking rules.
A subnet's secondary IP ranges cannot overlap with its own primary IP range, nor can they overlap with any future space reserved for primary IP range expansion.
If a secondary IP range exists within 10.240.0.0/2010.240.0.0/20, GCP will reject any subsequent request to expand the primary range into that overlapping space.
3
Identify the CIDR block located entirely outside the expanded 10.240.0.0/2010.240.0.0/20 space.
The range 10.240.16.0/2110.240.16.0/21 covers 10.240.16.010.240.16.0 to 10.240.23.25510.240.23.255, which starts immediately after 10.240.15.25510.240.15.255 and provides zero overlap.
This guarantees that both current operations and future primary CIDR expansion can proceed without modifying or recreating the secondary range.

Anahtar Kavram

VPC Subnet Primary Expansion and Secondary IP Range Non-Overlap Rules
Soru 302Soru

Match each Google Cloud storage option or persistent disk type to its primary architectural capability and ideal workload scenario.

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

Öğeler

Cloud Spanner
Cloud Bigtable
Local SSD
Balanced Persistent Disk (pd-balanced)

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

Cloud Spanner pairs with the global relational database capability; Cloud Bigtable pairs with the petabyte-scale NoSQL capability; Local SSD pairs with the high-performance host-attached ephemeral block storage; and Balanced Persistent Disk pairs with the cost-effective network block storage option.
Each service targets distinct operational constraints: Cloud Spanner supports globally scalable relational transactions; Cloud Bigtable handles massive NoSQL telemetry and time-series throughput; Local SSD provides maximum IOPS with host-bound ephemerality; and Balanced Persistent Disk offers durable network block storage optimized for cost-performance balance.

Adım Adım Çözüm

1
Identify relational database requirements requiring global consistency
Matched Cloud Spanner to global relational database with strong ACID consistency.
Cloud Spanner is uniquely engineered to scale relationally across regions without sacrificing ACID consistency.
2
Identify massive-scale NoSQL key-value and time-series requirements
Matched Cloud Bigtable to petabyte-scale NoSQL low-latency workloads.
Cloud Bigtable handles high-throughput key-value write/read operations required by time-series data.
3
Differentiate persistent network block storage from ephemeral host-attached block storage
Matched Local SSD to non-persistent host-attached storage and pd-balanced to persistent network storage.
Local SSD is physically bound to the host hypervisor and loses data on VM stop, whereas persistent disks are network-attached and retain data.

Anahtar Kavram

GCP Database & Block Storage Selection Criteria
Tahmini Süre:1m 30s
Soru 303Soru

An enterprise analytics team is designing the infrastructure for a memory-intensive transactional database on Google Compute Engine. Benchmarking indicates the database requires 416 GB416\text{ GB} of RAM and 32 vCPUs32\text{ vCPUs}. The database is strictly stateful, operates 24/7 with zero tolerance for ungraceful instance terminations, and is projected to run continuously for at least three years. Which machine family and purchasing model configuration should the cloud engineer select to meet these operational and financial requirements?

Cevabı ve açıklamayı göster

Cevap: Provision an m1-ultramem-32 memory-optimized Compute Engine instance attached to a 3-year Committed Use Discount (CUD).

Cevap

Provisioning an m1-ultramem-32 memory-optimized Compute Engine instance with a 3-year Committed Use Discount (CUD) is the correct choice.
The Memory-Optimized machine family (M1/M2/M3) is engineered specifically for memory-intensive workloads such as large in-memory databases like SAP HANA or Redis clusters requiring high RAM-to-vCPU ratios. Combined with a 3-year Committed Use Discount (CUD), this configuration guarantees dedicated baseline availability without preemption risks while achieving maximum cost efficiency for a continuous multi-year deployment.

Adım Adım Çözüm

1
Analyze workload resource requirements and select machine family.
The requirement calls for 416 GB RAM with 32 vCPUs (a ratio of 13 GB RAM per vCPU). Memory-optimized families (M1/M2/M3) offer up to 28 GB RAM per vCPU, ideal for large memory-bound databases.
General-purpose or compute-optimized machine types do not provide adequate memory density for 416 GB RAM without over-provisioning CPU cores.
2
Evaluate fault tolerance and availability constraints.
The workload is stateful and requires zero ungraceful terminations, ruling out Spot/Preemptible VMs.
Spot instances can be revoked at any time when compute capacity is needed elsewhere.
3
Determine the optimal pricing strategy for a 3-year continuous runtime.
Select a 3-year Committed Use Discount (CUD) for Compute Engine vCPUs and memory.
Committed Use Discounts offer the highest savings (up to 57% or 70% depending on resource type) for baseline, steady-state workloads running continuously over 1 or 3 years.

Anahtar Kavram

Selecting Compute Engine Machine Types and Purchasing Models for Memory-Bound Workloads
Soru 304Soru

A software architecture team is planning a serverless deployment on Google Cloud for a microservice that runs a third-party C++ binary packaged inside a custom Docker container. The service receives incoming HTTP webhooks and must handle multiple concurrent requests per container instance to maximize resource efficiency and reduce operational costs. Which compute platform should the team select?

Cevabı ve açıklamayı göster

Cevap: Cloud Run, because it supports custom container images and permits handling multiple concurrent requests per container instance.

Cevap

Cloud Run should be selected because it supports custom container images and permits handling multiple concurrent requests per container instance.
Cloud Run is a fully managed serverless platform that enables running stateless HTTP containers built from any language or binary. Crucially, Cloud Run allows configuring instance concurrency, allowing a single container instance to process multiple requests simultaneously to minimize cold starts and optimize cost.

Adım Adım Çözüm

1
Analyze workload requirements
Workload requires running a custom Docker container with a third-party binary and serving multiple concurrent HTTP requests per instance.
Evaluating operational constraints determines which serverless platform matches the execution profile.
2
Compare serverless compute capabilities on Google Cloud
Cloud Run natively supports custom OCI container images and configurable request concurrency per instance (up to 1000 requests per instance). Cloud Functions is designed primarily for code snippets with source-based deployment.
Selecting between Cloud Run and Cloud Functions depends on whether custom containerization and instance concurrency are key architectural constraints.
3
Select the optimal serverless option
Cloud Run satisfies both custom container image support and request concurrency requirements.
Cloud Run provides serverless scaling to zero while efficiently packing concurrent requests into container instances.

Anahtar Kavram

Selecting Serverless Compute Platforms (Cloud Run vs. Cloud Functions)
Soru 305Soru

A data analyst needs read-only access to view tables and execute queries within existing BigQuery datasets in a Google Cloud project, without the ability to modify table data or create new datasets. Following Google Cloud security best practices for least privilege, which IAM role should you grant to the analyst?

Cevabı ve açıklamayı göster

Cevap: BigQuery Data Viewer (roles/bigquery.dataViewer)

Cevap

BigQuery Data Viewer (roles/bigquery.dataViewer)
The BigQuery Data Viewer role (roles/bigquery.dataViewer) grants permissions to view dataset contents, tables, and run queries without permitting users to alter data, create datasets, or manage permissions, strictly satisfying the principle of least privilege.

Adım Adım Çözüm

1
Identify the required permissions
The user needs read-only access to view data and execute queries in BigQuery without modification rights.
Security best practices demand assigning the minimum necessary permissions to fulfill the role.
2
Evaluate role options against least privilege principles
BigQuery Data Viewer provides read access to dataset contents, whereas BigQuery Data Editor, Editor, and Owner grant excess write or administrative privileges.
Predefined fine-grained roles should always be preferred over broader predefined or primitive roles.

Anahtar Kavram

Principle of Least Privilege using Predefined IAM Roles
Soru 306Soru

An engineer is planning the initial virtual private cloud (VPC) topology for an enterprise workload in Google Cloud. Which two statements accurately describe Google Cloud VPC networks and subnets? (Select TWO answers.)

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

Cevabı ve açıklamayı göster

Cevap: VPC networks are global resources, whereas subnets are regional resources.; Custom mode VPC networks allow administrators to manually define IP address ranges for subnets in chosen regions.

Cevap

Google Cloud VPC networks are global resources containing regional subnets, and custom mode VPC networks allow administrators to explicitly define IP address ranges for subnets in selected regions.
Google Cloud VPC networks are global resources capable of hosting resources across multiple regions, whereas subnets belong to specific regions. Furthermore, custom mode VPC networks give cloud engineers explicit administrative control to create subnets with specific IP address ranges only in required regions.

Adım Adım Çözüm

1
Evaluate the architectural scope of VPC networks and subnets in Google Cloud.
Recognize that VPC networks are global entities that span across regions, while subnets are regional objects bound to a specific GCP region.
Understanding resource scope is fundamental when planning network topology and regional resource placement.
2
Analyze the operational differences between custom mode and auto mode VPC networks.
Determine that custom mode VPCs provide complete control over subnet creation, IP CIDR allocation, and regional placement.
Enterprise networks generally utilize custom mode VPCs to prevent IP space overlap with existing on-premises or peered networks.

Anahtar Kavram

Planning Virtual Private Cloud (VPC) Networks and Subnets
Soru 307Soru

A cloud administrator needs to delegate authority to a junior engineer to link an unlinked Google Cloud project to an organization's Cloud Billing Account using least-privilege IAM roles. Arrange the steps in the correct chronological order required to grant permissions and complete the linking process.

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

Cevabı ve açıklamayı göster

Cevap

The correct sequence begins by identifying the Project ID and Billing Account ID, granting the Billing Account User role on the billing account, granting the Project Billing Manager role on the project, and executing the gcloud billing projects link command.
Linking a project to a billing account requires permissions on two distinct levels in the GCP resource hierarchy: `roles/billing.user` on the Cloud Billing Account and `roles/resourcemanager.projectBillingManager` on the target Project. The workflow proceeds chronologically from identifying resource parameters to granting necessary IAM roles on both scopes, concluding with the CLI invocation to link the project.

Adım Adım Çözüm

1
Identify resource parameters
Obtain target Project ID and Cloud Billing Account ID.
Target identifiers are required parameters for granting scoped IAM roles and running gcloud commands.
2
Configure billing account level IAM
Assign `roles/billing.user` to the user on the Cloud Billing Account.
Linking requires permission to use the billing account without granting administrative access over billing settings.
3
Configure project level IAM
Assign `roles/resourcemanager.projectBillingManager` to the user on the target project.
Linking requires permission on the target project to change its billing configuration under least privilege.
4
Execute project linking
Run `gcloud billing projects link` using the engineer's authenticated session.
The CLI operation succeeds because the identity holds required privileges across both resource boundaries.

Anahtar Kavram

Least privilege IAM delegation for project billing link configuration
Soru 308Soru

A lead cloud engineer at a financial firm is preparing to launch a risk-modeling batch processing cluster in project `risk-analytics-prod`. The workload requires provisioning 128 N2 CPUs in the `us-west1` region, but deployment fails because the project's current regional limit is 32 N2 CPUs. The engineer must request an adjustment to accommodate the workload using the principle of least privilege. Which action should be taken to request the required capacity increase?

Cevabı ve açıklamayı göster

Cevap: Grant the engineer the Quota Administrator role (`roles/servicemanagement.quotaAdmin`) on the project, and submit a quota increase request from the Quotas & System Limits page in the Cloud Console.

Cevap

Grant the engineer the Quota Administrator role (`roles/servicemanagement.quotaAdmin`) on the project, and submit a quota increase request from the Quotas & System Limits page in the Cloud Console.
The correct solution uses the principle of least privilege by granting the Quota Administrator role (`roles/servicemanagement.quotaAdmin`), which enables the engineer to view and request quota increases directly through the Quotas & System Limits interface in the Google Cloud Console.

Adım Adım Çözüm

1
Identify the required administrative role for quota management.
Following the principle of least privilege, `roles/servicemanagement.quotaAdmin` provides the necessary permissions to view and request quota changes without granting full project ownership.
Primitive roles like Owner grant excessive privileges, while specific quota administrative permissions allow quota adjustment requests.
2
Navigate to the GCP resource management console interface.
Access the IAM & Admin > Quotas & System Limits section in the Google Cloud Console.
GCP resource quotas (such as Compute Engine N2 CPUs in `us-west1`) are monitored and requested via the Quotas interface.
3
Submit the regional CPU quota adjustment request.
Select the N2 CPUs metric for `us-west1` and submit a quota edit request with business justification for evaluation by Google Cloud.
GCP reviews and approves quota increase requests based on project usage, payment history, and resource availability.

Anahtar Kavram

GCP Resource Quota Management and IAM Quota Administrator Role
Soru 309Soru

A system administrator needs to deploy a fully managed relational database on Google Cloud to support an existing web application that uses a standard MySQL engine. Which Google Cloud database service best satisfies this requirement with minimal operational overhead?

Cevabı ve açıklamayı göster

Cevap: Cloud SQL

Cevap

Cloud SQL is the recommended service because it provides fully managed relational database instances running native MySQL.
Cloud SQL is Google Cloud's fully managed relational database service that directly supports standard MySQL, PostgreSQL, and SQL Server engines with automated backups, replication, and patching.

Adım Adım Çözüm

1
Identify the data model and engine requirements
The workload requires a relational database model with standard MySQL engine compatibility.
Matching workload database requirements to Google Cloud offerings is key to selecting the proper managed service.
2
Evaluate Google Cloud database options against relational database support
Cloud SQL natively supports MySQL, PostgreSQL, and SQL Server as fully managed services.
NoSQL services like Firestore and Bigtable do not support standard SQL engines or relational schemas.

Anahtar Kavram

Selecting managed relational database services in GCP based on engine requirements
Tahmini Süre:45s
Soru 310Soru

An organization is designing a Google Cloud networking architecture for a enterprise system requiring workload deployment across two distinct regions: `us-central1` and `europe-west1`. Compute instances in both regions must communicate securely with each other using internal private IP addresses over Google's global network backbone. Which VPC network and subnet design strategy should the cloud engineer implement?

Cevabı ve açıklamayı göster

Cevap: Create a single custom-mode VPC network with individual subnets created in `us-central1` and `europe-west1` using non-overlapping IP address ranges.

Cevap

Create a single custom-mode VPC network with individual subnets created in `us-central1` and `europe-west1` using non-overlapping IP address ranges.
In Google Cloud, a VPC network is a global resource, while subnets are regional resources. Creating a single custom-mode VPC network with distinct, non-overlapping subnets in `us-central1` and `europe-west1` allows compute resources in both regions to communicate privately using internal IP addresses over Google's internal global backbone network without additional routing hardware or public internet exposure.

Adım Adım Çözüm

1
Understand the scope of GCP VPC networks vs. Subnets
Recognize that a VPC network in Google Cloud is a global resource that spans all available regions, while subnets are regional resources tied to specific geographic regions.
This structural distinction defines how multi-region routing operates within GCP.
2
Evaluate inter-subnet communication within a single VPC
Instances in different regional subnets of the same VPC network can route traffic internally across regions using Google's global fiber backbone without needing public IP addresses or VPN tunnels.
VPC routing is inherently global within a single VPC container.
3
Identify subnet CIDR constraints
Ensure each region receives its own regional subnet with a distinct, non-overlapping IPv4 CIDR range.
Overlapping CIDR blocks within the same network topology lead to routing collisions and invalid configuration.

Anahtar Kavram

Google Cloud VPC networks are global constructs containing regional subnets that route internally across regions via Google's backbone network.
Soru 311Soru

An architect is configuring an estimate in the Google Cloud Pricing Calculator for a fault-tolerant, stateless processing workload on Compute Engine that can handle unexpected instance termination. Which VM provisioning model should be selected in the calculator to achieve the maximum cost savings?

Cevabı ve açıklamayı göster

Cevap: Spot VMs

Cevap

Spot VMs should be selected in the Pricing Calculator to achieve maximum cost savings for fault-tolerant workloads.
Selecting Spot VMs in the Google Cloud Pricing Calculator is correct because Google Cloud offers massive discounts (up to 60-91%) on unused compute capacity for fault-tolerant, stateless workloads that can survive unexpected instance terminations.

Adım Adım Çözüm

1
Identify the workload characteristics described in the scenario
The workload is stateless, fault-tolerant, and capable of handling sudden instance termination.
Fault-tolerant workloads can safely run on preemptible capacity without causing application failure.
2
Evaluate Compute Engine pricing models in the Google Cloud Pricing Calculator
Spot VMs offer discount rates between 60% and 91% compared to standard hourly on-demand rates.
Google Cloud offers excess compute capacity at deep discounts via Spot VMs for workloads that tolerate preemption.

Anahtar Kavram

Selecting Spot VMs for fault-tolerant workloads in the GCP Pricing Calculator to minimize compute costs.
Soru 312Soru

A startup is planning to deploy a containerized application on Google Kubernetes Engine (GKE). The DevOps team wants a fully managed solution where Google automatically provisions, configures, and scales the underlying node infrastructure based on pod specifications, eliminating the need to manage node pools manually. Which GKE cluster operational mode should the team select?

Cevabı ve açıklamayı göster

Cevap: GKE Autopilot mode

Cevap

GKE Autopilot mode is the correct choice because Google manages node provisioning, scaling, and cluster maintenance, eliminating node-level management overhead.
GKE Autopilot mode provides a fully managed cluster architecture where Google handles node provisioning, auto-scaling, security patching, and node configuration. This satisfies the requirement of eliminating manual node management overhead.

Adım Adım Çözüm

1
Analyze the operational requirements specified in the scenario.
The team requires zero node management overhead and automated node lifecycle management by Google.
Identifying management constraints determines whether Autopilot or Standard mode is appropriate.
2
Compare GKE cluster operational modes against the requirement.
GKE Autopilot automatically manages node provisioning, hardware configuration, and scaling based on pod requests.
GKE Autopilot shifts node management responsibilities completely to Google.

Anahtar Kavram

GKE Autopilot vs. Standard Operational Boundaries
Tahmini Süre:1m 0s
Soru 313Soru

You have created a Google Kubernetes Engine (GKE) cluster named `demo-cluster` in zone `us-central1-a`. You open a terminal and run `kubectl get nodes`, but the command fails because your local authentication context is missing. Which `gcloud` command must you execute to update your kubeconfig file with credentials for this cluster?

Cevabı ve açıklamayı göster

Cevap: gcloud container clusters get-credentials demo-cluster --zone us-central1-a

Cevap

Execute `gcloud container clusters get-credentials demo-cluster --zone us-central1-a` to update the local kubeconfig context.
Executing `gcloud container clusters get-credentials demo-cluster --zone us-central1-a` downloads cluster credentials and updates the local `kubeconfig` file, allowing `kubectl` to interact with the GKE cluster.

Adım Adım Çözüm

1
Identify the missing prerequisite for executing `kubectl` commands against a newly created GKE cluster.
Recognize that `kubectl` requires endpoint certificates and user credentials stored in the local `~/.kube/config` file.
Without proper kubeconfig context entries, `kubectl` cannot locate or authenticate against the GKE control plane.
2
Determine the appropriate `gcloud` command to retrieve and populate cluster credentials.
`gcloud container clusters get-credentials` fetches authentication tokens and writes the required context into `kubeconfig`.
This is the Google-recommended command for enabling local `kubectl` access to a GKE cluster.

Anahtar Kavram

Fetching GKE cluster credentials using gcloud to configure local kubectl context
Tahmini Süre:45s
Soru 314Soru

A cloud administrator is establishing governance for a newly acquired business unit in Google Cloud. The administrator needs to set up a dedicated hierarchy branch under the organization node, enforce regional deployment boundaries using organization policy constraints, and place both new and existing workloads into this branch. What is the correct sequence of steps to establish this resource hierarchy and governance structure?

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

Cevabı ve açıklamayı göster

Cevap

The correct sequence is to first create the parent Folder under the Organization node, apply the Organization Policy constraint at the Folder level, create the new workload Project within the Folder, and finally move the existing standalone Project into the Folder.
In Google Cloud resource hierarchy management, structural nodes (Folders) must be created first under the Organization node. Once the container node exists, governance rules such as Organization Policies should be attached at that Folder level so that policy inheritance takes effect. After policy enforcement is established, new projects can be created directly inside the Folder, and existing standalone projects can be migrated into the Folder to inherit the governance constraints.

Adım Adım Çözüm

1
Create the parent container (Folder) directly under the Organization node.
Establishes the structural node in the resource hierarchy where policies and child resources will be anchored.
You cannot apply folder-level policies or assign projects to a folder until the folder container itself exists.
2
Apply the Organization Policy constraint to the newly created Folder.
Establishes security and compliance guardrails that automatically propagate down to all child projects via resource hierarchy inheritance.
Setting policies prior to project creation ensures that newly provisioned or migrated workloads immediately comply with corporate governance.
3
Provision the new project inside the configured parent Folder.
The project is initialized directly within the folder governance scope.
Creating the project in the designated folder ensures it inherits the location restrictions defined at the folder level upon creation.
4
Move the existing project into the parent Folder.
The legacy project changes its location in the resource hierarchy and immediately inherits the folder's policy constraints.
Moving an existing project into a folder is performed after policy configuration so that the project instantly aligns with the target folder's active policy state.

Anahtar Kavram

Resource hierarchy inheritance and sequential project governance provisioning in Google Cloud.
Soru 315Soru

A financial services organization is managing a custom-mode Virtual Private Cloud (VPC) network in Google Cloud. The primary subnet in `europe-west1` is configured with the IP block 10.40.16.0/2210.40.16.0/22 (10.40.16.010.40.19.25510.40.16.0 - 10.40.19.255). Two other regional subnets in the same VPC use 10.40.0.0/2110.40.0.0/21 (10.40.0.010.40.7.25510.40.0.0 - 10.40.7.255) and 10.40.8.0/2210.40.8.0/22 (10.40.8.010.40.11.25510.40.8.0 - 10.40.11.255). Due to rapid scaling, the architecture team must expand the primary IP range of the `europe-west1` subnet to support at least 3,500 internal compute instances without recreating the subnet or causing downtime for existing workloads. Which CIDR modification plan accomplishes this expansion without creating an IP range collision?

Cevabı ve açıklamayı göster

Cevap: Expand the primary subnet CIDR block in `europe-west1` from 10.40.16.0/2210.40.16.0/22 to 10.40.16.0/2010.40.16.0/20.

Cevap

Expand the primary subnet CIDR block in europe-west1 from 10.40.16.0/2210.40.16.0/22 to 10.40.16.0/2010.40.16.0/20.
Expanding the primary subnet to 10.40.16.0/2010.40.16.0/20 provides 4,096 IP addresses (10.40.16.010.40.31.25510.40.16.0 - 10.40.31.255), satisfying the 3,500 instance requirement. It fully contains the original 10.40.16.0/2210.40.16.0/22 IP range (10.40.16.010.40.19.25510.40.16.0 - 10.40.19.255) without overlapping existing subnets (10.40.0.0/2110.40.0.0/21 and 10.40.8.0/2210.40.8.0/22).

Adım Adım Çözüm

1
Determine the required IP address capacity.
To support at least 3,500 instances, a /20/20 subnet mask (23220=4,0962^{32-20} = 4,096 IP addresses) is required, whereas a /21/21 mask provides only 2,048 addresses.
Google Cloud VPC subnets require sufficient contiguous IP space for compute instances and reserved network addresses.
2
Evaluate GCP VPC subnet expansion constraints.
The new expanded CIDR range must be a broader netmask (smaller prefix number), and the original subnet range (10.40.16.0/2210.40.16.0/22) must be fully contained inside the new range.
GCP permits zero-downtime subnet expansion only when the base address alignment retains existing workloads inside the expanded range.
3
Check for IP address overlap across existing VPC subnets.
The block 10.40.16.0/2010.40.16.0/20 spans 10.40.16.010.40.16.0 through 10.40.31.25510.40.31.255. It contains 10.40.16.0/2210.40.16.0/22 (10.40.16.010.40.19.25510.40.16.0 - 10.40.19.255) and does not conflict with 10.40.0.0/2110.40.0.0/21 (10.40.0.010.40.7.25510.40.0.0 - 10.40.7.255) or 10.40.8.0/2210.40.8.0/22 (10.40.8.010.40.11.25510.40.8.0 - 10.40.11.255).
Subnet ranges within a single VPC network must be strictly non-overlapping.

Anahtar Kavram

VPC Subnet Expansion and CIDR Planning
Tahmini Süre:2m 0s
Soru 316Soru

A DevOps engineer creates a new Google Kubernetes Engine (GKE) cluster named `prod-cluster` in the `us-central1` region. From a newly provisioned administrator workstation, the engineer attempts to deploy a application workload using `kubectl apply -f deployment.yaml`. However, the command fails with an error indicating that the connection to server `localhost:8080` was refused. Which action should the engineer take to allow `kubectl` to successfully communicate with the GKE cluster?

Cevabı ve açıklamayı göster

Cevap: Execute `gcloud container clusters get-credentials prod-cluster --region us-central1` to update the local kubeconfig file with cluster entry details and authentication credentials.

Cevap

Execute `gcloud container clusters get-credentials prod-cluster --region us-central1` to retrieve the cluster kubeconfig credentials.
The option directing the user to run `gcloud container clusters get-credentials prod-cluster --region us-central1` is correct because `kubectl` relies on the local `kubeconfig` file to locate and authenticate against the GKE API server endpoint. Fetching credentials via `gcloud` writes the necessary context and authorization tokens to `kubeconfig`.

Adım Adım Çözüm

1
Identify the cause of the `localhost:8080` connection error.
Recognize that `kubectl` defaults to `localhost:8080` when no cluster context or API server endpoint is configured in the workstation's `~/.kube/config` file.
Before `kubectl` can send requests to a remote GKE API server, it requires cluster certificates and endpoint information.
2
Run the `gcloud container clusters get-credentials` command specifying the cluster name and region.
The command queries GKE endpoints, retrieves cluster credentials, and populates an entry in the local `kubeconfig` file.
This configures the active context for `kubectl` to target the GKE cluster control plane.
3
Re-run `kubectl apply -f deployment.yaml`.
The deployment manifest is submitted directly to the GKE control plane and resources are created.
The authenticated request reaches the correct cluster control plane URL.

Anahtar Kavram

Configuring kubectl credentials for GKE cluster management using gcloud
Soru 317Soru

An enterprise is planning a multi-region Google Cloud deployment that connects to an on-premises data center using Cloud Interconnect. The environment must host Google Kubernetes Engine (GKE) clusters using alias IPs and prevent IP address collisions. Sequence the following steps in the correct order to properly plan and implement the Virtual Private Cloud (VPC) network architecture from initial network assessment to hybrid connectivity configuration.

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

Cevabı ve açıklamayı göster

Cevap

The correct sequence begins with auditing existing on-premises IP space, followed by creating a custom-mode VPC network, provisioning custom subnets with non-overlapping primary CIDR ranges, configuring secondary CIDR ranges for GKE alias IPs, and finally setting up Cloud Router BGP advertising to the on-premises network.
Proper VPC network planning for enterprise hybrid environments follows a logical sequence: identifying unallocated IP ranges on-premises first, creating a custom-mode VPC network to maintain full subnet control, establishing regional subnets with primary CIDRs, provisioning secondary ranges for GKE cluster alias IPs, and finally advertising the completed CIDRs across BGP over Cloud Interconnect.

Adım Adım Çözüm

1
Audit existing on-premises IP space and identify unallocated ranges.
Establishes clear boundaries for GCP IP assignment, avoiding IP address collisions with existing on-premises networks.
VPC planning must begin by identifying available unallocated space prior to defining cloud ranges.
2
Create a custom-mode VPC network.
Disables automatic creation of subnets in every region, providing total control over subnet CIDR block selection.
Auto-mode VPC networks automatically create subnets using fixed 10.128.0.0/910.128.0.0/9 ranges which often overlap with enterprise networks.
3
Define primary IPv4 CIDR blocks for subnets in selected regions.
Subnets are created with tailored, non-overlapping primary IP ranges.
Subnet primary ranges must exist before secondary ranges can be attached.
4
Configure secondary IPv4 CIDR ranges on the subnets for GKE cluster Pods and Services.
Reserves distinct IP ranges attached to the subnets for container networking.
GKE native VPC clusters rely on secondary IP ranges configured on the subnets for pod and service alias IPs.
5
Configure Cloud Router BGP routes to advertise the VPC subnet ranges to on-premises.
Enables two-way dynamic routing between on-premises and GCP workloads.
Dynamic routing propagation must reflect fully configured subnet primary and secondary ranges.

Anahtar Kavram

Planning Enterprise Hybrid VPC Networks and Subnets
Tahmini Süre:2m 0s
Soru 318Soru

A DevOps automation principal needs to grant a service account the minimum necessary IAM roles and execute the appropriate gcloud commands to create a new workload project inside a corporate folder and link it to an existing Cloud Billing Account. Arrange the steps in the correct operational sequence from first to last to complete this task under the principle of least privilege.

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

Cevabı ve açıklamayı göster

Cevap

The correct operational sequence begins with granting `roles/resourcemanager.projectCreator` on the target folder, followed by granting `roles/billing.user` on the Cloud Billing Account, creating the project using `gcloud projects create`, and finally linking the billing account using `gcloud billing projects link`.
Permissions must be configured prior to executing CLI commands. First, folder-level project creation rights (`roles/resourcemanager.projectCreator`) and billing account consumption rights (`roles/billing.user`) are established. Second, the project is created under the folder via `gcloud projects create`. Finally, billing is attached via `gcloud billing projects link`.

Adım Adım Çözüm

1
Assign folder creation privileges
Service account gains authorization to create projects within the specific folder.
Google Cloud IAM requires permission propagation at the target hierarchy node before resource provisioning commands can succeed.
2
Assign billing authorization privileges
Service account gains authorization to link projects to the specified billing account.
Least-privilege guidelines mandate granting `roles/billing.user` on the billing account rather than broad primitive roles like Owner or Project Billing Manager.
3
Provision the target project
New project ID is created under the specified folder ID.
The project resource must exist before billing association can take place.
4
Associate billing account to project
Project status is updated to enable paid API services and compute resource provisioning.
Linking requires permissions on both the billing account (`roles/billing.user`) and the target project (inherently held by project creation or project management roles).

Anahtar Kavram

Configuring least-privilege IAM roles (`roles/resourcemanager.projectCreator` and `roles/billing.user`) and executing the gcloud tool sequence for project creation and billing link association.
Soru 319Soru

An Associate Cloud Engineer needs to configure granular access controls for an automated deployment service account by creating a new project-level custom IAM role and granting it to the service account. Which sequence of steps represents the correct procedure to implement this using the gcloud command-line tool?

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

Cevabı ve açıklamayı göster

Cevap

The correct operational order is: First, define the custom role properties in a local YAML configuration file. Second, create the project-level custom role using `gcloud iam roles create`. Third, verify the created role details with `gcloud iam roles describe`. Fourth, assign the custom role to the target service account using `gcloud projects add-iam-policy-binding`.
Creating and applying a custom IAM role requires a strict workflow: first defining the permission schema in a file, creating the role resource at the desired level of the hierarchy using `gcloud iam roles create`, validating the resource via `gcloud iam roles describe`, and lastly modifying the resource's IAM policy binding to attach the role to the principal via `gcloud projects add-iam-policy-binding`.

Adım Adım Çözüm

1
Draft the custom role definition file
A structured YAML file containing metadata and exact permission strings (such as `compute.disks.create`).
Google Cloud best practice requires defining granular permissions in a declarative format prior to resource creation.
2
Create the custom IAM role in the GCP project
The custom IAM role is created under the path `projects/[PROJECT_ID]/roles/[ROLE_NAME]`.
The role must exist in the target project's IAM registry before it can be assigned to principals.
3
Inspect and verify the custom role status
Confirmation that the role launch stage is active and contains the expected permissions.
Verifying role configuration ensures no typos or missing permissions exist before applying the role to production service accounts.
4
Bind the custom role to the service account principal
An updated IAM policy for the project granting the service account access.
Role creation and role assignment are separate IAM operations; the binding step applies the role to the identity.

Anahtar Kavram

Custom IAM Role Creation and Policy Binding Lifecycle
Soru 320Soru

A cloud administration team needs to expand the primary IP address range of an existing subnet in a custom-mode Virtual Private Cloud (VPC) network. The subnet is currently configured with the primary CIDR block 10.20.1.0/2410.20.1.0/24. Which CIDR range can be specified to successfully expand this existing subnet's primary IP range?

Cevabı ve açıklamayı göster

Cevap: 10.20.0.0/2310.20.0.0/23

Cevap

The CIDR range 10.20.0.0/2310.20.0.0/23 correctly expands the existing subnet.
In Google Cloud VPC networks, expanding an existing primary subnet CIDR block requires providing a larger CIDR range (smaller netmask prefix length) that entirely includes the original IP range. The CIDR 10.20.0.0/2310.20.0.0/23 spans from 10.20.0.010.20.0.0 to 10.20.1.25510.20.1.255, which fully encapsulates the existing 10.20.1.0/2410.20.1.0/24 block.

Adım Adım Çözüm

1
Identify the existing subnet primary IP range
The current subnet uses 10.20.1.0/2410.20.1.0/24, which covers IP addresses 10.20.1.010.20.1.0 through 10.20.1.25510.20.1.255.
Expanding a subnet requires selecting a broader network block that contains the original block.
2
Evaluate valid expansion constraints in Google Cloud VPC
To expand a primary subnet IP range, the netmask must be decreased (e.g., /24 to /23), and the start of the new block must align properly while containing the original addresses.
Subnet ranges can only be expanded, never shrunk or replaced with non-contiguous blocks.
3
Verify candidate CIDR blocks
10.20.0.0/2310.20.0.0/23 covers 10.20.0.010.20.0.0 to 10.20.1.25510.20.1.255, successfully encompassing the original 10.20.1.0/2410.20.1.0/24 block while doubling the available IP capacity.
This meets all VPC primary IP range expansion requirements.

Anahtar Kavram

VPC Subnet Primary CIDR Expansion Rules
ÖncekiSayfa 16 / 80Sonraki
Tüm alıştırma soruları — Google Cloud Associate Cloud Engineer | Examkin