Free Google Associate Cloud Engineer Actual Exam Questions - Question 11 Discussion
You want to connect to this instance using the fewest number of steps. What should you do?
D vs B? B skips mentioning firewall rules, which are crucial for RDP access. D explicitly includes setting firewall rules and credentials, making it the more complete choice for fewer steps.
Probably C since port 22 is for SSH, not RDP, so that seems off.
Maybe D, since it includes setting creds and opening the right port for RDP access.
Actually, option D covers all key steps: setting username/password, opening port 3389, and using the RDP button in the console for easiest access. Without the firewall rule, connection won’t work.
B tbh feels overcomplicated because just installing an RDP client and setting a password isn’t enough without opening the correct port. A doesn’t mention setting credentials, so that’s definitely out. C is weird because it talks about port 22, which is SSH, not RDP, so that can’t be right either. D covers setting creds, opening port 3389, and using the RDP button—all necessary for a straightforward connection—so it seems like the most complete choice here.
It’s D since port 3389 is for RDP and setting creds plus firewall rule covers all bases.
Maybe B makes sense too since it focuses on setting the Windows username and password in the console, which is needed for RDP access. Just installing an RDP client and opening port 3389 is not enough if you don’t have credentials set. Plus, B doesn’t mention verifying the firewall rule explicitly, but that might be assumed since you need port 3389 open to connect remotely. The steps seem fewer compared to D, which explicitly includes verifying the firewall rule, meaning more manual steps. So, B could be the simpler route if GCP handles firewall rules automatically when you set the password.
Option B skips checking firewall rules, which could cause connection issues. Setting credentials and installing an RDP client is necessary but might not guarantee access without opening port 3389, so fewer steps aren’t actually achieved here.
Port 22 is for SSH, so options mentioning it seem off for RDP. Also, just installing a client without setting credentials won't get you in. Does the console’s RDP button really save time over a local client?
Firewall needs port 3389 for RDP, so options mentioning port 22 can be dropped. Also, just installing an RDP client without setting the username/password first won’t work. So it has to be between C and D, but C’s port 22 mention is weird.
Makes sense that D is the way to go since RDP needs port 3389 open and you have to set the username and password to connect properly. The other options either mention port 22, which is for SSH, or miss setting up the credentials, so they wouldn’t work for the easiest connection method here. D covers all bases in one go.
D