Associate Cloud EngineerDemo

By Google · Question Mode

QuestionQ26

Configuring access and security

You are implementing a company-wide standard to control SSH access for your Google Cloud projects. You want to simplify SSH access management to your Compute Engine instances while maintaining audit compliance and eliminating as many manual steps as possible. What should you do?

  • A Configure a service account to add SSH keys for all VMs.
  • B Configure metadata SSH keys to manage sudo access to instances.
  • C Enable OS Login by using an organization policy for each Google Cloud project.
  • D Enable OS Login with two-factor authentication for the domain.
Explanation

Enforcing OS Login through an organization policy (compute.requireOsLogin) across all projects centralizes SSH access management using IAM roles and Cloud Identity, automatically removing the need to manually manage per-instance SSH keys while providing centralized audit logging via Cloud Audit Logs. Managing metadata SSH keys or per-VM service account keys requires manual key distribution and revocation, and domain-wide two-factor OS Login is a narrower, separate control rather than the company-wide policy mechanism being asked for here.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!