Discuss Google Professional Cloud Network Engineer Exam Topic 4 Question 108

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?

AUpload your public ssh key to the project Metadata.

BUpload your public ssh key to each instance Metadata.

CCreate a custom Google Compute Engine image with your public ssh key embedded.

DUse gcloud compute ssh to automatically copy your public ssh key to the instance.

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

Get Premium Professional Cloud Network Engineer Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test

33 comments · newest first

Leila 10 months ago

Wait, can you really just upload the key to project Metadata?

Brandon 10 months ago

I think B is better for individual control.

Filiberto 10 months ago

A is the way to go, much easier!

Tamesha 11 months ago

D is pretty cool, but does it really work every time?

Vinnie 11 months ago

C sounds like a lot of extra work, not sure it's worth it.

Lindsey 11 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.

Flo 11 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.

Ivette 11 months ago

I remember practicing a question about SSH keys, and I feel like uploading to each instance Metadata is too tedious.

Alysa 12 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.

Carmela 12 months ago

I'm a bit confused on the differences between the options. I'll need to review the details carefully before deciding.

Vilma 12 months ago

The gcloud compute ssh command sounds interesting. I'll have to look into that option more closely.

Agustin 1 year 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.

Olen 1 year 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?

Kristin 1 year ago

This seems pretty straightforward. I'd go with option A and upload the public key to the project metadata.

Lawanda 1 year ago

I think creating a custom image with the key embedded is the most secure option.

Lynelle 1 year ago

But wouldn't it be easier to just upload it to the project Metadata?

Goldie 1 year ago

I disagree, I believe option D is more efficient.

Lynelle 1 year ago

I think option A is the best choice.

Wayne 1 year 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!

Kina 1 year 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!

Kenny 1 year ago

↳ replying to Kina

C) Create a custom Google Compute Engine image with your public ssh key embedded.

Justine 1 year ago

↳ replying to Kina

B) Upload your public ssh key to each instance Metadata.

Ernest 1 year ago

↳ replying to Kina

A) Upload your public ssh key to the project Metadata.

Lynelle 1 year ago

D seems like the easiest option. Let gcloud do the heavy lifting and copy the key for me. Lazy, but efficient!

Rikki 1 year ago

↳ replying to Lynelle

Yeah, why make it harder for yourself when you can let gcloud handle it with just one command.

Telma 1 year ago

↳ replying to Lynelle

I agree, option D is definitely the most efficient way to go.

Matilda 1 year 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.

Cherry 1 year ago

↳ replying to Matilda

That's a good choice. It's always better to prioritize security when it comes to SSH keys.

Dalene 1 year ago

↳ replying to Matilda

B) Upload your public ssh key to each instance Metadata.

Annett 1 year 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.

Elena 1 year ago

↳ replying to Annett

C) Create a custom Google Compute Engine image with your public ssh key embedded.

Dante 1 year ago

↳ replying to Annett

B) Upload your public ssh key to each instance Metadata.

Pilar 1 year ago

↳ replying to Annett

A) Upload your public ssh key to the project Metadata.

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