All practice questions

1591 questions

Question 161Question

An organization is planning to deploy batch machine learning training jobs on Google Cloud Compute Engine. The jobs support native checkpointing, can tolerate unexpected instance preemptions without losing progress, and must be executed at the lowest possible cost. Which Compute Engine provisioning model should you recommend?

Show answer & explanation

Answer: Spot VM instances

Answer

Spot VM instances should be selected to run fault-tolerant, interruptible batch workloads at the lowest possible cost.
Spot VM instances utilize excess Compute Engine capacity and offer discounts between 60% and 91% compared to standard VM pricing. Because the machine learning workload natively checkpoints progress and tolerates preemptions, Spot VMs deliver maximum cost efficiency without risking data loss.

Step-by-Step Solution

1
Analyze the operational requirements of the workload
The machine learning training job is a batch process, supports checkpointing, and can handle unexpected interruptions.
Fault-tolerant workloads do not require guaranteed VM availability or high-availability SLAs.
2
Evaluate Google Cloud Compute Engine cost-optimization features
Spot VMs provide steep discounts by using spare Google Compute Engine capacity, with the caveat that Compute Engine can reclaim them at any time.
Because the workload saves its state periodically, preemption simply delays execution slightly rather than causing data loss, achieving maximum cost savings.

Key Concept

Planning Compute Engine Resources and Machine Types for Fault-Tolerant Workloads
Question 162Question

An enterprise organization uses a Google Cloud resource hierarchy consisting of an Organization node, department Folders, and environment Projects. A compliance auditor needs read-only access to all current and future Google Cloud resources grouped under the 'Finance-Dept' folder. You need to configure access control following Google Cloud best practices and the principle of least privilege. Which action should you take?

Show answer & explanation

Answer: Grant the predefined Viewer role (roles/viewer) to the auditor at the 'Finance-Dept' folder level.

Answer

Grant the predefined Viewer role (roles/viewer) to the auditor at the 'Finance-Dept' folder level.
In Google Cloud's resource hierarchy, IAM policy bindings flow downward from Organization to Folders to Projects to Resources. Assigning the predefined Viewer role at the 'Finance-Dept' folder level grants read-only access to all present and future child resources while maintaining administrative efficiency and the principle of least privilege.

Step-by-Step Solution

1
Identify the resource hierarchy node that encapsulates all target resources.
The 'Finance-Dept' folder is identified as the parent container.
IAM permissions assigned at a higher node in the hierarchy inherit automatically to all lower child resources.
2
Select the role matching the exact read-only access requirement.
The predefined Viewer role (roles/viewer) is selected.
Predefined roles strictly align with the principle of least privilege compared to broad primitive roles.
3
Apply the IAM role binding at the folder level.
The auditor inherits read access across all current and future projects in 'Finance-Dept'.
Folder-level binding eliminates manual configuration for future child projects.

Key Concept

Resource Hierarchy IAM Policy Inheritance
Question 163Question

A software development team needs to deploy a stateless web application packaged inside a custom Docker container image to Google Cloud without managing underlying infrastructure or virtual machines. Which Google Cloud serverless compute option should the team select?

Show answer & explanation

Answer: Cloud Run

Answer

Cloud Run is the ideal Google Cloud serverless option for deploying custom container images without managing server infrastructure.
Cloud Run provides a fully managed serverless execution environment that automatically scales stateless applications packaged as container images without requiring server management.

Step-by-Step Solution

1
Analyze workload packaging and operational constraints
The application requires running a custom Docker container image on a serverless platform without infrastructure management.
Identifying containerization and serverless operational criteria narrows down the valid Google Cloud compute options.
2
Compare serverless compute capabilities in Google Cloud
Cloud Run runs arbitrary stateless container images directly in a fully managed serverless environment, whereas Cloud Functions targets single-purpose code snippets.
Cloud Run provides serverless container deployment capabilities tailored to custom packaging needs.

Key Concept

Selecting serverless compute options based on workload containerization requirements
Estimated Time:45s
Question 164Question

A cloud security auditor requires read-only visibility into all cloud resources contained within a specific business unit's folder. An IT administrator grants the auditor the Viewer role (roles/viewer) directly on that folder. Which statement correctly describes the outcome of this role assignment across the resource hierarchy?

Show answer & explanation

Answer: The auditor automatically inherits read-only access to all current and future projects contained within that folder.

Answer

The auditor automatically inherits read-only access to all current and future projects contained within that folder.
In Google Cloud, IAM policies follow a strict top-down inheritance model across the resource hierarchy (Organization -> Folder -> Project -> Resource). Granting an IAM role at the folder level ensures that any existing or newly created child projects inside that folder automatically inherit the associated permissions.

Step-by-Step Solution

1
Identify the node in the resource hierarchy where the IAM role is granted.
The Viewer role is assigned at the Folder level.
In Google Cloud, resource hierarchy follows Organization > Folder > Project > Resource.
2
Apply the rule of IAM policy inheritance.
Permissions granted on a parent node are inherited by all child resources.
Policy inheritance in Google Cloud IAM is transitive and automatic.

Key Concept

Resource Hierarchy IAM Policy Inheritance
Question 165Question

A data processing team needs to run a 4-hour nightly batch job that validates large data files. The application is designed to be fault-tolerant and can checkpoint its progress to resume if interrupted. The primary objective is to minimize compute costs as much as possible. Which Compute Engine resource planning option is best suited for this workload?

Show answer & explanation

Answer: Compute Engine Spot virtual machine instances

Answer

Compute Engine Spot virtual machine instances provide the highest cost savings for fault-tolerant, checkpoint-enabled batch jobs.
Compute Engine Spot VMs offer up to 60-91% discounts compared to standard VM pricing, making them the most cost-effective choice for stateless or checkpointed batch workloads that can handle preemption.

Step-by-Step Solution

1
Analyze workload characteristics
The job runs for 4 hours, is executed nightly, and is fault-tolerant with checkpointing capabilities.
Understanding execution duration and tolerance for interruptions determines appropriate compute pricing models.
2
Evaluate compute pricing models
Spot VMs provide extreme discounts in exchange for potential preemption, matching fault-tolerant batch job requirements perfectly.
Choosing Spot VMs over Standard VMs or Serverless runtimes minimizes cost while accommodating the 4-hour runtime.

Key Concept

Evaluating Spot VMs for fault-tolerant, cost-sensitive batch compute workloads
Question 166Question

An enterprise logistics firm is planning Compute Engine virtual machine specifications for a legacy telemetry parser service. The workload runs continuously 24 hours a day, 7 days a week, and strictly requires 2 vCPUs and 14 GB of memory to run efficiently without waste. Standard machine types provide either too little memory (2 vCPUs with 8 GB) or unnecessary compute (4 vCPUs with 16 GB). Which deployment strategy should the Cloud Engineer recommend to minimize monthly operational costs while meeting these exact workload requirements?

Show answer & explanation

Answer: Provision Compute Engine VMs using Custom Machine Types with 2 vCPUs and 14 GB memory, and purchase Committed Use Discounts (CUDs) for the baseline workload.

Answer

Provision Compute Engine VMs using Custom Machine Types tailored to 2 vCPUs and 14 GB memory, combined with Committed Use Discounts (CUDs) for steady 24/7 execution.
Configuring Custom Machine Types prevents paying for unused vCPUs when specific memory-to-vCPU ratios are needed, and applying Committed Use Discounts maximizes cost savings for steady-state 24/7 baseline infrastructure.

Step-by-Step Solution

1
Analyze resource requirements and machine type selection
Custom Machine Types allow defining non-standard vCPU and memory combinations (2 vCPUs, 14 GB RAM), preventing resource over-provisioning.
Predefined machine types like n1-standard-4 (4 vCPUs, 15 GB RAM) double the required CPU cost unnecessarily.
2
Analyze workload availability and pricing model
Since the workload runs 24/7 continuously, Committed Use Discounts (CUDs) offer the highest guaranteed discount (up to 57% for 1-year or 3-year commitments).
Spot VMs are subject to preemption and are inappropriate for uninterruptible continuous workloads.

Key Concept

Custom Machine Types & Committed Use Discounts (CUDs) optimization
Question 167Question

A financial analytics company is designing its Google Cloud infrastructure to handle two distinct workload requirements:
1. A batch risk-modeling application that runs nightly for 6 hours, processing fault-tolerant worker tasks that checkpoint state to Cloud Storage every 10 minutes.
2. A core licensing and authentication service that must run continuously 24/7 with strict uptime requirements.

The team wants to optimize infrastructure costs while maintaining compliance with operational requirements. Which Compute Engine provisioning strategy should the cloud engineer recommend?

Show answer & explanation

Answer: Provision Spot VMs using Managed Instance Groups for the batch risk-modeling application, and use standard Compute Engine instances with Committed Use Discounts (CUDs) for the 24/7 licensing service.

Answer

Use Spot VMs for the fault-tolerant, checkpointed batch processing application, and use standard VM instances backed by Committed Use Discounts for the continuous 24/7 licensing service.
The correct strategy leverages Spot VMs for the batch application because its state is saved every 10 minutes and it can tolerate instance preemption in exchange for high cost discounts. For the 24/7 licensing service, standard instances backed by Committed Use Discounts (CUDs) guarantee baseline availability while securing deep financial savings.

Step-by-Step Solution

1
Analyze the requirements for Workload 1 (Batch risk-modeling).
Workload 1 runs for 6 hours nightly and regularly checkpoints data, indicating high fault tolerance.
Fault-tolerant batch jobs are ideal candidates for Spot VMs, offering up to 60-91% discount off standard pricing.
2
Analyze the requirements for Workload 2 (Licensing service).
Workload 2 requires continuous 24/7 uptime with high availability.
Steady-state continuous workloads should use standard VMs combined with Committed Use Discounts (CUDs) to maximize savings without risk of preemption.
3
Synthesize the optimal Google Cloud compute strategy.
Combine Spot VMs for batch compute and Committed Use Discounts for baseline 24/7 workloads.
This combination aligns perfectly with Google Cloud recommended practices for cost optimization and workload reliability.

Key Concept

Compute Engine Workload Planning: Spot VMs vs Committed Use Discounts
Estimated Time:2m 0s
Question 168Question

A cloud administrator needs to request an increase for a Compute Engine GPU quota in a specific region for a Google Cloud project. Which two actions should the administrator take to perform this request? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Navigate to the Quotas page in the IAM & Admin section of the Google Cloud Console.; Select the specific GPU quota metric and region, then submit a quota increase request with a business justification.

Answer

The correct actions are navigating to the Quotas page in the IAM & Admin section of the Google Cloud Console, selecting the specific GPU metric and region, and submitting a quota increase request with a justification.
To request additional resource capacity in Google Cloud, administrators must access the IAM & Admin Quotas section in the Cloud Console, identify the exact metric and region requiring an increase, and submit a request including justification for the GCP support team to evaluate.

Step-by-Step Solution

1
Locate quota management interface
Access the Quotas page under IAM & Admin in the Google Cloud Console.
Quota management and increase requests are handled centrally in the Cloud Console IAM & Admin Quotas section.
2
Submit increase request
Filter for the target GPU metric and region, specify the requested limit, and provide a business justification.
Google Cloud requires specific metric selection and justification to review and approve quota increases.

Key Concept

Requesting GCP Resource Quota Increases
Question 169Question

A security audit reveals that the Google Group `[email protected]` has been granted the `roles/compute.admin` role at a parent Folder level named `Finance-Prod`. This folder contains ten production projects, including a sensitive audit project named `payments-main`. Company security policy requires members of `[email protected]` to retain Compute Engine administrative access across nine of the projects, but they must explicitly have no administrative access to `payments-main`. How should you restructure the IAM configuration to meet this requirement following the principle of least privilege?

Show answer & explanation

Answer: Remove the `roles/compute.admin` role binding for `[email protected]` from the `Finance-Prod` folder, and grant the `roles/compute.admin` role directly on each of the nine projects that require it.

Answer

Remove the `roles/compute.admin` role binding for `[email protected]` from the `Finance-Prod` folder, and grant `roles/compute.admin` individually on the nine projects requiring access.
In Google Cloud, IAM policy evaluation is additive down the resource hierarchy (Organization > Folder > Project > Resource). If a role is granted at the Folder level, all projects under that folder inherit those permissions. Because inherited permissions cannot be revoked or overridden at a child project level, the folder-level role grant must be removed and replaced with explicit project-level grants on only the projects that require access.

Step-by-Step Solution

1
Analyze IAM resource hierarchy inheritance rules.
Recognize that permissions granted at a parent node (Folder) are inherited down to all child nodes (Projects) and cannot be denied or revoked at the child level.
Google Cloud IAM policies are additive down the resource hierarchy tree.
2
Identify the source of over-privileged access.
The folder-level binding on `Finance-Prod` grants `roles/compute.admin` to all child projects, including `payments-main`.
To restrict access on one child project, the folder-level role binding must be removed.
3
Re-assign permissions following least privilege.
Remove the role grant from the parent folder and apply the `roles/compute.admin` role explicitly on the nine target projects.
This guarantees that `payments-main` does not inherit administrative permissions while preserving required access elsewhere.

Key Concept

Resource Hierarchy IAM Policy Additive Inheritance
Question 170Question

A data engineering team is attempting to deploy an automated batch processing pipeline inside a target Google Cloud project named `warehouse-analytics-live`. The execution fails because the Cloud Dataflow API (`dataflow.googleapis.com`) has not been activated in the project. As a Cloud Engineer, you must enable this service specifically for `warehouse-analytics-live` using the Google Cloud CLI. Which command should you execute?

Show answer & explanation

Answer: gcloud services enable dataflow.googleapis.com --project=warehouse-analytics-live

Answer

Execute `gcloud services enable dataflow.googleapis.com --project=warehouse-analytics-live` to activate the Dataflow API explicitly in the target project.
The command `gcloud services enable dataflow.googleapis.com --project=warehouse-analytics-live` directly activates the specified Google Cloud API endpoint for the designated project. Including the `--project` flag ensures deterministic execution against the target environment.

Step-by-Step Solution

1
Identify the required Google Cloud API service endpoint name.
The canonical service name for Cloud Dataflow is `dataflow.googleapis.com`.
Google Cloud API enablement commands require the full service identifier.
2
Select the correct gcloud CLI component for managing APIs.
Use `gcloud services enable` command group.
The `gcloud services` command group is designed for enabling, disabling, and listing Service Usage APIs.
3
Append the `--project` flag to specify the target project.
Command becomes `gcloud services enable dataflow.googleapis.com --project=warehouse-analytics-live`.
Specifying `--project` guarantees the API is enabled in the intended project regardless of the active local gcloud configuration context.

Key Concept

Enabling Cloud Service APIs using gcloud CLI with explicit project flags
Estimated Time:1m 0s
Question 171Question

An enterprise platform engineering team manages an automated infrastructure pipeline. The pipeline uses a custom service account to provision new Google Cloud projects. During execution, a script in the pipeline executes the command `gcloud services enable artifactregistry.googleapis.com --project=fintech-core-prod` to enable the Artifact Registry API in the target project. The execution fails with an authorization error indicating permission denied. Adhering to the Google Cloud security principle of least privilege, which action should the system administrator take to resolve this issue?

Show answer & explanation

Answer: Grant the pipeline service account the Service Usage Admin role (`roles/serviceusage.serviceUsageAdmin`) on the `fintech-core-prod` project.

Answer

Grant the pipeline service account the Service Usage Admin role (`roles/serviceusage.serviceUsageAdmin`) on the target project.
To enable Google Cloud APIs, an identity requires the `serviceusage.services.enable` permission on the destination project. The Service Usage Admin role (`roles/serviceusage.serviceUsageAdmin`) provides permissions to list, enable, and disable services on a project, making it the minimal predefined role necessary to meet the principle of least privilege.

Step-by-Step Solution

1
Identify the specific GCP permission required to enable APIs.
Enabling APIs using `gcloud services enable` requires the `serviceusage.services.enable` permission on the target project.
Google Cloud service enablement operates on a per-project basis via the Service Usage API.
2
Evaluate the available IAM roles for API enablement against security best practices.
The Service Usage Admin role (`roles/serviceusage.serviceUsageAdmin`) contains the required permission for enabling and disabling services without assigning excessive permissions.
Predefined roles should be preferred over primitive roles (Owner, Editor) to satisfy the principle of least privilege.
3
Select the correct resource scope for role binding.
Bind the role on the target project `fintech-core-prod`.
APIs must be activated within the workload/target project where the API endpoints will be consumed.

Key Concept

API Enablement IAM Permissions and Least Privilege
Question 172Question

An enterprise logistics company is planning the Google Cloud Compute Engine architecture for two distinct workloads:

1. An in-memory route calculation service running continuously 24/724/7 with a constant baseline demand. It requires a specific non-standard configuration of 1616 vCPUs and 128 GB128\text{ GB} of RAM (8 GB8\text{ GB} per vCPU).
2. A high-throughput image rendering pipeline that processes user-uploaded media. The rendering pipeline is stateless, fault-tolerant, and capable of resuming tasks if an instance terminates unexpectedly.

Which Compute Engine provisioning strategy optimizes infrastructure costs while meeting all operational requirements?

Show answer & explanation

Answer: Provision custom machine types with 16 vCPUs and 128 GB RAM covered by Committed Use Discounts (CUDs) for the route calculation service, and use Spot Virtual Machines within a Managed Instance Group for the image rendering pipeline.

Answer

Configure custom machine types (16 vCPUs, 128 GB RAM) backed by Committed Use Discounts for the continuous route calculation service, and utilize Spot VMs in a Managed Instance Group for the stateless image rendering pipeline.
Custom machine types allow tailoring the vCPU-to-memory ratio exactly (1616 vCPUs and 128 GB128\text{ GB} RAM) to prevent paying for unused compute capacity. Because the route calculation service runs constantly (24/724/7), attaching a Committed Use Discount (CUD) maximizes savings over a 1-year or 3-year period. Conversely, the image rendering pipeline is fault-tolerant and stateless, making Spot VMs within an autoscaling Managed Instance Group the most cost-effective choice.

Step-by-Step Solution

1
Analyze the resource ratio and execution continuity of the first workload.
The route calculation service requires 1616 vCPUs and 128 GB128\text{ GB} RAM (8 GB8\text{ GB} per vCPU), which does not align with standard predefined ratios (e.g., standard is 4 GB4\text{ GB}/vCPU, high-mem is 8 GB8\text{ GB}/vCPU on N1/N2 but fixed ratios). Using custom machine types avoids paying for unnecessary vCPUs. Since it runs 24/724/7, Committed Use Discounts (CUDs) provide up to 57% savings.
Matching custom machine specs eliminates wasted resources, and CUDs offer maximum savings for predictable, continuous compute baseline demand.
2
Evaluate fault tolerance and preemption resilience for the second workload.
The image rendering pipeline is stateless and fault-tolerant, allowing it to withstand instance terminations.
Spot VMs provide significant cost reductions (60-91% off standard prices) and are ideal for batch or stateless jobs that can handle preemption.
3
Combine the optimal pricing and machine type strategies.
Custom machine types + CUDs for Workload 1; Spot VMs in a MIG for Workload 2.
This strategy satisfies both performance/SLA guarantees and aggressive cost optimization.

Key Concept

Compute Engine Resource Planning, Custom Machine Types, Committed Use Discounts, and Spot VM Suitability
Estimated Time:3m 0s
Question 173Question

An organization is designing a Cloud Storage lifecycle policy for financial audit archives. The data access pattern is strictly defined as follows: objects are actively accessed multiple times daily for the first 30 days; between 31 and 90 days, objects are queried only once per month during financial reconciliation; after 90 days, objects are strictly retained for compliance and accessed less than once a year for 7 years. To minimize total cost of ownership (TCO) while avoiding early deletion/transition fee penalties and high data retrieval charges, which storage class lifecycle strategy should be planned?

Show answer & explanation

Answer: Store objects initially in Standard storage, configure an Object Lifecycle Management rule to transition objects to Nearline storage after 30 days, and add a second rule to transition objects to Archive storage after 90 days.

Answer

Store objects initially in Standard storage, configure an Object Lifecycle Management rule to transition objects to Nearline storage after 30 days, and add a second rule to transition objects to Archive storage after 90 days.
The correct strategy starts with Standard storage for the first 30 days to accommodate active daily access without retrieval fees. At 30 days, transitioning to Nearline storage matches the monthly access requirement and satisfies Nearline's 30-day minimum storage duration. At 90 days, transitioning to Archive storage provides the lowest cost for long-term compliance retention with access frequency under once per year.

Step-by-Step Solution

1
Analyze the access pattern for the initial 30-day period.
Daily active access requires Standard storage to avoid data retrieval fees.
Standard storage has no minimum retention duration and zero retrieval fees per GB, making it optimal for active data.
2
Evaluate the 31-90 day window and transition requirements.
Transitioning to Nearline storage at day 30 satisfies the monthly reconciliation access frequency.
Nearline storage is designed for data accessed at most once a month, has a 30-day minimum storage duration (satisfied between day 30 and day 90), and has lower retrieval costs than Coldline or Archive.
3
Evaluate the long-term storage requirement after 90 days.
Transitioning to Archive storage at day 90 maximizes long-term cost savings.
Archive storage offers the lowest storage cost per GB for data accessed less than once a year, perfectly matching the 7-year regulatory retention requirement.

Key Concept

Cloud Storage Class Selection and Object Lifecycle Management
Question 174Question

A financial services firm is building two backend components for a real-time transaction verification pipeline on Google Cloud:

1. Component X: An HTTP microservice that receives high-throughput API traffic. It relies on a custom C++ native binary compiled for Linux and must process up to 80 concurrent HTTP requests per instance to maximize resource efficiency.
2. Component Y: A lightweight Python event handler that executes briefly whenever a transaction log object is finalized in a Cloud Storage bucket, parsing the log and writing summary statistics to a database.

Which architecture recommendation correctly pairs these workloads with the appropriate Google Cloud serverless compute options?

Show answer & explanation

Answer: Deploy Component X to Cloud Run to support the custom C++ binary container environment and instance-level request concurrency, and deploy Component Y to Cloud Functions using a Cloud Storage event trigger.

Answer

Deploy Component X to Cloud Run to leverage custom container runtimes with multi-concurrency, and deploy Component Y to Cloud Functions with direct Cloud Storage event integration.
Cloud Run is built for containerized microservices, making it the appropriate choice when custom compiled system binaries (such as C++ libraries) are required and when high per-instance HTTP request concurrency (e.g., 80 requests/instance) is needed. Cloud Functions provides a FaaS paradigm that natively integrates with Cloud Storage event triggers to execute simple, short-lived Python functions upon file upload without container management.

Step-by-Step Solution

1
Analyze Component X requirements
Identified dependencies on a custom compiled Linux C++ binary and a concurrency target of 80 requests per instance.
Cloud Run executes custom OCI containers with support for arbitrary native libraries and configurable request concurrency per instance (up to 1,000 requests).
2
Analyze Component Y requirements
Identified a simple event-driven task triggered directly by object uploads in Cloud Storage.
Cloud Functions (FaaS) is ideal for short-lived, event-triggered code snippets natively integrated with Google Cloud events such as Cloud Storage triggers.
3
Evaluate architectural fit
Cloud Run for Component X and Cloud Functions for Component Y meets all technical constraints with minimum operational overhead.
This separation uses containerized serverless (Cloud Run) for binary/concurrency needs and function-as-a-service (Cloud Functions) for lightweight event processing.

Key Concept

Evaluating trade-offs between Cloud Run (custom containers, high concurrency, complex binaries) and Cloud Functions (lightweight, event-driven snippet execution).
Question 175Question

A Cloud Engineer needs to request an increase for a Compute Engine CPU resource quota in a specific region using the Google Cloud Console. What is the correct sequence of steps to submit this quota request?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence for requesting a GCP resource quota increase is to first navigate to the Quotas page, select the specific quota and region, enter the requested limit with justification, and submit the request.
Requesting a quota increase requires first navigating to the Quotas page in IAM & Admin, finding and selecting the specific quota metric and region, entering the new limit and required business justification, and finally submitting the request.

Step-by-Step Solution

1
Navigate to the Quotas section
Access to current quota limits across GCP services and regions
The IAM & Admin > Quotas section is the central location in the Cloud Console for viewing and editing quotas.
2
Select the target quota metric and location
Identification of the specific Compute Engine CPU quota in the intended region
GCP quotas are scoped by service and region, requiring precise selection before modification.
3
Specify new quota value and justification
Completion of the quota change form
Google Cloud requires a target limit and business justification to evaluate quota increase requests.
4
Submit the form
Request queued for automated processing or support review
Submitting completes the workflow and initiates the evaluation process.

Key Concept

Standard Console procedure for requesting GCP resource quota increases
Question 176Question

An organization needs to provision Google Cloud Compute Engine virtual machines for a fault-tolerant batch processing application. The application requires a non-standard configuration of 3 vCPUs and 11 GB of RAM to run efficiently. Which TWO configuration options should you select to meet the technical requirements while minimizing costs?

Select all that apply

Show answer & explanation

Answer: Provision the workload using a Custom Machine Type configured with 3 vCPUs and 11 GB of RAM.; Provision the Compute Engine instances as Spot VMs.

Answer

Selecting a Custom Machine Type with 3 vCPUs and 11 GB of RAM, and provisioning the instances as Spot VMs.
Using a Custom Machine Type allows precise resource allocation of 3 vCPUs and 11 GB RAM without paying for unused capacity. Provisioning the instances as Spot VMs maximizes cost savings for interruptible, fault-tolerant batch jobs.

Step-by-Step Solution

1
Analyze machine resource requirements
Standard machine types do not match 3 vCPUs and 11 GB RAM without over-provisioning.
Choosing a Custom Machine Type allows tailor-made vCPU and memory allocations to minimize wasted resources.
2
Evaluate workload fault tolerance for cost optimization
Batch processing that tolerates interruptions is ideal for Spot VMs.
Spot VMs offer steep discounts off standard pricing for fault-tolerant workloads.

Key Concept

Compute Engine Custom Machine Types and Spot VM Suitability
Question 177Question

An enterprise DevOps team needs to configure an automated service account, [email protected], to provision new Google Cloud projects inside a designated folder named Engineering-Apps. Additionally, these newly created projects must be linked to the company central billing account (ID: 01ABCD-EF1234-567890). Following the principle of least privilege, which configuration of IAM roles should be assigned to the service account?

Show answer & explanation

Answer: Grant Project Creator (roles/resourcemanager.projectCreator) on the Engineering-Apps folder and Billing Account User (roles/billing.user) on the central billing account.

Answer

Grant Project Creator (roles/resourcemanager.projectCreator) on the Engineering-Apps folder and Billing Account User (roles/billing.user) on the central billing account.
To create projects within a specific folder and link them to a billing account, an identity requires Project Creator (roles/resourcemanager.projectCreator) bound on that target folder and Billing Account User (roles/billing.user) bound on the specific Billing Account. This configuration satisfies the principle of least privilege by scoping project creation rights to the intended folder and limiting billing interaction to user-level linking.

Step-by-Step Solution

1
Identify the minimum permission needed to create projects in a specific resource container.
The Project Creator role (roles/resourcemanager.projectCreator) granted on the target folder (Engineering-Apps) allows creating projects within that folder without granting global organization-wide privileges.
Applying the role at the folder level adheres to the principle of least privilege.
2
Identify the minimum permission required to associate newly created projects with an enterprise billing account.
The Billing Account User role (roles/billing.user) must be bound directly on the billing account resource (01ABCD-EF1234-567890).
Project creation permissions do not automatically grant rights to attach billing accounts.

Key Concept

Scope-specific IAM role assignment for project creation and billing account linking in GCP resource hierarchy
Estimated Time:1m 30s
Question 178Question

A DevOps engineer needs to establish a new application environment in Google Cloud following standard operational procedures. In which order should the engineer execute the administrative steps to correctly position the project in the resource hierarchy, enable billing, and grant access?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence begins with creating the parent folder under the organization node, creating the project inside that folder, linking an active billing account to the project, enabling the necessary Cloud Service APIs, and finally granting predefined IAM roles to the development team.
Setting up a cloud solution environment follows a strict dependency workflow: the organizational folder must exist first to establish policy boundaries, followed by project creation inside that folder. Billing must then be linked so that required Cloud Service APIs can be enabled. Finally, IAM roles are assigned to grant user access to the enabled services.

Step-by-Step Solution

1
Create the parent organizational folder.
Establishes the resource hierarchy node under which the project will be grouped.
Folders act as logical parent containers for projects in the Google Cloud resource hierarchy.
2
Create the Google Cloud project inside the folder.
Establishes the fundamental container for resources, policies, and billing associations.
Projects cannot host services or receive billing associations until the project resource itself exists.
3
Link the Billing Account to the project.
Enables the project to consume GCP billable resources and services.
Google Cloud requires an active billing link before enabling paid service APIs or provisioning infrastructure.
4
Enable required Cloud Service APIs.
Activates service endpoints (such as Compute Engine or GKE APIs) within the project context.
Service APIs are disabled by default on new projects and must be enabled before resource creation commands succeed.
5
Grant IAM access roles on the project.
Provides team members with appropriate least-privilege permissions.
IAM roles are configured after establishing project infrastructure readiness so principals can safely begin operations.

Key Concept

Sequential administration for initializing Google Cloud projects within the resource hierarchy.
Question 179Question

A principal cloud engineer is preparing to deploy an automated data processing pipeline across a cluster of Compute Engine virtual machines in the us-central1 region. During initialization testing, instance creation fails with a QUOTA_EXCEEDED error for N2_CPUS. Upon inspecting the project's Quotas & System Limits page, the engineer confirms that current usage has reached the regional limit of 24 CPUs, but the pipeline requires 64 CPUs to meet SLA requirements. Which action should the engineer take to resolve this limitation following Google Cloud best practices?

Show answer & explanation

Answer: Select the N2_CPUS metric for us-central1 on the Quotas page in the Google Cloud Console, click Edit Quotas, enter the required quota value of 64 along with a justification, and submit the request.

Answer

Select the N2_CPUS metric for us-central1 on the Quotas page in the Google Cloud Console, click Edit Quotas, enter the required quota value of 64 along with a justification, and submit the request.
Google Cloud resource quotas protect users from unexpected spikes in consumption and prevent systemic overload. To increase a quota limit for a specific compute resource like regional N2 CPUs, an administrator must navigate to IAM & Admin > Quotas, select the relevant metric and region, specify the new target limit with a justification, and submit a quota increase request.

Step-by-Step Solution

1
Identify the specific quota bottleneck.
Determined that the N2_CPUS quota in the us-central1 region has reached 100% utilization (24 out of 24 CPUs).
GCP quotas are enforced at the individual project and regional level for specific machine families.
2
Navigate to IAM & Admin > Quotas in the Google Cloud Console.
Filtered the list of quotas by Metric (N2_CPUS) and Region (us-central1).
The Cloud Console Quotas page provides the administrative interface for viewing current usage and requesting quota increases.
3
Submit an official quota increase request.
Specified the new desired quota limit of 64 CPUs, provided business justification, and submitted the form.
Quota increase requests are evaluated by Google Cloud support or automated approval systems based on project history and justification.

Key Concept

GCP Resource Quota Management & Request Workflow
Estimated Time:2m 0s
Question 180Question

A digital publishing company is architecting serverless compute solutions for two new services on Google Cloud:

1. Service 1: An interactive web API that requires handling up to 250 concurrent HTTP requests per container instance to optimize resource utilization.
2. Service 2: A lightweight background script that executes automatically whenever a raw text file is uploaded to a Cloud Storage bucket.

Which TWO deployment decisions correctly align with Google Cloud serverless compute capabilities for these services?

Select all that apply

Show answer & explanation

Answer: Deploy Service 1 to Cloud Run because Cloud Run natively supports receiving multiple concurrent requests on a single container instance.; Deploy Service 2 to Cloud Functions because it directly integrates with Cloud Storage event triggers for automatic execution upon file upload.

Answer

Deploying Service 1 to Cloud Run to leverage container instance concurrency, and deploying Service 2 to Cloud Functions to take advantage of native Cloud Storage event triggers.
Cloud Run is ideal for stateless HTTP workloads requiring multi-concurrency per container instance. Cloud Functions is ideal for event-driven background processing triggered directly by Google Cloud services such as Cloud Storage object mutations.

Step-by-Step Solution

1
Analyze Service 1 requirements
Service 1 requires high HTTP concurrency per instance (up to 250 requests).
Cloud Run is designed to handle multi-concurrency within a single container instance, whereas 1st-gen Cloud Functions are strictly single-concurrency.
2
Analyze Service 2 requirements
Service 2 requires lightweight, event-driven execution triggered by Cloud Storage file uploads.
Cloud Functions excels at event-driven tasks triggered directly by Google Cloud service events like Cloud Storage bucket object creations.

Key Concept

Selecting between Cloud Run and Cloud Functions based on concurrency and event-driven trigger requirements
PreviousPage 9 / 80Next