Your company is deploying their applications on Google Kubernetes Engine. You want to follow Google-recommended practices. What should you do to ensure that the container images used for new…

Question

Options

• AUse Google-managed base images for all containers.
• BUse Container Analysis to detect vulnerabilities in images.
• CUse an update script as part of every container image startup.
• DUse exclusively private images in Container Registry.

• A
  87% (13)
• B
  7% (1)
• C
  7% (1)

Explanation

Google-managed base images (e.g., from the Google Container Registry or Artifact Registry distroless/official images) are maintained by Google and regularly updated with the latest OS-level security patches. By building your containers on top of these images and rebuilding them when Google publishes updates, your deployments automatically inherit those patches. Option B (Container Analysis) detects vulnerabilities but does not apply patches. Option C (update scripts at startup) violates container immutability best practices and is unreliable. Option D (private images only) controls image source but does not guarantee patch currency.

No community discussion yet for this question.