AZ-104 Practice Question 55: File Sync Proactive Recall
Microsoft Azure Administrator Associate (AZ-104) · Test 6 · question 5 of 10
A company uses Azure File Sync with cloud tiering on file servers in the US and in India. Each morning, staff in India open project files that the US team created the previous day, and the first open of each file is slow because it has to be recalled from the Azure file share. The company wants the new and changed files to be already on the India server when staff arrive, and does not want to change how cloud tiering works on the US server.
What should the administrator do?
Show answer and explanation
Answer:
Proactive recall tells a server endpoint to download files as soon as they are created or modified in the Azure file share, instead of waiting for a user to open them. This is the scenario Microsoft describes for offices in different time zones: the India server prepares its local cache overnight, so the first open is fast, and other files are still tiered as usual. It is set for the specific server endpoint, which leaves the US server untouched.
Option B removes the local disk saving that cloud tiering exists for, and the server volume may not be large enough to hold the whole namespace. It is far broader than the requirement.
Option C moves in the opposite direction. A higher free space policy makes the server tier more files to keep more of the disk free, so more files are cloud-only and more first opens are slow.
Option D adds a second copy of the data and a second sync relationship. It does not change how tiered files are recalled and adds cost and complexity.
Reference: Understand Azure File Sync Cloud Tiering