Connecting to SQL Server on Compute Engine via RDP

ACE By islever Editorial Last updated

Planning and implementing compute resources.

Short answer

B Set a Windows username and password in the GCP Console and use a local RDP client to log in, as the console button does not support direct credential entry.

Question

You created an instance of SQL Server 2017 on Compute Engine to test features in the new version. You want to connect to this instance using the fewest number of steps. What should you do?
  1. Install a RDP client on your desktop. Verify that a firewall rule for port 3389 exists.
  2. Install a RDP client in your desktop. Set a Windows username and password in the GCP Console. Use the credentials to log in to the instance. Correct Answer
  3. Set a Windows password in the GCP Console. Verify that a firewall rule for port 22 exists. Click the RDP button in the GCP Console and supply the credentials to log in.
  4. Set a Windows username and password in the GCP Console. Verify that a firewall rule for port 3389 exists. Click the RDP button in the GCP Console, and supply the credentials to log in.

Key Takeaways

The exam tests the distinction between downloading an RDP configuration file and establishing a direct connection; the trap is assuming the console's RDP button allows password input without a local client.

This question addresses the most efficient method to connect to a Windows instance running SQL Server on Google Cloud Platform using Remote Desktop Protocol (RDP). It clarifies that while the GCP Console provides an RDP button, it does not support direct credential entry for immediate session establishment.

Common mistake: Candidates frequently select Option D because they assume the 'RDP button' in the GCP Console initiates a web-based RDP session where credentials can be entered directly, ignoring the requirement for a local RDP client.

Expert Analysis

Why the Answer Is Correct

Option B is the correct choice because it accurately reflects the technical reality of connecting to a Windows VM on Compute Engine with the fewest steps involving standard tools. While the prompt mentions 'fewest number of steps,' the critical constraint is the mechanism of connection. Setting the password in the console is mandatory if not done at creation, and using a local RDP client (or Chrome extension) is the standard, supported way to establish the session. The 'steps' refer to the administrative actions required: setting credentials and launching the client.

Why the Other Options Are Wrong

Option A is incomplete because it omits the crucial step of setting the Windows username and password, which is required for authentication. Option C is incorrect because port 22 is used for SSH, not RDP (which uses port 3389), and it falsely claims the console button accepts credentials. Option D is the most common distractor; clicking the 'Connect' > 'RDP' button in the GCP Console typically opens a tab that instructs you to download an.rdp file or use a local client, rather than providing an interactive login form for credentials within the browser interface itself.

Community Comment Notes

Community feedback highlights this exact ambiguity. As user vnxt noted, "RDP is enabled by default... Just make sure you install an RDP client... and set windows password," supporting B. User obeythefist tested this and confirmed, "When you click the RDP button, you are asked to install a client or use the Windows RDP client... There is no option to enter credentials." This consensus confirms that D describes a workflow that does not exist as stated.

Official Reference

https://cloud.google.com/compute/docs/instances/connecting-to-windows

This link opens the official vendor documentation in a new tab.

Exam Strategy

Always verify the specific capabilities of the GCP Console UI when questions involve 'direct' connections. If an option implies a feature (like web-based RDP credential entry) that requires additional software or downloads, it is likely incorrect compared to the standard client-based approach.

Frequently Asked Questions

Why doesn't the GCP Console RDP button allow direct login?

The button triggers a download of an RDP config file or redirects to instructions for using a local client; it does not host an interactive RDP session in the browser.

Is port 22 used for RDP connections to Windows?

No, port 22 is for SSH (Linux). RDP uses port 3389, which must be open in the firewall rules.

More ACE FAQ →

Community Votes

B
65%
C
10%
D
25%

65% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 193 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 30 of 193

  1. ankit89 👍 35
    D seems more correct
  2. UtsavDM 👍 27
    No, we can't connect using RDP directly in the GCP console. When we click on it, it asks us to install RDP client. So ultimately, B is more accurate.
  3. pas77 👍 23
    Obviously, B is not the answer because you have to install an RDP client which is an extra step. D is the answer because you can connect directly using the RDP button in the GCP console.
  4. obeythefist 👍 22
    I tested this on on Compute Engine today by deploying a new instance. D is not correct. When you click the RDP button, you are asked to install a client or use the Windows RDP client if you are running Windows. There is no option to enter credentials or get an RDP session through the web interface.
  5. jabrrJ68w02ond1 👍 20
    Tested it myself. At least on my Machines, I was asked to First install a RDP Client.
Show 25 more comments
  1. someoneinthecloud 👍 8
    B is the correct answer. A is incomplete, C is wrong (TCP 22 is SSH and we need to use RDP) and D, although it seems correct, has a incorrect step (clicking on RDP button in the GCP doesn't allow me to provide an user/password combination, what it does is to allow me to download the rdp config file and with that, I can use it to configure a RDP client to connect to the VM). Only B makes sense (even with some steps not mentioned)
  2. Khaled_Rashwan 👍 6
    D is correct A is wrong because: as long as there is a choice mentioning setting a password, then we should not consider that the password is already set C is wrong because: port 22 for ssh and do not help in our situation B & D are initially right answers but D is easier as long there is no need to install RDP client as per google docs.: https://cloud.google.com/solutions/chrome-desktop-remote-windows-compute-engine#connect_with_rdp
  3. eledu1985 👍 6
    In the link you provided the first step is to verify firewall rule was created, even if it is the default option!, so D is the most accurate even by the link.
  4. spudleymcdudley 👍 5
    D - From Google documentation "Before you connect using the Microsoft Remote Desktop Connection app, make sure that one of the following prerequisites is met: Your VM instance has a public IP address and your firewall rules allow TCP ingress traffic from your client's public IP address to the instance by using port 3389. Your local network is connected to your VPC by using VPN or Cloud Interconnect and your firewall rules allow TCP ingress traffic from your client's private IP address to the instance by using port 3389." - https://cloud.google.com/compute/docs/instances/connecting-to-instance#remote-desktop-connection-app
  5. someaccount25 👍 5
    My ans is B. If you click RDP button, you can see this message: Use a remote desktop protocol (RDP) client to connect to this instance. If you are running Windows on your local machine, use Remote Desktop Connection. Other operating systems might require you to use third-party software. The first time you connect, enter the username and password that you provided when you created the instance. Note: You must configure the network firewall to open TCP port 3389 to enable RDP access. Download the RDP file if you will be using a 3rd-party client. You can not connect and login to windows os from console.
  6. KC_go_reply 👍 5 Answered B
    I first thought it was D. Then, I tried in out in Compute Engine. After you create a Windows VM instance, port 3389 should be open. You then must set user name and password for RDP. The actual point here is the RDP button. When you click it, you just get an explanation that you should use a RDP client to connect. So you can´t directly connect to the instance with the RDP button. Therefore, D is wrong, and B is the correct answer.
  7. googlelearning 👍 5
    This is an odd one. Are we assuming the default firewall rules apply to the project that opens RDP? If so then its B, otherwise I would say its D. Make sure the RDP port is open then click set windows password and then click RDP all from the GCP console. No installing of software.
  8. ryumada 👍 5
    The firewall rule for port 3389 is created by default if you create windows server on Compute Engine. So, no need to verify it. https://cloud.google.com/compute/docs/instances/connecting-to-windows#before-you-begin
  9. waqas 👍 5
    D is the Answer. B is incorrect because even though installing an RDP client and setting the username and password will allow access, it misses setting a firewall rule for port 3389(RDP).
  10. XRiddlerX 👍 4
    B is correct. A (incorrect) - By default, 3389 is a firewall rule that is created. No need to verify it B (correct) - The only steps you need to perform to connect is install an RDP client locally, set the Windows Password, and use the creds to login. C (incorrect) - RDP communicates of 3389 and not 22. Port 22 is reserved for SSH D (incorrect) - By default, 3389 is a firewall rule that is created and you don't "supply" the password by clicking the RDP button. When clicking the RDP button, you get the option to download the RDP file to connect.
  11. samvegas 👍 4
    There are 2 assumptions 1> Is RDP Client installed or user is using chrome for RDP Extension. OR 2> Firewall is created (if on Default network then yes it is created) - if not then we need to check that. So its a trade off between either. Since the question says - "You want to verify new features of 2017", so it implicitly means that you have used SQL Server earlier versions may be on GCP or using it so RDP Client is installed on your laptop/computer. So I am voting for D.
  12. lxgywil 👍 4
    I think the answer is "B": #1 - Port 3389 is enabled for SQL Server VM by default (checking it explicitly is yet another step). #2 - You need to have an RDP client (see what happens when you click the "RDP button" without it being installed). #3 - The username & password have to be created in GCP Console (under instance details) in order to access the instance. Now, option A is not applicable because of #3, option C is a mess, and option D - because of #1 and #2.
  13. Buruguduystunstugudunstuy 👍 4 Answered D
    Answer D is the correct answer. This method allows you to set a Windows username and password in the GCP Console, verify that the firewall rule for RDP port 3389 exists, and use the RDP button in the GCP Console to connect to the SQL Server instance with the provided credentials. This method is convenient because it does not require the installation of an RDP client on your desktop. https://cloud.google.com/compute/docs/instances/connecting-to-windows
  14. hasib125 👍 4
    Crosschecked the issue. For me answer is D. By default after create a SQL Server 2017 on Compute Engine the firewall rule for port 3389 did not exists. I had to put 3389 on firewall. Also got an alert to RDP to put 3389 on firewall. Hence the right answer is : D
  15. kopper2019 👍 4
    that is correct default VPC has ssh and rdp open but what I created a custom VPC as maddy says you need yo to do both steps, even when D has more steps is the way to go to connect to Widnows VMs
  16. zukko78 👍 4
    according to LAB GSP093, for me correct B
  17. obeythefist 👍 3
    A. (Wrong). Install RDP and verify port 3389. Why wrong? You must also set a password in the VM before you can connect. B. (Correct). Everything in this response is what you must do to connect. There is some confusion about "installing an RDP client". Yes, Windows has one already, but other OS clients don't. When you click the RDP button in the Compute Engine console, it tells you to install RDP. By default in a new project, when you stand up a new instance, the firewall rule for 3389 is there. C. (Wrong). Make sure port 22 is in the firewall? Wrong! Port 22 is for SSH, not RDP. Thanks for the comedy answer, Google! D. (Wrong). Windows user name and password is needed. You don't need to check port 3389, it's open by default in a new environment (but a useful step). Where this is wrong is that clicking the RDP button does not take you to a remote desktop, it pops up a message telling you to install an RDP client then connect to the public IP for the instance.
  18. Suryas_One 👍 3
    In general, both B and D options are correct. But, as per the question we need to identify which one has a minimum number of steps involved. As per Google documents, when you create a Windows Instance, the RDP Port 3389 is enabled by default, so here we need not check for this PORT status. Therefore answer is B. Here is a reference from GCP Documents "Be sure the VM allows access through Remote Desktop Protocol (RDP). By default, Compute Engine creates firewall rules that allow RDP access on TCP port 3389. Verify that these firewall rules exist by visiting the firewall rules page in the Google Cloud console and looking for firewall rules that allow tcp:3389 connections."
  19. bamosk 👍 3 Answered B
    https://cloud.google.com/compute/docs/instances/connecting-to-windows#connect_to_windows_vms_by_using_rdp ^^ States :Use native RDP client to connect to the Windows instance such as the Microsoft Remote Desktop Connection app. THere is no mentioning of RDP from GCP Console. Scroll down to RDP to Windows server section on this page: https://www.cloudskillsboost.google/focuses/560?parent=catalog you will see options for RDP (windows), RDP (chrome plugin) , RDP (mac client). Firewall rule is automatically created for port 3389
  20. thewalker 👍 3 Answered B
    B + D. In B, Verify that a firewall rule for Port 3389 exists - is missing. in D, Install a RDP client in your desktop - is missing. Going with B as 3389 port should be enabled to connect to a Windows Instance. However, the step of installing the RDP client is important and by clicking on RDP button in the GCP Console will let you download the <instance name>.rdp file which is a shortcut to open the Windows VM instance using RDP / mstsc.
  21. cloudguy1 👍 3
    B) makes the most sense. You DO need some kind of a client or extension to connect through RDP and you DO need to create the credentials for Windows. Yes, you also do need to have the TCP port 3389 open for RDP, but unless you deleted or overridden it (and the question does not suggest anything of this sort), it should still be there - so that's just an additional, unnecessary step.
  22. jcloud965 👍 3
    D is correct because even if the default firewall is open on 3389, it may have been changed. B : Similar to D but installing a RDP client is an unnecessary step when you can connect from Chrome C : RDP works with port 3389. SSH is on port 22. A : generating a Windows password is mandatory to connect
  23. INASR 👍 3
    It is D , when you click on RDP , it asks you for username and password , so you need to set these credentials, make sure port is open and then clock connect . Even if you download RDP client, you still need to download the RDP file from the console and this is more steps to do.
  24. leba 👍 3
    Correct answer is A as it mentions fewest number of steps to connect to the instance. You can download the RDP Client and verify 3389 firewall is open. If the RDP asks for username and password, the instance is working
  25. ArizonaClassics 👍 3
    D is the most correct answer ( with a deeper look, you will see it comprises both answers from options A & B to give you full troubleshooting tips should your connection fail)

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Single Instance Managed Instance Group Configuration on GCP

S-grade

Authenticating On-Premises Apps to GCP AutoML APIs

S-grade

Consolidating Multi-Project Monitoring in One Stackdriver Dashboard

S-grade

How to Enable Cloud Pub/Sub API for App Engine

S-grade

Practice All ACE Questions

Access 84 questions with complete answers and detailed explanations.

View Full ACE Practice Test →

← Back to ACE Study Guide