Cloud Monitoring overview in GCP - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Cloud Monitoring Metrics

Which of the following best describes what a metric in Cloud Monitoring represents?

A A user account permission setting in Google Cloud.

B A static configuration file that defines alerting policies.

C A log entry generated by an application or system.

D A time series data point that measures a specific aspect of a resource or application over time.

💡 Hint

Think about what Cloud Monitoring tracks continuously to observe system health.

Metrics are numerical data points collected over time that represent the state or performance of resources or applications.

💻 Command Output

intermediate

Interpreting Metric Descriptions

What is the output of the following gcloud command that lists metric descriptors for Compute Engine?

GCP

gcloud monitoring metrics descriptors list --filter="metric.type:starts_with('compute.googleapis.com')" --limit=1 --format="value(displayName)"

A Disk read bytes

B Network received bytes

C CPU utilization

D Instance uptime

💡 Hint

The first Compute Engine metric descriptor in list order is CPU utilization.

The command filters metric descriptors starting with 'compute.googleapis.com' and returns the display name of the first metric, which is typically 'CPU utilization'.

🔀 Workflow

advanced

Creating an Alerting Policy Workflow

Which sequence correctly describes the steps to create an alerting policy in Cloud Monitoring?

A 1,2,3,4

B 2,1,3,4

C 1,3,2,4

D 3,1,2,4

💡 Hint

Think about the logical order from selecting what to monitor to saving the alert.

First, you select the resource and metric, then set the condition threshold, next configure notifications, and finally name and save the policy.

❓ Troubleshoot

advanced

Diagnosing Missing Metrics in Cloud Monitoring

You notice that a custom metric you created is not showing any data points in Cloud Monitoring. Which of the following is the most likely cause?

A The metric descriptor was not created or registered properly.

B The Google Cloud project is deleted.

C The metric data is stored in BigQuery instead of Cloud Monitoring.

D The Cloud Monitoring API is disabled in the project.

💡 Hint

Custom metrics require proper registration before data can be sent.

If the metric descriptor is missing or not registered, no data points can be collected or displayed for that metric.

✅ Best Practice

expert

Optimizing Cloud Monitoring Costs

Which practice helps reduce costs when using Cloud Monitoring for a large number of resources?

A Send metric data to multiple projects to distribute storage.

B Use metric filters to collect only necessary metrics and reduce data volume.

C Enable all available metrics for every resource to ensure full coverage.

D Increase the data retention period to keep all historical data indefinitely.

💡 Hint

Think about how to limit data collection to what is essential.

Filtering metrics to collect only what is needed reduces data ingestion and storage costs effectively.

Practice

1. What is the main purpose of Cloud Monitoring in Google Cloud Platform?

easy

A. To watch and track the health and performance of cloud resources

B. To create virtual machines automatically

C. To store large amounts of data securely

D. To manage user permissions and roles

Solution

1. Step 1: Understand Cloud Monitoring's role

   Cloud Monitoring is designed to observe and report on the status and performance of cloud resources.

2. Step 2: Compare options with this role

   Options B, C, and D describe other services like Compute Engine, Cloud Storage, and IAM, not monitoring.

3. Final Answer:

   To watch and track the health and performance of cloud resources -> Option A

4. Quick Check:

   Cloud Monitoring = watch cloud health [OK]

Hint: Monitoring means watching resource health and performance [OK]

Common Mistakes:

• Confusing monitoring with storage or VM creation
• Thinking monitoring manages user access
• Assuming monitoring creates resources automatically

2. Which command correctly lists all alert policies using the gcloud tool?

easy

A. gcloud alert-policies show

B. gcloud monitoring alerts list

C. gcloud monitoring alert-policies list

D. gcloud monitoring policies get

Solution

1. Step 1: Recall gcloud command structure for alert policies

   The correct command to list alert policies is under 'monitoring alert-policies list'.

2. Step 2: Verify each option's correctness

   gcloud monitoring alert-policies list matches the correct syntax. Options A, B, and D use incorrect verbs or resource names.

3. Final Answer:

   gcloud monitoring alert-policies list -> Option C

4. Quick Check:

   List alert policies = gcloud monitoring alert-policies list [OK]

Hint: Use 'gcloud monitoring alert-policies list' to see alerts [OK]

Common Mistakes:

• Using 'alerts' instead of 'alert-policies'
• Using 'show' instead of 'list' to list policies
• Mixing command verbs and resource names

3. What will be the output of this command?

gcloud monitoring metrics list --filter="metric.type=compute.googleapis.com/instance/cpu/utilization" --limit=1

medium

A. Deletes the CPU utilization metric

B. Shows an error because the filter syntax is wrong

C. Lists all metrics without filtering

D. Lists one metric descriptor for CPU utilization of Compute Engine instances

Solution

1. Step 1: Understand the command components

   The command lists metric descriptors filtered by CPU utilization metric type, limiting output to one.

2. Step 2: Analyze expected output

   The output will show one metric descriptor matching the filter. No deletion or error occurs.

3. Final Answer:

   Lists one metric descriptor for CPU utilization of Compute Engine instances -> Option D

4. Quick Check:

   Filter + limit = one matching metric listed [OK]

Hint: Filter with --filter and limit results with --limit [OK]

Common Mistakes:

• Assuming filter syntax is invalid
• Expecting all metrics without filter
• Confusing list with delete command

4. You tried to create an alert policy with this command:

gcloud monitoring alert-policies create --notification-channels=1234567890 --condition-display-name="High CPU" --condition-filter="metric.type=compute.googleapis.com/instance/cpu/utilization" --condition-threshold-value=0.8

But it failed. What is the likely error?

medium

A. Missing required flag --condition-aggregations

B. Notification channel ID is invalid or missing

C. Condition filter syntax is incorrect

D. Threshold value must be a string, not a number

Solution

1. Step 1: Check notification channel usage

   The notification channel ID must be a valid existing channel; '1234567890' is likely a placeholder or invalid.

2. Step 2: Verify other flags

   Flags like condition filter and threshold value are syntactically correct; aggregation is optional.

3. Final Answer:

   Notification channel ID is invalid or missing -> Option B

4. Quick Check:

   Invalid notification channel causes failure [OK]

Hint: Check notification channel IDs exist before using [OK]

Common Mistakes:

• Assuming aggregation is always required
• Misformatting condition filter
• Using wrong data type for threshold

5. You want to create a dashboard that shows CPU utilization and memory usage for your Compute Engine instances. Which steps should you follow?

hard

A. Use Cloud Console to create a dashboard, add widgets for CPU and memory metrics, then save

B. Run gcloud commands to create a dashboard and add metrics in one command

C. Create alert policies for CPU and memory, then dashboards are created automatically

D. Use Cloud Storage to upload a JSON file with dashboard configuration

Solution

1. Step 1: Understand dashboard creation process

   Dashboards are created in Cloud Console by adding widgets for desired metrics.

2. Step 2: Evaluate options for dashboard creation

   Use Cloud Console to create a dashboard, add widgets for CPU and memory metrics, then save describes the correct manual process. Run gcloud commands to create a dashboard and add metrics in one command is incorrect as gcloud does not support full dashboard creation in one command. Create alert policies for CPU and memory, then dashboards are created automatically confuses alerts with dashboards. Use Cloud Storage to upload a JSON file with dashboard configuration misuses Cloud Storage.

3. Final Answer:

   Use Cloud Console to create a dashboard, add widgets for CPU and memory metrics, then save -> Option A

4. Quick Check:

   Dashboards made via Console with widgets [OK]

Hint: Create dashboards in Console by adding metric widgets [OK]

Common Mistakes:

• Thinking gcloud can create dashboards fully
• Confusing alert policies with dashboards
• Uploading dashboard configs to Cloud Storage