Examkin

Question

Difficulty: MediumConfigure Azure Files and Azure File Sync

An administrator is configuring hybrid storage using Azure File Sync. A Windows Server named Server1 is registered with a Storage Sync Service named StorageSync1. A sync group named SyncGroup1 is created in StorageSync1 and contains a cloud endpoint pointing to an Azure file share named share1, and a server endpoint pointing to the path D:\Projects on Server1. To meet a compliance requirement for off-site replica separation, the administrator creates a second sync group named SyncGroup2 in StorageSync1 with a cloud endpoint pointing to a separate Azure file share named share2. The administrator then attempts to add a server endpoint pointing to the path D:\Projects on Server1 within SyncGroup2. What is the result of attempting to create the server endpoint in SyncGroup2?

  1. A
    The operation will succeed, and the files in D:\Projects will sync bi-directionally with both share1 and share2.
  2. The operation will fail because Azure File Sync does not support multiple server endpoints referencing the same or overlapping directory paths on the same registered server.Answer
  3. C
    The operation will fail because a registered server can only be associated with a single sync group at a time.
  4. D
    The operation will fail because Azure File Sync requires all synchronized Azure file shares to reside in the same storage account.

Answer

The operation will fail because Azure File Sync does not support multiple server endpoints referencing the same or overlapping directory paths on the same registered server.
The correct option is that the operation will fail because Azure File Sync does not support multiple server endpoints referencing the same or overlapping directory paths on the same registered server. Each server endpoint path must be unique across all sync groups within the Storage Sync Service to prevent synchronization loop issues.

Step-by-Step Solution

1
Analyze the request to sync the same local directory path D:\Projects on Server1 to two different sync groups.
Identify that the path D:\Projects is already in use by SyncGroup1 as a server endpoint.
Before configuring a server endpoint, Azure File Sync validates that the path is not already associated with another endpoint.
2
Evaluate Azure File Sync constraints regarding path overlap.
Recall that Azure File Sync prohibits duplicate or nested/overlapping server endpoint paths on the same registered server across all sync groups.
This constraint prevents synchronization conflicts, race conditions, and loops between different cloud endpoints.
3
Determine the outcome of attempting to register D:\Projects in SyncGroup2.
The configuration attempt will fail with an validation error.
Azure File Sync enforces that each path on a server can only map to one sync group.

Key Concept

Azure File Sync server endpoint path exclusivity
Rate this question

Topics

Configure Azure Files and Azure File Sync

More questions from this topic