MS-102 Question #9: Real Exam Question with Answer & Explanation

Question

Case Study 2 - Litware, Inc Overview Litware, Inc. is a consulting company that has a main office in Montreal and a branch office in Seattle. Litware collaborates with a third-party company named A. Datum Corporation. Environment On-Premises Environment The network of Litware contains an Active Directory domain named litware.com. The domain contains three organizational units (OUs) named LitwareAdmins, Montreal Users, and Seattle Users and the users shown in the following table. The domain contains 2,000 Windows 10 Pro devices and 100 servers that run Windows Server 2019. Cloud Environment Litware has a pilot Microsoft 365 subscription that includes Microsoft Office 365 Enterprise E3 licenses and Azure AD Premium P2 licenses. The subscription contains a verified DNS domain named litware.com. Azure AD Connect is installed and has the following configurations: - Password hash synchronization is enabled. - Synchronization is enabled for the LitwareAdmins OU only. Users are assigned the roles shown in the following table. Self-service password reset (SSPR) is enabled. The Azure AD tenant has Security defaults enabled. Problem Statements Litware identifies the following issues: - Admin1 cannot create conditional access policies. - Admin4 receives an error when attempting to use SSPR. - Users access new Office 365 service and feature updates before the updates are reviewed by Admin2. Requirements Planned Changes Litware plans to implement the following changes: - Implement Microsoft Intune. - Implement Microsoft Teams. - Implement Microsoft Defender for Office 365. - Ensure that users can install Office 365 apps on their device. - Convert all the Windows 10 Pro devices to Windows 10 Enterprise ES. - Configure Azure AD Connect to sync the Montreal Users OU and the Seattle Users OU. Technical Requirements Litware identifies the following technical requirements: - Administrators must be able to specify which version of an Office 365 desktop app will be available to users and to roll back to previous versions. - Only Admin2 must have access to new Office 365 service and feature updates before they are released to the company. - Litware users must be able to invite A. Datum users to participate in the following activities: - Join Microsoft Teams channels. - Join Microsoft Teams chats. - Access shared files. - Just in time access to critical administrative roles must be required. - Microsoft 365 incidents and advisories must be reviewed monthly. - Office 365 service status notifications must be sent to Admin2. - The principle of least privilege must be used. Question You need to configure Azure AD Connect to support the planned changes for the Montreal Users and Seattle Users OUs. What should you do?

Options

• AFrom PowerShell, run the Add-ADSyncConnectorAttributeInclusion cmdlet.
• BFrom the Microsoft Azure AD Connect wizard, select Manage federation.
• CFrom the Microsoft Azure AD Connect wizard, select Customize synchronization options.
• DFrom PowerShell, run the Start-ADSyncSyncCycle cmdlet.

Explanation

To include additional or optional attributes in Azure AD Connect synchronization (for example, adding attributes not synchronized by default, adjusting filtered OUs, or enabling optional features), you use the Azure AD Connect wizard and choose 'Customize synchronization options.' This path gives access to optional features, directory extension attributes, and OU/domain filtering. Option A (Add-ADSyncConnectorAttributeInclusion) is a PowerShell cmdlet that can manipulate connector attribute inclusion, but the recommended and supported path for this task is through the wizard. Option B ('Manage federation') deals with federation trust configuration, not attribute sync. Option D (Start-ADSyncSyncCycle) only triggers an existing sync cycle and does not change what attributes are synchronized.

No community discussion yet for this question.