PCDOE Matching — 10 Questions

Question 1

Match each Google Cloud tool to its function in incident management.

Accepted Answer

Cloud Logging: Collect and store log data from applications and services.. In incident management, Cloud Logging collects logs, Cloud Monitoring provides metrics and alerts, Error Reporting aggregates errors, and Cloud Trace traces requests. Common confusions include mixing Cloud Logging with monitoring or debugger functions.

Answer

Cloud Logging: Provide visibility into performance and health.

Answer

Cloud Debugger: Store and analyze logs.

Question 2

Match each Kubernetes resource to its role in a DevOps pipeline.

Accepted Answer

Pod: Smallest deployable unit, runs containers.. Key Kubernetes objects for application management. Pod runs containers, Deployment manages replicas and updates, Service provides stable networking, ConfigMap stores non-sensitive configuration, and Ingress controls external HTTP access.

Answer

Pod: Provides stable IP and DNS for a set of pods.

Answer

Deployment: Stores configuration data as key-value pairs.

Answer

ConfigMap: Manages external HTTP access to services.

Question 3

Match each monitoring concept to its purpose.

Accepted Answer

Latency: Time taken to serve a request. The four golden signals are Latency, Traffic, Errors, and Saturation. Correct matches are A, B, C, D. Common confusions swap Error and Traffic definitions.

Answer

Latency: Rate of failed requests

Answer

Errors: Demand placed on the system

Question 4

Match each SRE term to its description.

Accepted Answer

SLI: A carefully defined quantitative measure of some aspect of the level of service.. The correct matches are: SLI with a quantitative measure, SLO with a target value, SLA with a contract including consequences, and Error Budget with remaining unreliability. Common confusions include swapping Error Budget with SLI or confusing SLO with SLA.

Answer

SLI: The acceptable amount of unreliability remaining before the SLO is violated.

Answer

SLO: A contract with users that includes consequences.

Question 5

Match each CI/CD concept to its definition.

Accepted Answer

Continuous Integration: The practice of frequently merging code changes into a shared repository, verified by automated builds and tests.. Continuous Integration focuses on frequent merging and automated testing; Continuous Delivery extends to staging deployment with manual production release; Continuous Deployment automates production releases. Common confusions arise from mixing these definitions.

Answer

Continuous Integration: The practice of automatically deploying code to production after each change.

Answer

Continuous Delivery: The practice of merging code changes frequently into a shared repository.

Question 6

Match each Cloud Monitoring metric type to its description.

Accepted Answer

Gauge: A metric that measures a value at a specific point in time.. The correct matches are: Gauge measures a point-in-time value, Cumulative measures accumulated value over time, and Delta measures rate of change. Common confusions include swapping definitions between gauge and cumulative, or misunderstanding delta as cumulative.

Answer

Gauge: A metric that measures an accumulated value over time.

Answer

Cumulative: A metric that measures a value at a specific point in time.

Answer

Delta: A metric that measures an accumulated value over time.

Question 7

Match each Google Cloud service to its primary purpose.

Accepted Answer

Cloud Build: Continuous integration/continuous delivery platform. The correct matches are: Cloud Build for CI/CD, Cloud Source Repositories for Git hosting, Cloud Functions for event-driven serverless functions, and Cloud Run for serverless containers. Common confusions include swapping the purposes of Cloud Build and Cloud Source Repositories.

Answer

Cloud Build: Private Git repository hosting

Answer

Cloud Source Repositories: Continuous integration/continuous delivery platform

Question 8

Match each Google Cloud deployment strategy to its description.

Accepted Answer

Blue/green deployment: Running two identical environments, only one serves traffic at a time.. Blue/green uses two environments, canary uses a small user subset, rolling updates gradually. Swapping definitions is a common distractor.

Answer

Blue/green deployment: Gradually replacing instances of the current version with the new one.

Answer

Canary deployment: Running two versions side-by-side and routing users based on test groups.

Answer

Rolling deployment: Switching traffic between two separate environments.

Question 9

Match each Google Cloud DevOps capability to its benefit.

Accepted Answer

Cloud Build: Automates build, test, and deployment. Cloud Build automates CI/CD pipelines, and Artifact Registry stores build artifacts. Common confusions involve mixing capabilities like monitoring (Cloud Monitoring) or source code management (Cloud Source Repositories) with other tools.

Answer

Cloud Build: Monitors application performance

Answer

Cloud Deploy: Manages source code repositories

Answer

Cloud Monitoring: Provides continuous delivery pipelines

Question 10

Match each cost optimization practice to its description.

Accepted Answer

Committed Use Discounts: Discounts for committing to use a certain amount of resources for 1 or 3 years.. Common cost management techniques on Google Cloud include Committed Use Discounts (long-term commitment savings), Preemptible VMs (short-lived cheaper instances), Sustained Use Discounts (automatic monthly usage discounts), and Custom Machine Types (tailored VMs). The distractors swap definitions between related practices.

Answer

Committed Use Discounts: Short-lived, lower-cost instances that can be terminated at any time.

Answer

Preemptible VMs: Discounts for committing to use a certain amount of resources for 1 or 3 years.