GCP Associate Cloud Engineer Practice Question

Your company runs dozens of Linux virtual machines on Compute Engine across several projects. Security policy states that:

  • Each SSH key must be linked to an individual Google Cloud IAM identity.
  • VM administrators must never edit instance or project metadata manually to add or remove keys.
  • When an employee's IAM account is disabled, the employee must instantly lose SSH access to every VM.

Which approach satisfies all of these requirements with the least operational overhead?

  • Store each engineer's public key in project-wide metadata under the ssh-keys field and instruct administrators to remove keys when employees leave.

  • Enable OS Login on every project and grant each engineer the IAM role roles/compute.osLogin (or roles/compute.osAdminLogin). Engineers add their own public key to their OS Login profile and connect with gcloud compute ssh.

  • Create a dedicated service account that holds a single SSH key, grant it the compute.instanceAdmin IAM role, and share the key with all engineers.

  • Ask administrators to append each engineer's key directly to /home/username/.ssh/authorized_keys on every VM using a configuration-management script.

GCP Associate Cloud Engineer
Planning and implementing a cloud solution
Your Score:
Settings & Objectives
Random Mixed
Questions are selected randomly from all chosen topics, with a preference for those you haven’t seen before. You may see several questions from the same objective or domain in a row.
Rotate by Objective
Questions cycle through each objective or domain in turn, helping you avoid long streaks of questions from the same area. You may see some repeat questions, but the distribution will be more balanced across topics.

Check or uncheck an objective to set which questions you will receive.

Bash, the Crucial Exams Chat Bot
AI Bot