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?
A.
Install a RDP client on your desktop. Verify that a firewall rule for port 3389 exists.
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.
C.
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.
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.
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.
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.
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
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.
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.
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.
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.
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.
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.
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.
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."
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.
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."
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.
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.
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
vnxt
Highly Voted 4 years, 6 months agopas77
3 years, 4 months agojabrrJ68w02ond1
2 years, 11 months agoUtsavDM
3 years, 2 months agoryumada
2 years, 3 months agoeledu1985
2 years, 1 month agobubidubi
9 months, 2 weeks agoGregwaw
1 year, 2 months agoankit89
Highly Voted 4 years, 6 months agoobeythefist
2 years, 8 months agoMakar
Most Recent 2 weeks agomartin2099
2 weeks, 4 days agorchowra
1 month agoakki82782
1 month agoChetantest07
1 month, 1 week agosivakarthick16
1 month, 4 weeks agoTimfdklfajlksdjlakf
2 months, 3 weeks agokairosfc
3 months, 3 weeks agojcloud965
4 months agoBuenaCloudDE
4 months agoccpmad
5 months, 4 weeks agosinh
10 months, 1 week agoSuryas_One
10 months, 3 weeks agosinh
10 months, 3 weeks agothewalker
1 year agoNoviceNebula
1 year ago