Question
You have an Azure subscription that contains the storage accounts shown in the following table.
In the East US Azure region, you create a storage sync service named Sync1.
You need to create a sync group in Sync1.
Which storage accounts can you use, and what can you specify as the cloud endpoints. To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
| Name | Location | Kind | Container | File share |
| --- | --- | --- | --- | --- |
| storage1 | East US | StorageV2 | cont1 | share1 |
| storage2 | East US | BlockBlobStorage | cont2 | Not applicable |
| storage3 | East US | FileStorage | Not applicable | share3 |
| storage4 | Central US | StorageV2 | cont4 | share4 |
Explanation
Storage accounts: storage1 and storage3 only — A sync group's cloud endpoint must live in a storage account that is in the same Azure region as the Storage Sync Service (Sync1 is in East US) and that supports Azure Files, so only the East US, Azure Files–capable accounts qualify; storage1 and storage3 meet both conditions. The wider choices that add storage2 and storage4 fail one of those tests (wrong region, or an account type/configuration that cannot host the Azure file share a cloud endpoint requires), so options such as "storage1, storage2, storage3, and storage4" are not valid.
Cloud endpoints: share1 and share3 only — The cloud endpoint of an Azure File Sync sync group is always an Azure file share, never a blob container, so cont1, cont2, and cont4 can never be selected regardless of which account they sit in. That leaves the file shares in the eligible East US accounts, share1 and share3; share4 is excluded because its storage account is not usable with Sync1, which rules out "share1, share3, and share4 only" and every option that mixes in containers.
