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 company manages multiple Linux Compute Engine instances across several Google Cloud projects. Currently, SSH access is granted by manually adding public SSH keys to project-wide and instance-level metadata. As the engineering team grows, managing individual keys and revoking access for departing employees has become difficult.
You need to implement a centralized solution that links SSH access directly to users' Google Cloud IAM identities and eliminates the need to manage public SSH keys in metadata.
Which solution should you implement?
Cloud Key Management Service (Cloud KMS) is designed to manage cryptographic symmetric and asymmetric encryption keys for data encryption and signing. Bare Metal Solution is a specialized environment for running specialized hardware (like Oracle databases) on bare-metal servers with serial console access.
You were configuring out-of-band administrative serial console access for specialized Bare Metal Solution hardware servers running supported enterprise workloads.
Storing SSH keys in project-wide metadata makes those public SSH keys available to all Linux virtual machine instances in the project that have not explicitly blocked project-wide SSH keys. Granting the Service Account User (roles/iam.serviceAccountUser) role allows identities to run operations or attach service accounts to resources.
Service Account User role does not grant or govern SSH login privileges.block-project-ssh-keys is configured.You needed a quick, legacy method to grant temporary developer access across an entire test project without requiring OS Login configuration or Cloud Identity integration.
OS Login is a Google Cloud feature that manages SSH access to Linux Compute Engine instances using Identity and Access Management (IAM) and your organization's directory services, eliminating the need to manually store and distribute individual SSH keys in metadata.
enable-oslogin=TRUE in project or instance metadata, Google Cloud automatically links a user's Linux user profile to their Google Cloud IAM identity.sudo privileges) and Compute OS Login (grants standard user access). When a user leaves the organization and their IAM account is deactivated or roles are revoked, their SSH access across all instances is terminated immediately.sudo) access purely through IAM role bindings.Compared to legacy metadata-based SSH key management, OS Login eliminates configuration sprawl, prevents stale keys from lingering on servers, and aligns virtual machine access directly with enterprise identity governance.
Adding SSH keys to instance-specific metadata configures local user accounts and authorized keys for only that particular Compute Engine instance. The Compute Instance Admin (v1) (roles/compute.instanceAdmin.v1) role gives full control over instance lifecycle operations such as starting, stopping, and editing VM configurations.
Compute Instance Admin (v1) provides broad administrative control over virtual machine configurations and disks, violating the principle of least privilege merely to allow remote terminal access.You had an isolated, single standalone VM that required custom, one-off public key access for an external contractor who does not have a Google Cloud IAM identity.
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