Exam AZ-104 topic 3 question 33 discussion

The Answer is not correct. It should be no access for both cases. - for first case, cause the IP is not matching the SAS requirements - for second case, since it is using "net use" where it uses SMB. The SMB (Server Message Broker) protocol does not support SAS. it still asks for username/password. Accordingly, it will give error wrong username/pass and will not provide access.

Correct Answer: Box 1: will have no access The IP 193.77.134.1 does not have access on the SAS, because it is not matching the SAS requirements. IP is out of range. Box 2: will have no access The SAS token is not supported in mounting Azure File share currently, it just supports the Azure storage account key. Since it is using "net use" where it uses SMB, the SMB (Server Message Broker) protocol does not support SAS. it still asks for username/password. Accordingly, it will give error wrong username/pass and will not provide access. Reference: https://docs.microsoft.com/en-us/azure/storage/common/storage-dotnet-shared-access-signature-part-1 https://docs.microsoft.com/en-us/azure/vs-azure-tools-storage-manage-with-storage-explorer?tabs=windows https://docs.microsoft.com/en-us/azure/storage/files/storage-how-to-use-files-windows https://docs.microsoft.com/en-us/answers/questions/40741/sas-key-for-unc-path.html

WRONG 1. will have no access 2. will have no access

Shared access signature (SAS) tokens aren't currently supported for mounting Azure file shares. https://learn.microsoft.com/en-us/azure/storage/files/storage-how-to-use-files-windows

- will have no access - will have no access

Box1: have no access , due to IP restriction. Box2: Will be able to access, since storage explorer can access the share using SAS. Now the SAS will need to be modified by appending the share name after the storage account file endpoint "https://<StorageAccount>.file.core.windows.net/<share1>/?<SAS>"

Box 1: Will have no access. The IP 193.77.134.1 is not in IP range of SAS requirements; Box 2: Will have all rights. Net use now supports SAS token when mounting Azure File share: CMD: net use Z: \\mystorageaccount.file.core.windows.net\myshare /u:Azure\mystorageaccount <SAS_Token>

This is what I got an answer today from Bing AI. Yes, you can access a storage account using SAS with the net use command. The net use command is used to connect to a file share on a remote computer and map it to a drive letter on your local computer 1. To connect to an Azure storage account using SAS, you can use the following command: net use <drive-letter>: \\<storage-account-name>.file.core.windows.net\<share-name> /u:<storage-account-name> <storage-account-key>

In my examp september 2023.

Found the question on another site I am studying, and it has the same answer which I don't think is correct. It takes forever to check some of these questions.

Box 1: will have no access The IP 193.77.134.1 does not have access on the SAS, because it is not matching the SAS requirements. IP is out of range. Box 2: will have no access The SAS token is not supported in mounting Azure File share currently, it just supports the Azure storage account key. Since it is using "net use" where it uses SMB, the SMB (Server Message Broker) protocol does not support SAS. it still asks for username/password. Accordingly, it will give error wrong username/pass and will not provide access. Reference: https://docs.microsoft.com/en-us/azure/storage/common/storage-dotnet-shared-access-signature-part-1 https://docs.microsoft.com/en-us/azure/vs-azure-tools-storage-manage-with-storage-explorer?tabs=windows https://docs.microsoft.com/en-us/azure/storage/files/storage-how-to-use-files-windows https://docs.microsoft.com/en-us/answers/questions/40741/sas-key-for-unc-path.html

I had this in my exam today - Passed 800

How are most these answers wrong? What a trash exam collection

Some of these questions are just trash, I swear, like they WANT you to FAIL.

Exact same Q came in my exam on 30 April2023.

Answer is A: No Access B: No Access SAS can't be used as a password. It has to be passed as a Key https://learn.microsoft.com/en-us/azure/storage/common/storage-sas-overview#how-a-shared-access-signature-works

The Answer is incorrect. It should be no access for both cases.