Cloud Digital Leader Scaling with Google Cloud operations Practice Test 3 — 15 Questions

Question 1

A company wants to proactively identify underutilized Compute Engine VMs (high provisioned capacity but low actual usage) to reduce costs. Which Google Cloud tool provides recommendations for right-sizing VMs?

Choose an answer to begin — your selection is scored in the full session.

Accepted Answer

Active Assist Recommender — ML-based VM rightsizing recommendations.. Active Assist Recommender is Google Cloud's ML-based service that analyzes historical VM utilization metrics and generates rightsizing recommendations, flagging VMs that are over-provisioned relative to actual usage. It directly addresses the goal of proactively identifying underutilized Compute Engine VMs to reduce cost. The recommendations include specific machine type suggestions and estimated savings.

Answer

Cloud Monitoring — set alerts for low CPU utilization.

Answer

Cloud Asset Inventory — lists all VMs and their configurations.

Answer

Cloud Billing budgets — set spending limits to prevent overspend.

Question 2

An SRE team has a monthly error budget of 43 minutes (99.9% SLO). In the first week of the month, a deployment causes a 50-minute outage. What should the SRE team do for the remainder of the month, and why?

Accepted Answer

Freeze feature deployments for the rest of the month, focus on reliability improvements, and investigate the deployment process that caused the outage.. The team has already consumed more than the entire monthly error budget (50 minutes used vs. 43 minutes allowed). To avoid violating the 99.9% SLO for the rest of the month, they must freeze feature deployments and focus on reliability improvements. This is a core SRE practice: when the error budget is exhausted, the team shifts from feature velocity to stability, investigating the root cause and hardening the deployment process.

Answer

Immediately deploy a hotfix to restore features that were rolled back during the outage.

Answer

Negotiate with stakeholders to increase the SLO to 99.5% to get more error budget.

Answer

Continue deploying features normally — the outage was a one-time event and won't happen again.

Question 3

A reliability engineering team wants to proactively identify weaknesses in their distributed system by deliberately injecting failures — killing random instances, introducing network latency, and cutting off database connections — to observe how the system responds. What is this practice called?

Accepted Answer

Chaos engineering — deliberately injecting controlled failures to discover system weaknesses and build resilience confidence.. Chaos engineering is the practice of deliberately injecting controlled failures—such as killing instances, introducing latency, or cutting database connections—into a distributed system to proactively identify weaknesses and build resilience confidence. This approach aligns with Google Cloud's reliability principles, where tools like Chaos Monkey (part of the Simian Army) or Google's internal DiRT (Disaster Recovery Testing) are used to test system behavior under failure conditions.

Answer

Destructive testing — deliberately breaking the system to determine the breaking point.

Answer

Penetration testing — simulating attacks to find security vulnerabilities.

Answer

Load testing — verifying the system handles expected traffic volumes.

Question 4

Google Cloud's operations suite includes Cloud Monitoring for metrics. What is the difference between 'monitoring' and 'observability' in cloud operations?

Accepted Answer

Monitoring tracks predefined metrics and alerts on known conditions; observability is the system property enabling engineers to understand any internal state from its outputs (metrics, logs, traces).. Monitoring and observability are distinct concepts in cloud operations. Monitoring involves tracking predefined metrics and setting alerts for known failure conditions, while observability is a system property that allows engineers to understand any internal state by analyzing outputs like metrics, logs, and traces. In Google Cloud, Cloud Monitoring provides monitoring capabilities, but achieving true observability requires integrating Cloud Logging and Cloud Trace to explore unknown issues.

Answer

Monitoring and observability are identical terms — both describe collecting and analyzing system metrics.

Answer

Monitoring is for production; observability is for development and testing environments.

Answer

Observability only applies to AI systems; monitoring is for traditional applications.

Question 5

A company wants to set up automated checks that continuously verify their website's homepage, login page, and API endpoints are accessible from multiple global locations. If any endpoint becomes unreachable for more than 2 minutes, the on-call engineer should be alerted. Which Cloud Monitoring feature provides this?

Accepted Answer

Cloud Monitoring uptime checks that probe endpoints from global locations with alerting on failure.. Cloud Monitoring uptime checks are specifically designed to probe HTTP, HTTPS, or TCP endpoints from multiple global locations at configurable intervals (e.g., every 1 minute). They can trigger alerting policies when a check fails for a specified duration (e.g., 2 minutes), directly matching the requirement for continuous, multi-location endpoint accessibility verification with alerting on sustained failure.

Answer

Cloud Logging log-based alerts that detect 5xx errors in application logs.

Answer

Cloud Trace that records response times for each user request.

Answer

Custom scripts on Compute Engine VMs that ping endpoints every minute.

Question 6

A company's cloud costs have increased by 40% over the past quarter. The operations team wants to identify and address the root causes. Which cost optimization strategies should they investigate first?

Accepted Answer

Identify idle and underutilized resources (oversized VMs, unused disks, unattached IPs), apply lifecycle policies to storage, and commit to CUDs for stable workloads.. The first step in cloud cost optimization is to identify and eliminate waste from idle or oversized resources, which is the most common source of cost inefficiency. Applying lifecycle policies to storage and committing to Committed Use Discounts (CUDs) for stable workloads are proven strategies to reduce costs without compromising performance. This approach aligns with Google Cloud's recommended FinOps practices, focusing on immediate, high-impact savings before considering architectural changes.

Answer

Immediately upgrade all infrastructure to the latest generation hardware for better efficiency.

Answer

Migrate all workloads to Spot VMs immediately to reduce costs by 90%.

Answer

Switch cloud providers to whoever has the lowest advertised list price.

Question 7

Google Cloud runs its own infrastructure operations using the Site Reliability Engineering (SRE) model, which Google invented. What is the core principle that distinguishes SRE from traditional IT operations?

Accepted Answer

SRE applies software engineering principles to operations — automating toil, using quantitative SLOs, and treating reliability as an engineered system property.. The core principle of SRE is applying software engineering practices to operations work. This means automating manual toil, defining quantitative Service Level Objectives (SLOs) to measure reliability, and treating reliability as an engineered property of the system — not as an afterthought. This contrasts with traditional IT operations, which often rely on manual processes and reactive troubleshooting.

Answer

SRE teams never allow production deployments to ensure maximum stability.

Answer

SRE relies entirely on external monitoring vendors to detect and respond to all incidents.

Answer

SRE means development and operations teams are separate departments that communicate only via ticketing systems.

Question 8

A company uses Google Cloud across 5 teams, 20 projects, and 3 regions. They want to enforce a standard that all resources include specific labels (e.g., `team`, `environment`, `cost-center`) for cost attribution and governance. What is the most scalable way to enforce this labeling standard?

Accepted Answer

Enforce labeling through IaC templates with required label variables in CI/CD pipelines, and use Cloud Asset Inventory to audit compliance.. It combines Infrastructure as Code (IaC) templates with required label variables in CI/CD pipelines to enforce labeling at resource creation time, and uses Cloud Asset Inventory to audit and detect non-compliant resources. This approach is scalable across 5 teams, 20 projects, and 3 regions because it automates enforcement and provides continuous compliance monitoring without manual intervention.

Answer

Send monthly reminders to all teams via email to add labels to their resources.

Answer

Manually add labels to all existing and new resources through the Cloud Console.

Answer

Grant only project owners permission to create resources, and rely on them to enforce labeling.

Question 9

A company's application experiences a P1 (critical) production incident at 2 AM on a Sunday. The on-call engineer resolves the issue after 3 hours but isn't sure which team members to contact or what steps to follow during an incident. What operational practice and tooling would have helped manage this incident better?

Accepted Answer

Establish a documented incident response process with defined roles, escalation paths, and runbooks, supported by on-call rotation tooling and Cloud Monitoring alerting.. A documented incident response process with defined roles, escalation paths, and runbooks ensures that the on-call engineer knows exactly whom to contact and what steps to follow during a P1 incident. Combined with on-call rotation tooling (e.g., PagerDuty, Opsgenie) and Cloud Monitoring alerting, this practice reduces mean time to acknowledge (MTTA) and mean time to resolve (MTTR) by providing clear, repeatable procedures. Without such a process, the engineer wasted time determining the response, which a runbook would have eliminated.

Answer

Increase the application's max_instances so it scales to handle the issue automatically.

Answer

Move all production deployments to Sunday nights to avoid weekday incident risk.

Answer

Disable monitoring alerts to prevent false alarms that wake engineers unnecessarily.

Question 10

A company wants to optimize Cloud Storage costs for a bucket containing 100 TB of access logs. The logs from the last 7 days are frequently analyzed; logs from 8–90 days are occasionally reviewed; logs older than 90 days are archived for compliance but rarely accessed. What is the most cost-effective storage class configuration?

Accepted Answer

Configure lifecycle rules: Standard (0-7 days) → Nearline (8-90 days) → Archive (90+ days).. It aligns the storage class with the access patterns of the logs: Standard for frequently accessed recent data, Nearline for occasional access, and Archive for rarely accessed compliance data. This minimizes costs by using cheaper storage for older data while maintaining performance for active analysis. Lifecycle rules automate the transition, ensuring no manual intervention is needed.

Answer

Store all 100 TB in Standard storage for consistent access performance.

Answer

Delete all logs older than 7 days to minimize storage costs.

Answer

Store all logs in Archive storage since most are rarely accessed.

Question 11

A company's engineering organization wants to share operational knowledge across teams using a 'golden path' — a recommended, pre-configured set of tools, services, and templates that makes the easy path also the correct path. Which Google Cloud concept supports this practice?

Accepted Answer

Use Terraform blueprints, organization policies, and Cloud Foundation Toolkit to create pre-configured landing zones that enforce standards automatically.. The Cloud Foundation Toolkit (CFT) provides Terraform blueprints and pre-configured landing zones that enforce organizational policies and standards automatically. This aligns directly with the 'golden path' concept by making the easy path (using the blueprints) also the correct path (enforcing compliance and best practices through organization policies and automated deployments).

Answer

Create a shared Google Slides presentation documenting best practices for teams to reference.

Answer

Grant all teams Organization Admin access so they can configure resources however they prefer.

Answer

Hire a dedicated cloud architect to review every new project's design before it starts.

Question 12

A company's cloud team is asked to demonstrate that their infrastructure changes are repeatable and auditable. They use Terraform configuration files committed to a Git repository to define all cloud resources. Which operational practice does this exemplify?

Accepted Answer

Infrastructure as Code (IaC) managed through version control, providing repeatable and auditable infrastructure changes. By storing Terraform configuration files in a Git repository, the team treats infrastructure definitions as code, enabling version control, peer review, and a complete audit trail of changes. This is the core principle of Infrastructure as Code (IaC), which ensures that every infrastructure change is repeatable because the exact same configuration can be applied multiple times, and auditable because Git history records who changed what and when.

Answer

Manual change management, where each infrastructure change is recorded in a spreadsheet for audit purposes

Answer

Disaster recovery planning, using configuration files to document what needs to be rebuilt after a failure

Answer

Cost optimization, by defining infrastructure in code to enable automatic right-sizing of resources

Question 13

A product team is discussing how to handle a planned 48-hour maintenance window for a critical customer-facing service. The SRE team argues the maintenance window is unnecessary with proper cloud architecture. Which cloud capability eliminates the need for planned downtime maintenance windows?

Accepted Answer

Zero-downtime deployment strategies like rolling updates and blue/green deployments, combined with cloud live migration for infrastructure maintenance. Cloud platforms like Google Cloud support zero-downtime deployment strategies (rolling updates, blue/green deployments) and live migration for infrastructure maintenance. Live migration transparently moves running VMs between hosts without interrupting the OS or applications, while blue/green deployments allow traffic to be switched to a fully updated environment before the old one is taken down. Together, these capabilities eliminate the need for planned downtime maintenance windows entirely.

Answer

Longer maintenance windows scheduled during off-peak hours to minimize customer impact

Answer

Notifying customers in advance of the maintenance window and offering service credits for the downtime

Answer

Backing up all data before the maintenance window to ensure recovery if something goes wrong

Question 14

An operations team tracks the following metrics for their customer portal: request latency p99, error rate, and requests per second. In Site Reliability Engineering terminology, what are these metrics called, and what do they collectively define?

Accepted Answer

Service Level Indicators (SLIs), which measure specific dimensions of service behavior from the user's perspective and collectively define how reliability is quantified. In Site Reliability Engineering (SRE), the metrics p99 latency, error rate, and requests per second are classified as Service Level Indicators (SLIs). SLIs are carefully chosen quantitative measures of specific aspects of the service's behavior, such as availability, latency, or throughput, as experienced by the end user. Collectively, these SLIs define how reliability is quantified and are used to set and monitor Service Level Objectives (SLOs).

Answer

Key Performance Indicators (KPIs) that define the overall health of the business

Answer

Service Level Agreements (SLAs), defining the contractual commitments made to customers

Answer

Operational metrics that are only relevant to the infrastructure team and not to business stakeholders

Question 15

A company's cloud costs have grown faster than its business. The FinOps team is implementing cloud cost governance. Which practice most effectively ensures that individual teams are accountable for their cloud spending?

Accepted Answer

Implementing consistent resource labeling and chargeback reporting so each team's cloud spending is visible and attributed to them. Implementing consistent resource labeling and chargeback reporting directly enables cost attribution to individual teams. In Google Cloud, labels are key-value pairs attached to resources, and when combined with billing export to BigQuery, they allow granular cost breakdowns per team. This creates clear accountability by making each team's spending visible and chargeable back to their budget, which is the core principle of cloud cost governance.

Answer

Requiring all teams to use only the cheapest available cloud service options regardless of technical requirements

Answer

Consolidating all cloud accounts under a single centralized IT team that controls all cloud resource creation

Answer

Disabling all non-production environments to eliminate spending outside of production