Question 38 — AZ-104 Practice Exam 13
For each statement about Azure File Sync and cloud tiering, drag it to the appropriate boxes in the Correct Match column.
Each item may be used once, more than once, or not at all.
| Option | Correct Match |
|---|---|
| Transforms Windows Server into a fast cache of Azure file shares | [Gap 1] |
| Allows use of SMB, NFS, and FTPS locally on Windows Server to access data | [Gap 2] |
| Caches frequently accessed files locally; tiers other files to Azure based on policy | [Gap 3] |
| Replaces a tiered local file with a pointer that represents a URL to the cloud copy | [Gap 4] |
| Opening a tiered file seamlessly recalls data from Azure without user awareness | [Gap 5] |
| Supports as many caches as needed around the world | [Gap 6] |
- Cloud tiering
- Global multi-cache support
- Azure File Sync
- Reparse point
- Blob lifecycle management
- Transparent recall from Azure
Correct answers
- Gap 1: Azure File Sync
- Gap 2: Azure File Sync
- Gap 3: Cloud tiering
- Gap 4: Reparse point
- Gap 5: Transparent recall from Azure
- Gap 6: Global multi-cache support
Explanations
Correct Matches
Azure File Sync – Converts Windows Server into a cache for Azure file shares and lets you keep using Windows Server protocols (SMB/NFS/FTPS) locally.
Cloud tiering – Keeps hot files locally and tiers colder files to Azure based on policy.
Reparse point (pointer) – Local placeholder that represents the Azure URL for the file when it’s tiered.
Transparent recall from Azure – On open, data is recalled automatically; users needn’t know the file was in the cloud.
Offline O attribute / greyed icon – Visual/attribute cue that the file is only in Azure.
Global multi-cache support – Multiple caches worldwide are supported.
Unused Item(s)
Blob lifecycle management – Applies to object storage policies, not Azure File Sync tiering.