Exam Associate Cloud Engineer All QuestionsBrowse all questions from this exam
Question 20

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?

    Correct Answer: D

    The best way to connect to the SQL Server 2017 instance on Compute Engine using the fewest steps is to set a Windows username and password in the GCP Console and verify that a firewall rule for port 3389 exists. Clicking the RDP button in the GCP Console allows you to enter the credentials to establish a connection. This method leverages the GCP Console interface and assumes the necessary RDP configurations are in place by default, minimizing the setup process.

Discussion
vnxtOption: B

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.

pas77

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.

UtsavDM

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.

jabrrJ68w02ond1

Tested it myself. At least on my Machines, I was asked to First install a RDP Client.

ryumada

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

eledu1985

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.

bubidubi

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.

Gregwaw

You need firewall ingress rule for port 3398 in your VPC. It is not created by default.

ankit89Option: D

D seems more correct

obeythefist

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.

Suryas_OneOption: B

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."

thewalkerOption: 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.

jcloud965Option: 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."

Captain1212Option: B

B seems more correct because you cannot use rdp by click you have to first install it

Abi143Option: 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

certified28Option: 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

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.

krishnu123Option: D

D is the correct answer

ccpmadOption: D

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.

sinhOption: D

The following sites do not describe RDP client installation. https://cloud.google.com/compute/docs/instances/connecting-to-windows

sinhOption: D

https://cloud.google.com/compute/docs/instances/connecting-to-windows#remote-desktop-connection-app

NoviceNebulaOption: 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.

Evan7557Option: D

Answer D

ovokpusOption: 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

YourCloudGuruOption: 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.

ShenanniganOption: 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