MENU
You are setting up a Windows VM on Compute Engine and want to make sure you can log in to the VM via RDP. What should you do?
Suggested Answer: B
Get Premium Associate Cloud Engineer Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
You can generate Windows passwords using either the Google Cloud Console or the gcloud command-line tool. This option uses the right syntax to reset the windows password.
gcloud compute reset-windows-password windows-instance
36 comments · newest first
KI
Kimbery
10 months ago
Why would you need a JSON key for RDP? That seems unnecessary.
AN
Antonio
10 months ago
Wait, can you really use Google Account credentials? Sounds off.
LA
Laurel
10 months ago
You need to use gcloud compute reset-windows-password for RDP access.
LY
Lynsey
11 months ago
Totally agree, option B is the way to go!
HA
Hana
11 months ago
I think option C is a bit risky, better stick with B.
MA
Matthew
11 months ago
I’m confused about the service account part in option D. I don’t recall needing a JSON key just to log in via RDP.
TR
Tracey
11 months ago
I practiced a similar question, and I think it was about retrieving credentials after the VM is created. That makes me lean towards option B again.
DO
Dominic
11 months ago
I'm not entirely sure, but I feel like we talked about using metadata for setting up Windows VMs. Could option C be a possibility?
CA
Carey
12 months ago
I think I remember that you need to use gcloud to reset the password for Windows VMs, so maybe option B is correct?
EU
Eulah
12 months ago
I think the key here is that we're setting up a Windows VM, so the standard Google Account login won't work. Based on that, I'd say option B is the way to go - using the gcloud compute reset-windows-password command to retrieve the correct login credentials.
HO
Hobert
1 year ago
I'm a little confused by this question. Wouldn't option A work, where we just use our Google Account credentials to log in? I'm not sure why we'd need to do anything special to set up the login. Let me think about this a bit more.
TR
Trinidad
1 year ago
Option C sounds like the easiest approach to me. That way, we can just set the password when we create the VM, and then use that to log in. I feel pretty confident that this is the right solution.
KE
Kenneth
1 year ago
Hmm, I'm not sure about this one. I know we need to set up the login credentials, but I'm not familiar with the gcloud command. Maybe C would work, where we add the password as metadata when creating the VM?
RE
Regenia
1 year ago
I think the answer is B. Using the gcloud compute reset-windows-password command seems like the best way to retrieve the login credentials for the Windows VM.
DA
Dana
1 year ago
Option C is genius! Hiding the password in the metadata? It's like a digital version of that old trick of writing the combination on the back of the lock.
LI
Lili
1 year ago
Option B all the way! Gcloud to the rescue! It's like having a personal butler who knows all your passwords and is totally cool with sharing them.
RI
Ria
1 year ago
Ria: Definitely, it's like having a password manager built right in.
CY
Cyril
1 year ago
Cyril: I agree, using gcloud makes it so easy to manage passwords.
ST
Stanford
1 year ago
B) After the VM has been created, use gcloud compute reset-windows-password to retrieve the login credentials for the VM.
CA
Carman
1 year ago
Option A? Really? Using my Google Account credentials? Might as well just give the VM my social security number and the keys to my house.
MI
Michal
1 year ago
D) After the VM has been created, download the JSON private key for the default Compute Engine service account. Use the credentials in the JSON file to log in to the VM.
VA
Valentin
1 year ago
C) When creating the VM, add metadata to the instance using 'windows-password' as the key and a password as the value.
IR
Ira
1 year ago
B) After the VM has been created, use gcloud compute reset-windows-password to retrieve the login credentials for the VM.
JA
Jaime
1 year ago
Downloading the JSON private key? Seriously? That's like trying to hack into the Pentagon with a paper clip and a rubber band.
GO
Goldie
1 year ago
B) After the VM has been created, use gcloud compute reset-windows-password to retrieve the login credentials for the VM.
MI
Miesha
1 year ago
C) When creating the VM, add metadata to the instance using 'windows-password' as the key and a password as the value.
AL
Aliza
1 year ago
A) After the VM has been created, use your Google Account credentials to log in into the VM.
LA
Laurene
1 year ago
Hmm, that's interesting. I'll have to look into that option as well. Thanks for sharing your perspective, Shantay.
DA
Daniel
2 years ago
Option C is the winner! I love the idea of setting the password as metadata. It's like hiding the key under the doormat, but digital.
EV
Evangelina
1 year ago
D) After the VM has been created, download the JSON private key for the default Compute Engine service account. Use the credentials in the JSON file to log in to the VM.
BA
Barb
1 year ago
C) When creating the VM, add metadata to the instance using 'windows-password' as the key and a password as the value.
BA
Barney
1 year ago
B) After the VM has been created, use gcloud compute reset-windows-password to retrieve the login credentials for the VM.
ED
Edna
1 year ago
A) After the VM has been created, use your Google Account credentials to log in into the VM.
SH
Shantay
2 years ago
I disagree, I believe the answer is B. Using gcloud to reset the Windows password after VM creation makes more sense to me.
TR
Truman
2 years ago
Option B seems like the way to go. I mean, who wants to use their Google Account credentials to log into a VM? That's just asking for trouble.
LA
Laurene
2 years ago
I think the answer is C. Adding metadata with the password during VM creation seems like the right way to go.