| Question.86 You have an Azure subscription that contains an Azure file share. You have an on-premises server named Server1 that runs Windows Server 2016. You plan to set up Azure File Sync between Server1 and the Azure file share. You need to prepare the subscription for the planned Azure File Sync. Which two actions should you perform in the Azure subscription?  |
86. Click here to View Answer
1. Create a Storage Sync Service.
2. Create a sync group.
3. Install Azure File Sync agent on the server with the full data set.
4. Register that server and create a server endpoint on the share.
| Question.87 You have an Azure subscription that contains the storage accounts shown in the following exhibit.  Use the drop-down menus to select the answer choice that completes each statement based on the information presented in the graphic  . |
87. Click here to View Answer
Box 1: contoso104 only
Premium file shares are hosted in a special purpose storage account kind, called a FileStorage account.
Box 2: contoso101 or contos103 only
Object storage data tiering between hot, cool, and archive is supported in Blob Storage and General Purpose v2 (GPv2) accounts. General Purpose v1 (GPv1) accounts don’t support tiering.
The archive tier supports only LRS, GRS, and RA-GRS.
Reference:
https://docs.microsoft.com/en-us/azure/storage/common/storage-account-overview
https://docs.microsoft.com/en-us/azure/storage/files/storage-how-to-create-premium-fileshare?tabs=azure-portal
https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blob-storage-tiers
| Question.88 You have an Azure subscription named Subscription1. In Subscription1, you create an Azure file share named share1. You create a shared access signature (SAS) named SAS1 as shown in the following exhibit:  To answer, select the appropriate options in the answer area.  |
88. Click here to View 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
| Question.89 You have a general-purpose v1 Azure Storage account named storage1 that uses locally-redundant storage (LRS). You need to ensure that the data in the storage account is protected if a zone fails. The solution must minimize costs and administrative effort. What should you do first? (A) Create a new storage account. (B) Configure object replication rules. (C) Upgrade the account to general-purpose v2. (D) Modify the Replication setting of storage1. |
89. Click here to View Answer
Answer is (C) Upgrade the account to general-purpose v2.
v1 supports GRS/RA-GRS but question was about least cost. Least cost is ZRS which is only supported for v2 and premium file/block storage.
Reference:
https://docs.microsoft.com/en-us/azure/storage/common/storage-redundancy#supported-storage-account-types
| Question.90 You have an Azure subscription that contains the storage accounts shown in the following table.  You plan to manage the data stored in the accounts by using lifecycle management rules. To which storage accounts can you apply lifecycle management rules? (A) Storage1 only (B) Storage1 and storage2 only (C) Storage3 and storage4 only (D) Storage1, storage2, and storage3 only (E) Storage1, storage2, storage3, and storage4 |
90. Click here to View Answer
Answer is (D) Storage1, Storage2, and Storage3 only
The lifecycle management feature is available in all Azure regions for general purpose v2 (GPv2) accounts, blob storage accounts, premium block blobs storage accounts, and Azure Data Lake Storage Gen2 accounts