Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Associate Cloud Engineer practice bank has an additional 2,014 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
Your organization wants to simplify SSH access management across multiple Compute Engine Linux instances in a Google Cloud project. Currently, team members manually add individual SSH public keys to project and instance metadata, leading to administrative overhead and access management challenges.
You need to transition the environment to centralized identity-based access by enabling OS Login across all instances in the project.
What should you do, and what happens to metadata-stored SSH keys once this configuration is applied?
This option suggests setting the enable-oslogin metadata key to FALSE, which explicitly turns off or disables the OS Login feature across the project.
enable-oslogin to FALSE leaves instances in legacy metadata-based SSH mode. It does not enable centralized identity management.~/.ssh/authorized_keys. Instead, when enabled, Compute Engine configures OpenSSH to query user profiles and SSH keys dynamically via the metadata server and NSS/PAM modules.enable-oslogin to FALSE forces instances to rely entirely on manual public SSH keys stored in project or instance metadata.authorized_keys file or disabling OS Login removes centralized IAM governance over SSH logins.You wanted to deliberately disable OS Login across an entire project to revert back to legacy metadata-based SSH key management.
This option suggests using an invalid metadata key name (os-login-enabled) and proposes that Compute Engine combines legacy metadata keys with identity profiles.
enable-oslogin. Using an invalid key name like os-login-enabled will be treated as an arbitrary custom metadata key and will fail to activate the OS Login service.This option would only be valid if Google Cloud used os-login-enabled as the official system attribute and implemented a hybrid fallback mechanism that imported existing metadata keys directly into user identity records.
This option describes treating enable-oslogin as a container for SSH public key strings while bypassing Cloud IAM role evaluations.
enable-oslogin is a boolean flag that expects a value of TRUE or FALSE. It is not a key repository for storing SSH key data.roles/compute.osLogin or roles/compute.osAdminLogin, not by pasting public keys into configuration flags.enable-oslogin will not configure the underlying PAM/NSS modules properly.Google Cloud required administrators to manually map individual public keys to custom metadata attributes rather than using centralized user profiles and IAM roles.
OS Login is a Google Cloud feature that links Linux user accounts directly to Google identities (Google Workspace, Cloud Identity, or standard Google accounts). Instead of manually provisioning and managing local SSH keys on virtual machines or across project metadata, access is controlled centrally using Identity and Access Management (IAM) roles.
enable-oslogin to TRUE at the project level automatically activates OS Login for all Compute Engine instances within that project (unless explicitly overridden by instance metadata).roles/compute.osLogin) or Compute OS Admin Login (roles/compute.osAdminLogin).Configuring enable-oslogin=TRUE at the project level provides a single, declarative action that enforces secure identity-based authentication across all current and future VMs in the project, entirely removing the operational overhead of metadata-based SSH key management.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated