Microsoft AZ-104 Practice Test - Questions Answers, Page 16

Box 1: contosostorage

The name of account

Box 2: file.core.windows.net

Box 3: data

The name of the file share is data.

Example:

Reference: https://docs.microsoft.com/en-us/azure/storage/files/storage-how-to-use-files-windows

Step 1: Install the Azure File Sync agent on Server1

The Azure File Sync agent is a downloadable package that enables Windows Server to be synced with an Azure file share

Step 2: Register Server1.

Register Windows Server with Storage Sync Service

Registering your Windows Server with a Storage Sync Service establishes a trust relationship between your server (or cluster) and the Storage Sync Service.

Step 3: Add a server endpoint

Create a sync group and a cloud endpoint.

A sync group defines the sync topology for a set of files. Endpoints within a sync group are kept in sync with each other. A sync group must contain one cloud endpoint, which represents an Azure file share and one or more server endpoints. A server endpoint represents a path on registered server.

Reference: https://docs.microsoft.com/en-us/azure/storage/files/storage-sync-files-deploymentguide

Box 1: Zone-redundant storage (ZRS)

Zone-redundant storage (ZRS) replicates your data synchronously across three storage clusters in a single region.

LRS would not remain available if a data center in the region fails

GRS and RA GRS use asynchronous replication.

Box 2: StorageV2 (general purpose V2)

ZRS only support GPv2.

Reference:

https://docs.microsoft.com/en-us/azure/storage/common/storage-redundancy

https://docs.microsoft.com/en-us/azure/storage/common/storage-redundancy-zrs

AzCopy is a command-line utility that you can use to copy blobs or files to or from a storage account.

Incorrect Answers:

A, C, E: AzCopy does not support table and queue storage services.

D: AzCopy supports file storage services, as well as blob storage services.

Reference:

https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-v10

You can provide authorization credentials by using Azure Active Directory (AD), or by using a Shared

Access Signature (SAS) token.

Box 1:

Both Azure Active Directory (AD) and Shared Access Signature (SAS) token are supported for Blob storage.

Box 2:

Only Shared Access Signature (SAS) token is supported for File storage.

Reference:

https://docs.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-v10

Microsoft have Docker Volume Plugin for Azure file storage which provides exactly this and it is used for Azure file shares.

Azure File Storage volume plugin is not limited to ease of container migration. It also allows a file share to be shared among multiple containers (even though they are on different hosts) to collaborate on workloads, share configuration or secrets of an application running on multiple hosts.

Another use case is uploading metrics and diagnostics data such as logs from applications to a file share for further processing.

Reference:

https://azure.microsoft.com/en-gb/blog/persistent-docker-volumes-with-azure-file-storage/

Azure file shares can be used as persistent volumes for stateful containers. Containers deliver "build once, run anywhere" capabilities that enable developers to accelerate innovation. For the containers that access raw data at every start, a shared file system is required to allow these containers to access the file system no matter which instance they run on.

https://docs.microsoft.com/en-us/azure/storage/files/storage-files-introduction

The hardware in a location is divided in to multiple update domains and fault domains. An update domain is a group of VMs and underlying physical hardware that can be rebooted at the same time.

VMs in the same fault domain share common storage as well as a common power source and network switch.

Microsoft updates, which Microsoft refers to as planned maintenance events, sometimes require that VMs be rebooted to complete the update. To reduce the impact on VMs, the Azure fabric is divided into update domains to ensure that not all VMs are rebooted at the same time.

https://docs.microsoft.com/en-us/azure/virtual-machines/windows/tutorial-availability-sets

From the RG1 blade, click Deployments. You see a history of deployment for the resource group.

Reference:

https://docs.microsoft.com/en-us/azure/azure-resource-manager/templates/template-tutorialcreate-first-template?tabs=azure-powershell

Through activity logs, you can determine:

ß what operations were taken on the resources in your subscription ß who started the operation ß when the operation occurred ß the status of the operation ß the values of other properties that might help you research the operation

On the Azure portal menu, select Monitor, or search for and select Monitor from any page

2. Select Activity Log.

3. You see a summary of recent operations. A default set of filters is applied to the operations. Notice the information on the summary includes who started the action and when it happened.

Reference:

https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/view-activity-logs

From the RG1 blade, click Deployments. You see a history of deployment for the resource group.

Reference:

https://docs.microsoft.com/en-us/azure/azure-resource-manager/templates/template-tutorialcreate-first-template?tabs=azure-powershell

Through activity logs, you can determine:

ß what operations were taken on the resources in your subscription ß who started the operation ß when the operation occurred ß the status of the operation ß the values of other properties that might help you research the operation

1. On the Azure portal menu, select Monitor, or search for and select Monitor from any page

2. Select Activity Log.

3. You see a summary of recent operations. A default set of filters is applied to the operations. Notice the information on the summary includes who started the action and when it happened.

Reference:

https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/view-activity-logs