Exam AZ-104 All Questions

View all questions & answers for the AZ-104 exam

Exam AZ-104 topic 5 question 137 discussion

Actual exam question from Microsoft's AZ-104

Question #: 137
Topic #: 5

HOTSPOT -

You have an Azure subscription that contains the virtual networks shown in the following table.

The subscription contains the virtual machines shown in the following table.

Each virtual machine contains only a private IP address.

You create an Azure bastion for VNet1 as shown in the following exhibit.

For each of the following statements, select Yes if the statement is true. Otherwise, select No.

NOTE: Each correct selection is worth one point.

Show Suggested Answer

Suggested Answer:

by [deleted] at Sept. 1, 2023, 8:47 p.m.

Comments

Submit Cancel

hidefo6963

Highly Voted 1 year, 9 months ago

the 1st is "No" mstsc is a native client and is supported only by Standard Bastion the 2nd is "Yes"? if the poor wording means connecting through Azure Portal by SSH, that's what Basic Bastion supports. the 3rd is "No" No peering from the Bastion enabled Vnet1

upvoted 42 times

tableton

1 year, 2 months ago

I Upvoted you but now disagree: - mstsc.exe is RDP client, is the client included in windows and allow connect to RDP servers - Native client is intended to use from Azure CLI "Log in to Azure using the Azure CLI so you can access Azure Bastion native client support" https://petri.com/azure-bastion-native-client-support/ and yes, need Standard SKU but it's not the case

upvoted 5 times

BhanuD

3 months, 1 week ago

i think the Azure Bastion connects with web not as RDP client in widonws, hence it is N

upvoted 1 times

BhanuD

3 months, 1 week ago

When you click Connect,the RDP connection to this virtual machine via Bastion will open in your browser (over HTML5) using port 443 and the Bastion service. https://learn.microsoft.com/en-us/azure/bastion/bastion-connect-vm-rdp-windows

upvoted 1 times

BhanuD

3 months, 1 week ago

To connect with Native client from Bastion , more configuration is required on Bastion and Vm's also Native client support requires the Bastion Standard SKU

upvoted 1 times

...

tableton

1 year, 2 months ago

So in my oppinion Y-Y-N

upvoted 6 times

Arash123

1 year, 2 months ago

I believe first one is No https://learn.microsoft.com/en-us/azure/bastion/native-client#deploy-bastion-with-the-native-client-feature

upvoted 1 times

Arash123

1 year, 2 months ago

I was wrong (still not 100% sure). Seems mstsc.exe and Native Client are two different things! Basic SKU supports RDP but not Native Client.

upvoted 2 times

Lint89

10 months, 2 weeks ago

"Once you sign in to your target VM, the native client on your computer opens up with your VM session via MSTSC." https://learn.microsoft.com/en-us/azure/bastion/connect-vm-native-client-windows

upvoted 2 times

...

ADB22

7 months ago

mstsc.exe and the Native Client are two different things. mstsc.exe: This is the executable file for the Microsoft Terminal Services Client, commonly known as Remote Desktop Connection. It is used to connect to remote computers or virtual machines using the Remote Desktop Protocol (RDP). Native Client: This term can refer to various native applications depending on the context. In the context of remote desktop connections, it often refers to the built-in remote desktop clients available on different operating systems (e.g., Remote Desktop app on Windows, Microsoft Remote Desktop app on macOS, iOS, and Android). So, while mstsc.exe is a specific executable for Remote Desktop Connection on Windows, the Native Client can refer to any platform-specific remote desktop application

upvoted 2 times

...

Elsayed2030

6 months ago

I really don't see how 2 is a yes. I understand the Vnet are peered but the gateway transit is not enabled in the first Vnet. Wihtout it, it won't allow an external connection to directly connect to the second VNet.

upvoted 2 times

...

01111010

1 year, 7 months ago

First question is 'Yes' - rationale: mstsc is is a command line interface used to run the Microsoft Remote Desktop (RDP) client. Based on Bastion Basic SKU, access via RDP is supported on Basic and Standard Bastion. Link reference: https://learn.microsoft.com/en-us/azure/bastion/configuration-settings#skus

upvoted 9 times

...

Kuikz

Highly Voted 1 year, 9 months ago

I would say NO YES NO Basic SKU cannot connect to VM using a native client https://learn.microsoft.com/en-us/azure/bastion/bastion-overview

upvoted 23 times

[Removed]

1 year, 7 months ago

https://learn.microsoft.com/en-us/azure/bastion/native-client

upvoted 2 times

...

josola

1 year, 6 months ago

Yes, it can. Check https://learn.microsoft.com/en-us/azure/bastion/configuration-settings#skus

upvoted 2 times

josola

1 year, 6 months ago

Moderator, please disregard this response. I was wrong.

upvoted 5 times

...

SBGM

Most Recent 1 month, 3 weeks ago

I was typing a comment about how RDP is supported at the basic SKU but apparently that means the RDP button in the Azure portal. mstsc.exe still seems to require the standard SKU.

upvoted 1 times

...

8ac3742

2 months, 2 weeks ago

If I enable "Use remote gateways" on vNet2, it allows traffic to be forwarded between vNet1 and vNet3. then I can use Bastion1 on vNet1 to remotely connect to VMs in vNet3 via the Azure portal. Azure Bastion supports remote access to VMs in peered virtual networks, so Bastion1 can connect to VMs in vNet3 through the peering setup. However the question doesn't mention whether enabled "Use remote gateways" on vNet2, so I would choose False for 3rd question.

upvoted 1 times

...

8ac3742

2 months, 2 weeks ago

yes, yes, no Using Bastion to connect to one VM via Portal appears to use mstsc.exe on local to connect to VM without disclosing the public IP of that VM, so 1st answer is yes. Using SSH to connect to Unix VM via Bastion so 2nd answer is yes vNet3 is not peered so the 3rd answer is no

upvoted 1 times

...

PMPft17

8 months, 1 week ago

Q3: I believe it YES. Makes me think its more to do with the SKU or Azure Portal, not the Region itself. Vnet1 <--> Vnet2 ---> Vnet3. If there is global peering, Azure Bastion supports this. I would think Vnet1 could connect to Vnet 3 (route traffic) if globally peered.

upvoted 2 times

chrillelundmark

5 months, 2 weeks ago

It clearly states it support global peering. https://learn.microsoft.com/en-us/azure/reliability/reliability-bastion#multi-region-support

upvoted 1 times

...

[Removed]

8 months, 3 weeks ago

WRONG No Yes No

upvoted 2 times

...

joolitan

9 months ago

The Remote Desktop Connection client (mstsc.exe) can be used to connect to VM1 through Bastion1 = Yes refer = https://learn.microsoft.com/en-us/azure/bastion/configuration-settings Feature Developer SKU Basic SKU Standard SKU Premium SKU Connect to Windows VM using RDP Yes Yes Yes Yes The Azure portal can use SSH to connect to VM2 through Bastion1 = Yes refer = https://learn.microsoft.com/en-us/azure/bastion/configuration-settings Feature Developer SKU Basic SKU Standard SKU Premium SKU Connect to Linux VM using SSH Yes Yes Yes Yes The Azure portal can be used to connect to VM3 through Bastion1 = No https://learn.microsoft.com/en-us/azure/bastion/configuration-settings Azure Bastion Azure portal requires Standard SKU or higher. Also, Azure bastion configured for VNet1, but VM3 used VNet3 which not configured

upvoted 2 times

...

Dash_888

9 months, 1 week ago

Y-Y-N I believe the answer to Number 1 is Yes as shown in the reference below. https://learn.microsoft.com/en-us/azure/bastion/bastion-overview Connect to Windows VM using RDP - YES (Basic SKU)

upvoted 1 times

...

23169fd

1 year ago

No: Since the Basic tier does not support mstsc.exe, this statement is incorrect. Yes: VM2 is in VNet2, which is peered with VNet1. Because VNet1 and VNet2 are peered, the Bastion host in VNet1 can be used to connect to VM2 via SSH through the Azure portal. No: VM3 is in VNet3, which is in West US. VNet3 is peered with VNet2, but VNet2 is in a different region (East US). Bastion cannot traverse regional peering, so the Bastion host in VNet1 (East US) cannot connect to VM3 in VNet3 (West US).

upvoted 3 times

...

RemmyT

1 year, 2 months ago

1. Yes 2. Yes 3. No (No peering Vnet1 - VNet3) Bastion configuration settings Basic SKU / Standard SKU Connect to Linux VM using SSH : Yes / Yes Connect to Windows VM using RDP : Yes / Yes Connect to Linux VM using RDP : No / Yes Connect to Windows VM using SSH : No / Yes https://learn.microsoft.com/en-us/azure/bastion/configuration-settings

upvoted 5 times

...

MandAsh

1 year, 2 months ago

Its NYN. Mstsc is native client for bastion. No matter if it is out of box utility for windows.

upvoted 1 times

...

1828b9d

1 year, 3 months ago

This question was in exam 01/03/2024

upvoted 4 times

...

1828b9d

1 year, 3 months ago

This question was in exam 01/03/2024

upvoted 2 times

...

Amir1909

1 year, 3 months ago

- No - yes - No

upvoted 1 times

...

amsioso

1 year, 5 months ago

NYN https://learn.microsoft.com/en-us/azure/bastion/vm-upload-download-native "This feature requires the Standard SKU. The Basic SKU doesn't support using the native client."

upvoted 1 times

...

Indy429

1 year, 6 months ago

Box 1 should be NO Native client is not supported in Bastion Basic SKU.

upvoted 1 times

...

Load full discussion...