Connecting to SQL Server on Compute Engine via RDP
Planning and implementing compute resources.
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?
Answer
Correct 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.
Community Votes
65% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
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.
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.
Community Discussion (203 comments)
mazindere
👍 1
Selected: B
When you create a Windows Server VM instance in GCP, Google Cloud automatically creates and enables the default firewall rule allowing RDP traffic on TCP port 3389. You do not need to manually verify or configure port 3389, which makes option D contain an unnecessary step.
Mobadarin
👍 1
Selected: D
you need firewall ingress rule for port 3398 in your VPC. It is not created by default.
d5dd70c
👍 1
Selected: D
D looks good
Arghadeep
👍 1
Selected: D
There is no additional need of installing rdp client which makes and b incorrect, you can directly log in from console. And even the firewall rule although it's default should be verified before establishing connections. D is the absolute answer
modaknarayan
👍 2
Selected: D
D. 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. Explanation: For connecting to a SQL Server 2017 instance on Google Cloud Compute Engine using the fewest steps, you can use the RDP (Remote Desktop Protocol) connection, which is supported by default for Windows instances. The steps involved include: Setting a Windows username and password: You need to specify these credentials in the GCP Console to access the instance via RDP. Verifying the firewall rule for port 3389: Port 3389 is the default RDP port, so you need to ensure the appropriate firewall rule is in place. Clicking the RDP button in the GCP Console: Once these settings are configured, you can use the RDP button in the console to connect to the instance. You'll then supply the credentials you set in the console.
zAbuQasen
👍 1
Selected: D
Option D correctly includes: Setting the Windows username and password in the GCP Console. Verifying the firewall rule for port 3389. Using the "RDP" button in the GCP Console to log in, ensuring the fewest number of steps.
mnasruul
👍 1
Selected: B
B is Correct, because not option RDP button at Console GCP https://cloud.google.com/compute/docs/instances/connecting-to-windows#other
mnasruul
👍 1
Currently GCP support RDP Button at VM GCP https://www.google.com/search?sca_esv=636238c710bc0fc7&sxsrf=ADLYWIIE4h1x6wxfcCsUII3wGOJeLC5P5g:1733916710025&q=RDP+button+in+the+GCP+Console&udm=2&fbs=AEQNm0D7Nkus73mDfRiM-qGSEUWUGRlQvLHQV1vCo9BTpxTWdXf_Rth04xNqa7aHoD5yv9G64fmPfTi2VEH1A-4DF7EBxIPcUtslRrL9UyKNDbAjJZ4ogfz78wrk6C3LLbEGPWofK58Izae8SKteGXNQrtJbqmcwjyEKkFlr9j0j3HzRXs7H1iRv67Sx8M7um58mJG883G2H7e0gr16XyhQdWNKiT3YFzA&sa=X&ved=2ahUKEwj00siMz5-KAxUWRmcHHfmvOtYQtKgLegQIFhAB&biw=1920&bih=940&dpr=1.5#vhid=tU0HqiUlxKFSYM&vssid=mosaic
halifax
👍 2
Selected: D
D is correct because B doesn't mention using the RDP button, making the task less efficient. B assumes that you will be forced to implement the second task (install RDP)
Makar
👍 1
D is correct For connecting to a SQL Server instance (which is running on a Windows Server on Google Compute Engine), using Remote Desktop Protocol (RDP) is the standard method.
martin2099
👍 1
D it is the correct for me
rchowra
👍 1
correct answer is D
akki82782
👍 1
Option D is correct because it includes setting up a Windows username and password, verifying that port 3389 is open for RDP in the firewall, and then using the RDP button in the GCP Console to log in, ensuring all necessary steps for a successful connection are completed.
Chetantest07
👍 1
D ... direct connection, no client installation and simplified network configurations
sivakarthick16
👍 1
Selected: D
This option provides a clear set of steps: you set the necessary credentials, ensure the firewall allows RDP traffic, and then use the built-in RDP feature of the GCP Console to connect directly to the instance.
Timfdklfajlksdjlakf
👍 1
Selected: D
Google Cloud Console provides an easy-to-use RDP button that allows you to directly connect to your instance without needing to separately install and configure an RDP client. This reduces the steps required for connection.
kairosfc
👍 1
Selected: D
D is correct
jcloud965
👍 2
Selected: D
Documentation says "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."
BuenaCloudDE
👍 1
I think that the Q already not exist because much easier to do it by CLI and command which provides on created page of SQL instance?
ccpmad
👍 1
who say D, better to change to other cloud. If you click rdp button in gcp windows instance, create username and password to use in a remote desktop software. There is not one of this in gcp console. Yo need something external, like IAP Desktop or de Remote desktop programa in Windows pcs.
sinh
👍 1
Selected: D
The following sites do not describe RDP client installation. https://cloud.google.com/compute/docs/instances/connecting-to-windows
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."
sinh
👍 1
Selected: D
https://cloud.google.com/compute/docs/instances/connecting-to-windows#remote-desktop-connection-app
thewalker
👍 3
Selected: 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.
NoviceNebula
👍 1
Selected: D
I would say D as the question says fewest number of steps. So three steps 1. Set a Windows username and password in the GCP Console. 2. Verify that a firewall rule for port 3389 (RDP) exists. 3. Use the RDP button in the GCP Console to connect to the instance, supplying the credentials for login. In option B it says install RDP client. Which I think not the headache of GCP if you have installed RDP or not.
Evan7557
👍 1
Answer D
ovokpus
👍 1
Selected: D
Given the options: The first option mentions port 22, which is for SSH (used typically for Linux instances) and is irrelevant in this context. The second option matches the typical process of setting a Windows username/password, ensuring the firewall rule, and then using the GCP Console's RDP button. The third option misses the step about setting a Windows username/password. The fourth option involves the manual process of setting up an RDP client and then connecting. Given the emphasis on "fewest number of steps", the best option is: D
YourCloudGuru
👍 1
Selected: D
The correct answer is D. This option does not require you to install any additional software on your desktop, and it allows you to connect to the instance with just a few clicks. The other options are not as good: Option A requires you to install a RDP client on your desktop. Option B requires you to install a RDP client on your desktop and set a Windows username and password in the GCP Console. Option C requires you to set a Windows password in the GCP Console, verify that a firewall rule for port 22 exists, and then click the RDP button in the GCP Console and supply the credentials to log in.
Captain1212
👍 2
Selected: B
B seems more correct because you cannot use rdp by click you have to first install it
Abi143
👍 2
Selected: B
Bi scorrect I just tested it By default port will be active Just set password login with RDP as it will also be present in default on every pc
certified28
👍 2
Selected: B
you cannot connect using RDP from GCP console , you need to install a client first so B is the correct answer, verified it in sandbox
Trivris
👍 2
Answer D is correct. Even if you are asked to install rdp client, the easiest options is to navigate it from Google console rather finding it somewhere. Most of the cloud providers ask these questions for the sake of asking you to use their environment to do everything rather going through third party to install anything.
krishnu123
👍 2
D is the correct answer
Shenannigan
👍 1
Selected: B
Hi all, for those that are selecting D please read or re-read this document: https://cloud.google.com/compute/docs/instances/connecting-to-windows#remote-desktop-connection-app It clearly states that you need a RDP Client You can search the document for "To connect to the remote desktop of a Windows instance, use one of the following procedures." and review the table of options
Praxii
👍 1
Selected: D
The correct answer is D. I tested this today. I clicked on 'RDP' button and this is the message that came. "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" So veryfing 3389 is important. Next, those saying cant connect because third party connection message is coming. Just download the rdp file and it will connect using the app. So, either way you can connect using the button. Don't get confused.
Az900Exam2021
👍 1
This is a tricky question. B - "Install RDP on desktop" is redundant, since by default, it's included in windows D - "Verify 3389 firewall rule" is redundant as well, since 3389/22 port are open by default There is no perfect answer here.
ManvendraYadav
👍 1
I would say B is correct. RDP is enabled by default when you crate a Windows instance (no need to chek on it). Just make sure you install an RDP client ( chrome ext or RDP) and set windows password.
Ashish_Tayal
👍 1
Selected: D
As in production we always use custom VPC and in Custom VPC we have to enable RDP manually. So Port 3389 must be allowed in the firewall rule, so need to check the firewall rule point as well.
KC_go_reply
👍 5
Selected: 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.
chikorita
👍 1
buying this answer
red_panda
👍 1
Selected: D
D is correct. Why would anyone want to install specific software on their laptop, when we are taking a certification on cloud computing and you can achieve the same thing, in half the time?
lights4life
👍 1
Answer: D
Buruguduystunstugudunstuy
👍 4
Selected: 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
Nazz1977
👍 1
Selected: D
I think it is D
mrvergara
👍 2
Selected: D
https://cloud.google.com/compute/docs/instances/connecting-to-windows#before-you-begin
processor
👍 1
Selected: D
I would have say D as if RDP client is already installed, you don't have to do it again. And if it's not you'll be asked too, so that not changes to B, and it's more straight if the client is already installed
Mahesramar
👍 1
B is the right option as per GCP recommendation. https://cloud.google.com/compute/docs/instances/connecting-to-windows#remote-desktop-connection-app
glanshima
👍 1
Selected: B
D is wrong because there is no RDP button in GCP Console. you have to use RDP Client as per "...Then use IAP Desktop (on Windows) or the Google Cloud CLI in combination with an RDP client. For more information, see Microsoft Remote Desktop clients to connect to the Windows instance..." https://cloud.google.com/compute/docs/instances/connecting-to-windows
Buruguduystunstugudunstuy
👍 1
Yes, there is an RDP button in the GCP Console for Windows VMs. You can use this button to open an RDP connection to a Windows VM instance that you created in Compute Engine. The RDP button is available on the VM instances details page in the Cloud Console.
romega2
👍 1
Selected: B
I think it's B
mvk2022
👍 1
Selected: B
Yup, the RDP client is required on the local, without which the file provided by the console is useless. So answer is B.
kar_techie
👍 1
B is correct. I have created a windows instance and by default 3389 port is associated and RDP is enabled. Just to set the username/password on GCP and login to server.
anolive
👍 2
Selected: D
In my simulation was closest D
xxz
👍 1
Selected: D
D is the correct answer. https://cloud.google.com/compute/docs/instances/connecting-to-windows#remote-desktop-connection-app https://cloud.google.com/compute/docs/instances/windows/generating-credentials
eledu1985
👍 1
Selected: D
https://cloud.google.com/compute/docs/instances/connecting-to-windows#before-you-begin
bubidubi
👍 1
I disagree. The Q says that you have just created this VM, which means the FW rules for RDP has also been created. I believe the documentations says it a bit wonky as it is something to check if things aren't working after you've done everything right, as someone could have deleted that rule if this server has been up for a while, rather than having to check this right after you've made a new VM. I'd say B is better answer than D.
leogor
👍 1
B is the answer
hiromi
👍 2
Selected: B
B is correct. From GCP console: "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"
darkroomie
👍 2
Selected: B
Correct answer is B
adil114
👍 1
B- IS A CORRECT ANSWER
iadarsh
👍 1
Selected: D
D is correct because, before login to the instance we must ensure first that the firewall rule is allowing traffic through port 3369, otherwise we will not able to do RDP even we have the credentials.
ale_brd_111
👍 2
Selected: B
Option 2 is correct because: Using the internal IP address is always preferred to going through the Internet using the Public one. Through Internal IP option: Chrome Remote Desktop is a service that lets you remotely access another computer by using a web browser. Chrome Remote Desktop works on Windows, macOS, and Linux and does not require the VM instance to have a public IP address. Before you connect by using Chrome Remote Desktop, make sure that the following prerequisites are met: You've created a Windows account and password on the VM instance. You've installed the Chrome Remote Desktop service on the VM instance. https://cloud.google.com/compute/docs/instances/connecting-to-windows#chrome-remote-desktop
pedro_
👍 2
B and D have incorrect statements. Firewall rule 3389 MUST be explicitly allowed. (B incorrect) and You required either the RDP Chrome extension OR a third party RDP client to use it (D incorrect)
DesoLato
👍 1
So, wich is the correct one?
Gregwaw
👍 1
You need firewall ingress rule for port 3398 in your VPC. It is not created by default.
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.
on2it
👍 2
Selected: B
Iknow it
RanjithK
👍 1
Answer is B. Tried and tested
RanjithK
👍 1
Answer is B
patashish
👍 2
Option D is correct. Difference between B and D is only firewall setting. With default network , firewall rules will come in built to allow access on 3389 But in answer , they have not mentioned either default or custom network. We do not know if its changed. Better to cross check rules , add/edit if required Hence , as per my view D is correct answer.
AzureDP900
👍 2
Bis the correct answer.
bamosk
👍 3
Selected: 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
jagopi9381
👍 2
Selected: B
VOTE FOR B
kreeo
👍 1
Selected: D
firewall rule for port 3389 is needed.
WillPaaS
👍 1
Selected: D
A (incorrect ) Username and password need to be set B (incorrect ) RDP client Installation is not necessary C (incorrect ) no need to check port 22
denkyira
👍 1
C 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).
sedado77
👍 2
Selected: B
B is correct, as D promps you to use an installed RDP, which is not assumed. So go for B.
wjtb
👍 1
Selected: B
B is correct, you cannot connect through RDP without an RDP client.
jeet_geet
👍 2
GO WITH "B". THIS WAS THERE IN EXAM.
Mathiiii
👍 1
Selected: D
I suggest D
LaxmanTiwari
👍 1
B is the correct answer
Namenick10
👍 1
Selected: B
B seems correct
yashSai
👍 1
B is correct
svsilence
👍 1
ok RDP default open on VPC but D just "verify" not say "go add rule". so i think answer D is correct.
BenKenGo6
👍 1
Selected: B
It's B Connect to the VM instance by using RDP: 1. In the Cloud console, go to the VM instances page. 2. Make sure a green check mark check is displayed next to the name of your crdhost instance, indicating that the instance is ready. 3. Click the instance name crdhost to open the VM instance details page. 4. Under Remote access, click Set Windows password, and then click Set to create your account on the remote machine. This step generates a password for you. Make a note of the password or copy it to a secure temporary file. 5. To connect to the remote instance, click the arrow arrow_drop_down next to the RDP button, and then select Download the RDP file. You can open the RDP file by using your preferred RDP client. 6. When your RDP client prompts for a password, enter the password that you generated earlier. https://cloud.google.com/architecture/chrome-desktop-remote-windows-compute-engine#interactive_installation_using_rdp
jgnogueira
👍 1
Selected: D
These steps are necessary, to connect on windows instances 1 Set Password 2 Firewall rule 3389 3 And connect on RDP button or client
nick68
👍 2
Selected: B
https://cloud.google.com/compute/docs/instances/connecting-to-windows#remote-desktop-connection-app Generating credentials for Windows VMs : Be sure the VM allows access through 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 Cloud Console and looking for firewall rules that allow tcp:3389 connections. So no need to be concerned with firewall rules. To connect with Microsoft Windows Remote Desktop, do the following: Create a Windows account and password if you do not have one yet. Instructions here https://cloud.google.com/compute/docs/instances/windows/generating-credentials Generating credentials for Windows VMs : Generate credentials for Windows Server VMs by using the Google Cloud Console or the Google Cloud CLI.
gielda211
👍 2
Selected: D
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
nshah68
👍 1
I just tried it on the console. You have to install an RDP client! There is no way to RDP into the server from the console. I did not have to create any firewall rules since there is a default rule to allow ingress connections on 3389. So B is the right answer in my opinion
nshah68
👍 1
One more thing - if the instance is launched using the default network then port 3389 is open for ingress. If using a custom network then a firewall rule needs to be created to allow connections on 3389
BAPII
👍 1
Selected: B
Bis the correct answer.
POOJA3808
👍 1
answer is D, https://cloud.google.com/compute/docs/instances/connecting-to-windows
Keeerthi
👍 1
Anyone confirm me which answers are correct.?. I'm confused with given answers and discussion answers...pls anyone give clarity
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.
hellof20
👍 1
Selected: D
I think D is correct.
AltHexMax
👍 1
Selected: D
Less steps... using Chrome RDP... no matter if on windows, mac or linux...
ACEngineer
👍 1
Selected: D
D is the possible solution with fewest steps. Hence it is the correct option.
RealEL40
👍 3
RDP is installed by default in windows and should be on linux also, so you don't need to install it. So not A and B.
dxloader
👍 2
Selected: D
https://cloud.google.com/architecture/chrome-desktop-remote-windows-compute-engine#connect_with_rdp
Uwe1
👍 1
D is the correct answer
vishnukumartr
👍 1
B. 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.
Jaira1256
👍 1
B seems to be the correct answer
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).
Vlan
👍 2
wrong. RDP and SSH are allowed by default. default-allow-rdp is there by default.
Shruti_Pal
👍 2
Answer is A
AminT
👍 2
A. A. Install a RDP client on your desktop. Verify that a firewall rule for port 3389 exists. 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.Option B is wrong as it fails to mention the key requirement of port 3389 be opened.Option C is wrong as RDP requires port 3389 to be opened.Option D is wrong as you need an RDP client.
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
Sriramiyer92
👍 1
The answer is "B". Link: https://cloud.google.com/compute/docs/troubleshooting/troubleshooting-rdp Excerpt : Note: The default port number for Windows RDP is 3389, however you can reconfigure this number. If you do, change the port number after tcp: in the "create rule" command to match. Defalut port no. is 3389. Hence aditional step of verification becomes an extra step.
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
hasib125
👍 3
Sorry ! I was wrong cause at GCP after connect using RRP it took time to connect on the instance. also got 3389 on firewall by default. Answer must be : B.
BalSan
👍 1
B is not right... Nothing is mentioned about if On prem network (desktop) is connected to Google Cloud... So Answer is D
jabrrJ68w02ond1
👍 20
Tested it myself. At least on my Machines, I was asked to First install a RDP Client.
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.
ready2rock
👍 2
B is the fewest number of steps....D ensures that you will actually get a successful connection, where B does not. WTF is the answer here?
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.
AD_0525
👍 2
As there is no statement to confirm whether the VM using default vpc or custom vpc, so it should be a best practice to check firewall rules, so D should be the answer.
Ashii
👍 2
D is a better bit https://cloud.google.com/compute/docs/instances/connecting-to-windows#remote-desktop-connection-app
alperenhasan
👍 1
i checked gcp console too, on VPC Firewall has got default-allow-rdp rule so it must be B.
pas77
👍 1
But you checked. LOL D is fewer steps as you don't need to install an RDP client
ri_unhou119
👍 2
I would say D is correct. https://cloud.google.com/architecture/chrome-desktop-remote-windows-compute-engine#connect_with_rdp
Agraved
👍 1
B is correct, as check is not required.
mcaromit
👍 2
D is the obvious correct answer
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.
FunkyTechnician
👍 1
Message when creating "Note: You must configure the network firewall to open TCP port 3389 to enable RDP access." See message here ---> https://miro.medium.com/max/1400/0*D96XBChdmalqTmNM.png
Rightsaidfred
👍 2
B is correct. Remember, it is the fewest amount of steps, and RDP Port 3389 is enabled by default.
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)
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
tavva_prudhvi
👍 2
Also, I have checked the default configurations in Networking, we have port:22, port:80, port:3389 as default. Hence, no need to do that again!
passnow
👍 1
I have never had the need to go set up any firewall when using rdp so all the noise with it being D is wrong. The answer is clearly the given option
maddy5835
👍 1
This is because the default network has predefined firewall-rule set up for RDP connections on port 3389
ozeross
👍 2
D is the correct answer. Firewall rules are not set by default and to be able to successfully access they need to be created.
tavva_prudhvi
👍 3
Yes, you're right but after I clicked the RDP button it says to install the RDP client but not to set the windows username/password.SO its B
tavva_prudhvi
👍 2
we are not testing the connection! Hence B
pas77
👍 1
Correct answer is A? how come? A is not doing anything. Only installing an RDP client and checking that port 3389 is allowed. Nothing else. Is not logging to the instance
sumanshu
👍 1
I corrected.. 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.Option B is wrong as it fails to mention the key requirement of port 3389 be opened.Option C is wrong as RDP requires port 3389 to be opened.Option D is wrong as you need an RDP client.
pentium2000
👍 2
I vote "D". We can't assume that the SQL Server is created on default VPC, which those said TCP 3389 pre-created. "D" makes sense if you are a cloud engineer.
sumanshu
👍 1
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.Option B is wrong as it fails to mention the key requirement of port 3389 be opened.Option C is wrong as RDP requires port 3389 to be opened.Option D is wrong as you need an RDP client.
EABDAJA
👍 1
B. 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.
GCP_Student1
👍 1
B. 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.
Hi2ALL
👍 2
D seems acceptable answer
Koen1978
👍 1
Cannot understand there is so much discussion on this. It's D...clearly. In B, you need to install an RDP client (vs in D just clicking a button). Then, in B you would need to type in IP address of the server (vs in D again just clicking a button). Don't over-analyse either....
tavva_prudhvi
👍 3
Yes, but if I click the RDP button, it's saying to install the RDP client, and I'm unable to connect to the instance without that. What do you say about that?
ShakthiGCP
👍 2
Ans: B, Guys. This is very simple. Just try it out in the GCP console with a Windows server. The question ask the "fewest number of steps". so that is Ans: B . The port and firewall will set by default and you no need to verify it every time for an RDP to a windows.
ShakthiGCP
👍 1
looking at the minute details - I'm also going wth Ans: D. between B and D , no much difference... Even D is downloading the RDP file to local when we click the RDP button. but the wordings are close enough in Ans : D
Vinod87
👍 2
D is correct!
iPablo26
👍 2
'Your VM allows RDP access. By default, Compute Engine creates firewall rules that allow RDP access on TCP port 3389'. It is unnecessary to verify anything on port 3389. I think B is the answer.
victory108
👍 1
B - 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.
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.
sumanshu
👍 1
if RDP client not installed on your local compuer - it will not open. So we need to first make sure, RDP client is installed. I'll vote for 'B'
nherrerab
👍 1
A is correct,
darren123
👍 1
Answer is B since we cannot RDP to the instance via GCP console. You can set the username and password via GCP, then use the local RDP client to login. Click the RDP button on the GCP Compute Engine page on any of the RDP instances, GCP will say the same. Can confirm B.
cRobert
👍 2
Sorry, typo, correct is B.
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.
JKRowlings
👍 1
D seems to be the correct answer. Google best practice asks you to verify the firewall rule for port 3389 exists. According to this article: https://cloud.google.com/compute/docs/instances/connecting-to-instance#remote-desktop-connection-app
cRobert
👍 1
From your resource By default, Compute Engine creates firewall rules that allow RDP access on TCP port 3389. You can verify that these firewall rules exist It's not a must to check the port, so correct answer is A.
alpharomeo9
👍 1
Connect using your RDP client 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. After creating the instance I have set the username and password (this step is mandatory). I clicked on RDP button and immediately it showed the above message. But without adding or verifying the port I was able to execute option B. But I would suggest to go with Option D as the Note suggest to configure the port after clicking RDP connect
Bhagirathi
👍 1
all of you confused. which one is actually correct to choose?
eliteone11
👍 1
My vote goes to D. Verifying 3389 is open I believe is the key indicator here. Regardless if its open by default or not I feel like that is more important. B would only be correct if we are assuming the user doesnt have an RDP client already installed... very strange altogether but if I had to choose one I would choose D.
robor97
👍 2
B. RDP must be installed as is not by default. Port 3389 is open by default
cecocenov
👍 1
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. Option B is wrong as it fails to mention the key requirement of port 3389 be opened. Option C is wrong as RDP requires port 3389 to be opened. Option D is wrong as you need an RDP client.
swatititame
👍 2
• B. 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.
Cakemanator
👍 1
Just tested You need to have some RDP client on your machine local (browser extension or third-party software), also you have to verify that firewall rule to allow RDP exists, and the final step is to set login credentials. It seems that A and B are correct but only partially. I'm confused..
gh999l
👍 1
D seems more correct. As it will avoid the step of installing RDP client in your base machine.
cuban123
👍 1
Its B. Firewall rule for 3389 rdp gets created when gce instance is created. no need to check for it...
nwk
👍 1
Vote D, no need the hassle to install RDP Client
bayurzx
👍 1
I can verify that B is correct. I recently did a quick lab concerning that.
glam
👍 3
B. 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.
prasanu
👍 1
Ans is B. As most of them preferRing is D, I would say when you create an instance in a newly project by default google has allowed firewall rule for RDP, so we don't need to verify it again. so answer id B
anony1234567
👍 1
D is the correct one as the downloaded RDP file would have the public IP for access. Otherwise you would have to look for it.
hiteshrup
👍 1
Answer is B. Reasons are listed here. A: Incorrect, though default firewall rule will have 3389. However, there is no credential file given nor username / password. Question asked to test features and not test connectivity, so we need to login at least to go into system and verify features C: Definite incorrect as port 22 is not for RDP and it is for SSH There is very fine line between B and D. Let's start evaluating steps on B. Steps involved in B: Step 1: Install RDP (in case of non-window system), that will be avoided in window. Step 2: Set Window user and password in GCP Consol and use to login. Step involved in D: Step 1: Click RDP button in GCP Console (This regardless of OS) Step 2: Verify rule for port 3389 (This is not require steps as default rule) Step 3: Set / Use credential for login to system. So if, we use Window system to login, then Step1 also can be eliminate in step3 but can not delete steps from Option D. So with all logic, Option B can be consider over Option D.
SSPC
👍 3
B is correct
gp7066
👍 2
B, The default network is pre-populated with firewall rules that allow incoming connections to instances. These rules can be deleted or modified as necessary: default-allow-rdp Allows ingress connections on TCP port 3389 from any source to any instance in the network. This rule has a priority of 65534, and it enables connections to instances running the Microsoft Remote Desktop Protocol (RDP). For testing we can assume Firewall rules are left to defaults https://cloud.google.com/vpc/docs/firewalls
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.
cannonball0608
👍 2
answer is B. There is a security element in consideration. SQL server is a database server and normally will not be exposed with a public IP address. The Chrome RDP plugin (method D) can only connect to VMs with public IP while the native RDP client can connect via corporate VPN.
XRiddlerX
👍 1
I agree that B is the answer but your security element has nothing to do with the question. Your reading too much into it from an exam perspective.
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.
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)
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.
szakaria
👍 1
D is definitely correct. I just tried it.
berom3
👍 1
I would say B. If you don't have Windows you have to install the RDP client https://codelabs.developers.google.com/codelabs/cloud-create-sql-server/index.html#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
cloudenthu01
👍 1
D is correct.
mlantonis
👍 2
I would also choose D. https://cloud.google.com/solutions/chrome-desktop-remote-windows-compute-engine#connect_with_rdp
tavva_prudhvi
👍 1
See point number 5 in your article it clearly mentions about CHROME RDP APP, where did you get that without installing it?
saurabh1805
👍 1
Considering this document closes correct answer is D: https://cloud.google.com/compute/docs/instances/connecting-to-instance#windows_gui
dan80
👍 1
D - https://cloud.google.com/compute/docs/troubleshooting/troubleshooting-rdp
hems4all
👍 2
Port 3389 is a Firewall rule, what if this rule was deleted, and after that VM is created? RDP won't work in that case, you can try by deleting default firewall rule "default-allow-rdp"
juancambb
👍 1
D is correct!
Lush
👍 2
Although this answer seems correct, I think it is redundant to be checking that the firewall rule for port 3389 is in place, this rule is automatically created when setting up a windows instance, the correct answer is B
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
Raj22
👍 2
why should we have to install RDP, so ans will be D
Lush
👍 1
Only windows has RDP installed by default, everybody else has to download and install
zukko78
👍 4
according to LAB GSP093, for me correct B
YashBindlish
👍 3
Correct Answer is A
ehizren
👍 1
A can't be correct. You must set up a password for RDP
vnxt
👍 56
I would say B is correct. RDP is enabled by default when you crate a Windows instance (no need to chek on it). Just make sure you install an RDP client ( chrome ext or RDP) and set windows password.
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
ankit89
👍 35
D seems more correct
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.
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
Lush
👍 3
This is wrong because you have been asked to connect, not test for a connection.
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.
cesar7816
👍 3
For me is easier to use the RDP icon from the GCP console instead of using RDP client
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
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 uservnxt 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
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.
Related Analysis
Practice All ACE Questions
Access 84 questions with complete answers and detailed explanations.
View Full ACE Practice Test →