Check your knowledge

1.

How often does the cloud endpoint change detection job run?

Every 12 hours.

Every 8 hours.

Every 24 hours.

2.

What is the Azure File Sync agent?

It's installed on a server to enable Azure File Sync replication between the local file share and an Azure file share.

It's installed on a server to set NTFS permissions on files and folders.

It's installed on an Azure file share to control on-premises file and folder replication traffic.

3.

How do you assess your server's compatibility with Azure File Sync?

Download and run the Azure File Sync agent to assess the file share and server.

Install the Azure PowerShell module on the server and use the cmdlet Invoke-AzStorageSyncCompatibilityCheck.

Register the server with the Storage Sync Service to have the server evaluated for compatibility.

4.

In what order do you create the Azure resources needed to support Azure File Sync?

Storage Sync Service, storage account, file share, and then the sync group.

Storage account, file share, Storage Sync Service, and then the sync group.

Storage account, file share, sync group, and then Storage Sync Service.

5.

What is cloud tiering in Azure File Sync?

It's a policy you create that prioritizes the sync order of file shares.

It's a policy that sets the frequency at which the sync job runs.

It's a feature that tiers infrequently accessed files to free up space on the local file share.

6.

What's the deployment process for Azure File Sync?

Evaluate your on-premises system, create the Azure resources, install the Azure File Sync agent, register the on-premises server, and create the server endpoint.

Create the Azure resources, install the Azure File Sync agent, register the on-premises server, and create the server endpoint.

Evaluate your on-premises system, create the Azure resources, install the Azure File Sync agent on a virtual machine, register the on-premises server, and create the server endpoint.

7.

Which of these answers isn't a possible cause for file sync issues?

Your company's firewall rules are blocking network traffic on port 445.

The virtual machine that runs the Storage Sync Service is stopped.

Your on-premises server doesn't support SMB encryption.

Knowledge check

Feedback