Explanation:
To ensure an SSH key works on every instance in the project efficiently, uploading the public key to project metadata (A) is the correct approach. Project metadata applies to all instances in the project, ensuring new instances automatically include the key. Existing instances will inherit the key after a restart. While option D (gcloud compute ssh) adds the key to individual instance metadata when used, it requires manual or scripted execution for each instance, making it less efficient. Options B (per-instance metadata) and C (custom image) are not scalable or efficient for all instances.
Ultimate access to all questions.
How can you efficiently configure your personal SSH key to work on all instances within your Google Cloud project?
A
Upload your public ssh key to the project Metadata.
B
Upload your public ssh key to each instance Metadata.
C
Create a custom Google Compute Engine image with your public ssh key embedded.
D
Use gcloud compute ssh to automatically copy your public ssh key to the instance.
No comments yet.