Overview
-
Company Information
-
ADatum Corporation is a manufacturing company that has a main office in Seattle and two branch offices in Los Angeles and Montreal.
Fabrikam Partnership
-
ADatum recently partnered with 2 company named Fabrikam, Inc.
Fabrikam is a manufacturing company that has a main office in Boston and a branch office in Orlando.
Both companies intend to collaborate on several joint projects.
Existing Environment
ADatum AD DS Environment
The on-premises network of ADatum contains an Active Directory Domain Services (AD DS) forest named adatum.com.
The forest contains two domains named adatum.com and east.adatum.com and the domain controllers shown in the following table.
Fabrikam AD DS Environment
-
The on-premises network of Fabrikam contains an AD DS forest named fabrikam.com.
The forest contains two domains named fabrikam.com and south.fabrikam.com.
The fabrikam.com domain contains an organizational unit (OU) named Marketing.
Server Infrastructure
The adatum.com domain contains the servers shown in the following table.
HyperV1 contains the virtual machines shown in the following table.
All the virtual machines on HyperV1 have only the default management tools installed.
SSPace1 contains the Storage Spaces virtual disks shown in the following table.
Azure Resources
ADatum has an Azure subscription that contains an Azure AD tenant. Azure AD Connect is configured to sync the adatum.com forest with Azure AD.
The subscription contains the virtual networks shown in the following table.
The subscription contains the Azure Private DNS zones shown in the following table.
The subscription contains the virtual machines shown in the following table.
All the servers are in a workgroup.
The subscription contains a storage account named storage1 that has a file share named share1.
Requirements
Planned Changes
ADatum plans to implement the following changes:
• Sync Data1 to share1.
• Configure an Azure runbook named Task1.
• Enable Azure AD users to sign in to Server1.
• Create an Azure DNS Private Resolver that has the following configurations:
• Name: Private1
• Region: West US
• Virtual network: VNet1
• Inbound endpoint: SubnetB
• Enable users in the adatum.com domain to access the resources in the south.fabrikam.com domain.
Technical Requirements
ADatum identifies the following technical requirements:
• The data on SSPace1 must be available always.
• DC2 must become the schema master if DC1 fails.
• VM3 must be configured to enable per-folder quotas.
• Trusts must allow access to only the required resources.
• The users in the Marketing OU must have access to storage1.
• Azure Automanage must be used on all supported Azure virtual machines.
• A direct SSH session must be used to manage all the supported virtual machines on HyperV1.
You need to implement the planned change for Data1.
Which actions should you perform in sequence? To answer, drag the appropriate actions to the correct order. Each action may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point.
The suggested answer is correct
- Deploy the Storage Sync Service
- Install the Azure File Sync agent
- Create a sync group and a cloud endpoint
- Create a server endpoint
Yiannisthe7th
Highly Voted 6 months, 2 weeks ago
https://learn.microsoft.com/en-us/azure/storage/file-sync/file-sync-deployment-guide?tabs=azure-portal%2Cproactive-portal
upvoted 6 times
monisshk
Most Recent 4 months ago
1.Deploy the Storage Sync Service 2.Install the Azure File Sync agent 3.Create a sync group and a cloud endpoint 4.Create a server endpoint This question is valid Exam date - 27-07-2024
upvoted 3 times
NazerRazer
1 year ago
1. Deploy the Azure Storage Sync service. You need to deploy the Azure Storage Sync service in your Azure subscription to create a sync group. 2. Install and register the Azure File Sync agent. Install the Azure File Sync agent on each of your on-premises servers that you want to sync with Azure. 3. Add a server endpoint. After the Azure File Sync agent is installed, you configure server endpoints for the folders you want to sync on your on-premises servers. 4.Create a sync group. Once you've configured server endpoints, you can group them into a sync group. Sync groups define the sync topology. answer 3 and 4 are in the wrong order. Server endpoint first then a sync group.
upvoted 1 times
NazerRazer
1 year ago
im Wrong the order is correct as Chermosomorilla noted
upvoted 2 times
chermosomorilla
1 year ago
The answer provided is correct. A Server Endpoint cannot be added until the Sync Group exists, so the order must be: Deploy Azure Storage Sync Service, Install and register the Azure File Sync agent Create Sync Group Add Server Endpoint https://learn.microsoft.com/en-us/azure/storage/file-sync/file-sync-deployment-guide?tabs=azure-portal%2Cproactive-portal
upvoted 6 times