New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Google Professional Cloud Network Engineer Exam - Topic 4 Question 108 Discussion

Actual exam question for Google's Professional Cloud Network Engineer exam
Question #: 108
Topic #: 4
[All Professional Cloud Network Engineer Questions]

You need to ensure your personal SSH key works on every instance in your project. You want to accomplish this as efficiently as possible.

What should you do?

Show Suggested Answer Hide Answer
Suggested Answer: A

Overview By creating and managing SSH keys, you can let users access a Linux instance through third-party tools. An SSH key consists of the following files: A public SSH key file that is applied to instance-level metadata or project-wide metadata. A private SSH key file that the user stores on their local devices. If a user presents their private SSH key, they can use a third-party tool to connect to any instance that is configured with the matching public SSH key file, even if they aren't a member of your Google Cloud project. Therefore, you can control which instances a user can access by changing the public SSH key metadata for one or more instances. https://cloud.google.com/compute/docs/instances/adding-removing-ssh-keys#addkey


by Chau at Jul 03, 2025, 10:31 PM

Limited Time Offer

25%

Off

Get Premium Professional Cloud Network Engineer Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Leila
2 months ago
Wait, can you really just upload the key to project Metadata?
upvoted 0 times
...
Brandon
2 months ago
I think B is better for individual control.
upvoted 0 times
...
Filiberto
2 months ago
A is the way to go, much easier!
upvoted 0 times
...
Tamesha
3 months ago
D is pretty cool, but does it really work every time?
upvoted 0 times
...
Vinnie
3 months ago
C sounds like a lot of extra work, not sure it's worth it.
upvoted 0 times
...
Lindsey
3 months ago
Creating a custom image with the SSH key embedded seems like a good idea, but I wonder if it complicates updates later on.
upvoted 0 times
...
Flo
3 months ago
I’m leaning towards using gcloud compute ssh because it sounds like it would automate the process, but I can't recall if it works for all instances.
upvoted 0 times
...
Ivette
4 months ago
I remember practicing a question about SSH keys, and I feel like uploading to each instance Metadata is too tedious.
upvoted 0 times
...
Alysa
4 months ago
I think uploading the public SSH key to the project Metadata might be the most efficient way, but I'm not entirely sure if it applies to all instances.
upvoted 0 times
...
Carmela
4 months ago
I'm a bit confused on the differences between the options. I'll need to review the details carefully before deciding.
upvoted 0 times
...
Vilma
4 months ago
The gcloud compute ssh command sounds interesting. I'll have to look into that option more closely.
upvoted 0 times
...
Agustin
4 months ago
I think option C might be the way to go. Creating a custom image with the key embedded could save a lot of time in the long run.
upvoted 0 times
...
Olen
4 months ago
Hmm, I'm not sure if that's the most efficient approach. Wouldn't it be better to upload the key to each instance's metadata individually?
upvoted 0 times
...
Kristin
5 months ago
This seems pretty straightforward. I'd go with option A and upload the public key to the project metadata.
upvoted 0 times
...
Lawanda
7 months ago
I think creating a custom image with the key embedded is the most secure option.
upvoted 0 times
...
Lynelle
7 months ago
But wouldn't it be easier to just upload it to the project Metadata?
upvoted 0 times
...
Goldie
7 months ago
I disagree, I believe option D is more efficient.
upvoted 0 times
...
Lynelle
7 months ago
I think option A is the best choice.
upvoted 0 times
...
Wayne
7 months ago
I'm feeling a bit mischievous today, so I'm going to go with option E: tattooing my public key on my forehead. That's efficiency and security all in one!
upvoted 0 times
...
Kina
7 months ago
C is the way to go. Having the key embedded in the image means I don't have to worry about it at all. Set it and forget it!
upvoted 0 times
Kenny
6 months ago
C) Create a custom Google Compute Engine image with your public ssh key embedded.
upvoted 0 times
...
Justine
7 months ago
B) Upload your public ssh key to each instance Metadata.
upvoted 0 times
...
Ernest
7 months ago
A) Upload your public ssh key to the project Metadata.
upvoted 0 times
...
...
Lynelle
7 months ago
D seems like the easiest option. Let gcloud do the heavy lifting and copy the key for me. Lazy, but efficient!
upvoted 0 times
Rikki
5 months ago
Yeah, why make it harder for yourself when you can let gcloud handle it with just one command.
upvoted 0 times
...
Telma
5 months ago
I agree, option D is definitely the most efficient way to go.
upvoted 0 times
...
...
Matilda
7 months ago
I'm going with B. Uploading the key to each instance's metadata might take a bit more time, but it's more secure that way.
upvoted 0 times
Cherry
7 months ago
That's a good choice. It's always better to prioritize security when it comes to SSH keys.
upvoted 0 times
...
Dalene
7 months ago
B) Upload your public ssh key to each instance Metadata.
upvoted 0 times
...
...
Annett
8 months ago
Option A all the way! Uploading the key to the project metadata is the most efficient way to ensure it works across all instances.
upvoted 0 times
Elena
7 months ago
C) Create a custom Google Compute Engine image with your public ssh key embedded.
upvoted 0 times
...
Dante
7 months ago
B) Upload your public ssh key to each instance Metadata.
upvoted 0 times
...
Pilar
7 months ago
A) Upload your public ssh key to the project Metadata.
upvoted 0 times
...
...

Save Cancel