Exam Professional Cloud DevOps Engineer All Questions

View all questions & answers for the Professional Cloud DevOps Engineer exam

Exam Professional Cloud DevOps Engineer topic 1 question 156 discussion

Actual exam question from Google's Professional Cloud DevOps Engineer

Question #: 156
Topic #: 1

[All Professional Cloud DevOps Engineer Questions]

Your company runs applications in Google Kubernetes Engine (GKE). Several applications rely on ephemeral volumes. You noticed some applications were unstable due to the DiskPressure node condition on the worker nodes. You need to identify which Pods are causing the issue, but you do not have execute access to workloads and nodes. What should you do?

A. Check the node/ephemeral_storage/used_bytes metric by using Metrics Explorer.
B. Check the container/ephemeral_storage/used_bytes metric by using Metrics Explorer.
C. Locate all the Pods with emptyDir volumes. Use the df -h command to measure volume disk usage.
D. Locate all the Pods with emptyDir volumes. Use the df -sh * command to measure volume disk usage.

Show Suggested Answer

Suggested Answer: B 🗳️

by koo_kai at Oct. 28, 2023, 8:21 p.m.

Comments

Submit Cancel

dija123

7 months ago

Selected Answer: B

The container/ephemeral_storage/used_bytes metric seems correct.

upvoted 1 times

...

alpha_canary

10 months ago

Selected Answer: B

https://cloud.google.com/monitoring/api/metrics_kubernetes#:~:text=container/ephemeral_storage/used_bytes The container/ephemeral_storage/used_bytes metric can help you identify which pods are consuming ephemeral storage and potentially causing the DiskPressure condition. why not A? The node/ephemeral_storage/used_bytes metric would show the total ephemeral storage used on a node, but it wouldn't help you identify which pods are consuming the storage.

upvoted 2 times

...

xhilmi

1 year ago

Selected Answer: B

To identify which Pods are causing the DiskPressure node condition due to ephemeral volumes, you should check the container/ephemeral_storage/used_bytes metric using Metrics Explorer. Therefore, the correct answer is B. This metric provides information about the ephemeral storage usage of containers within Pods. By examining this metric, you can identify the specific Pods that are contributing to the DiskPressure condition on the worker nodes. Metrics Explorer allows you to visualize and analyze metrics data, making it a suitable tool for investigating resource usage and identifying potential issues in a GKE environment.

upvoted 2 times

...

nqthien041292

1 year ago

Selected Answer: B

Vote B

upvoted 1 times

...

mshafa

1 year, 1 month ago

Selected Answer: B

This approach provides the necessary detail to identify which Pods are causing the DiskPressure condition without the need for direct access to the nodes or the ability to execute commands on them. Metrics Explorer in Google Cloud's operations suite (formerly Stackdriver) allows you to query and visualize metrics from your GKE environment, making it a powerful tool for this kind of diagnostic task.

upvoted 2 times

...

YushiSato

1 year, 1 month ago

Selected Answer: B

I think the answer is B. You need to use container/ephemeral_storage/used_bytes because you need to identify the pod that is causing the problem. pod/ephemeral_storage/used_bytes also exists, but it is still in beta. https://cloud.google.com/monitoring/api/metrics_kubernetes

upvoted 3 times

...

macqly

1 year, 1 month ago

Why not B?

upvoted 1 times

...

khoukha

1 year, 1 month ago

A: node/ephemeral_storage/used_bytes GA Ephemeral storage usage GAUGE, INT64, By k8s_node Local ephemeral storage bytes used by the node. Sampled every 60 seconds.

upvoted 1 times

lelele2023

1 year, 1 month ago

why not B though?

upvoted 1 times

...

koo_kai

1 year, 1 month ago

Selected Answer: A

https://cloud.google.com/monitoring/api/metrics_kubernetes

upvoted 1 times

lelele2023

1 year, 1 month ago

why not B though?

upvoted 3 times

...