Module 5: Securing Google Kubernetes Engine: Techniques and Best Practices

Looking for ‘Security Best Practices in Google Cloud Module 5 Answers’?

In this post, I provide complete, accurate, and detailed explanations for the answers to Module 5: Securing Google Kubernetes Engine: Techniques and Best Practices of Course 10: Security Best Practices in Google Cloud – Preparing for Google Cloud Certification: Cloud Security Engineer Professional Certificate.

Whether you’re preparing for quizzes or brushing up on your knowledge, these insights will help you master the concepts effectively. Let’s dive into the correct answers and detailed explanations for each question!

Securing Google Kubernetes Engine: Techniques and Best Practices

Graded Assignment

1. "Kubernetes service account" and "Google service account" are different names for the same type of service account.

  • True
  • False ✅

Explanation:

  • Kubernetes service accounts are used within Kubernetes to grant permissions to pods.
  • Google service accounts are part of Google Cloud IAM and are used to access Google Cloud services.

2. Which ONE of the following is NOT a security best practice on Kubernetes.

  • Restrict access between pods.
  • Upgrade your GKE infrastructure.
  • Disable Workload Identity. ✅
  • Use shielded GKE nodes.

Explanation:

  • Disabling Workload Identity is not a best practice. In fact, enabling Workload Identity is recommended as it allows Kubernetes workloads to access Google Cloud services securely without needing to manage service account keys manually.

3. GKE has logging and monitoring functions built in.

  • True ✅
  • False

Explanation:

  • GKE integrates with Cloud Logging and Cloud Monitoring (formerly Stackdriver).
  • This provides built-in observability for logs, metrics, and events out of the box.

Leave a Reply