Question
You have on-premises servers that run Windows Server as shown in the following table.
You have an Azure file share named share1 that stores two files named File2.docx and File3.docx.
You create an Azure File Sync sync group that includes the following endpoints:
✑ share1
✑ D:\Folder1 on Server1
✑ D:\Data1 on Server2
For each of the following statements, select Yes if the statement is true. Otherwise, select No.
NOTE: Each correct selection is worth one point.
Hot Area:
| Name | Local content |
| --- | --- |
| Server1 | D:\Folder1\File1.docx |
| Server2 | D:\Data1\File3.docx |
Explanation
Statement 1 (Yes): A server endpoint stays an ordinary writable NTFS folder. Creating File2.docx in D:\Folder1 on Server1 succeeds; if the name collides with File2.docx in share1, Azure File Sync keeps both files as a sync conflict instead of blocking the write.
Statement 2 (Yes): File1.docx can be created in D:\Data1 on Server2 like any other file; it is then uploaded to share1 and synced to the other endpoints.
Statement 3 (Yes): Sync is multi-master: every file in the sync group is synced to every server endpoint. File3.docx existed in both share1 and D:\Data1 on Server2 before the server endpoint was created, so Azure File Sync creates a conflict file and keeps both versions: the most recently written one keeps the name File3.docx and the older one is renamed with its endpoint name (for example File3-Server2.docx or File3-Cloud.docx). File3.docx is therefore synced to D:\Folder1 on Server1.
