更新时间: 试题数量: 购买人数: 提供作者:

有效期: 个月

章节介绍: 共有个章节

收藏
搜索
题库预览
Introductory Info Case Study - Overview - Litware, Inc. is a pharmaceutical company that has a subsidiary named Fabrikam, Inc. Litware has offices in Boston and Seattle, but has employees located across the United States. Employees connect remotely to either office by using a VPN connection. Existing Environment. Identify Environment The network contains an Active Directory forest named litware.com that is linked to an Azure Active Directory (Azure AD) tenant named litware.com. Azure AD Connect uses pass-through authentication and has password hash synchronization disabled. Litware.com contains a user named User1 who oversees all application development. Litware implements Azure AD Application Proxy. Fabrikam has an Azure AD tenant named fabrikam.com. The users at Fabrikam access the resources in litware.com by using guest accounts in the litware.com tenant. Existing Environment. Cloud Environment All the users at Litware have Microsoft 365 Enterprise E5 licenses. All the built-in anomaly detection policies in Microsoft Cloud App Security are enabled. Litware has an Azure subscription associated to the litware.com Azure AD tenant. The subscription contains an Azure Sentinel instance that uses the Azure Active Directory connector and the Office 365 connector. Azure Sentinel currently collects the Azure AD sign-ins logs and audit logs. Existing Environment. On-premises Environment The on-premises network contains the servers shown in the following table. (含图) Both Litware offices connect directly to the internet. Both offices connect to virtual networks in the Azure subscription by using a site-to-site VPN connection. All onpremises domain controllers are prevented from accessing the internet. Requirements. Delegation Requirements Litware identifies the following delegation requirements: Delegate the management of privileged roles by using Azure AD Privileged Identity Management (PIM). Prevent nonprivileged users from registering applications in the litware.com Azure AD tenant. Use custom catalogs and custom programs for Identity Governance. Ensure that User1 can create enterprise applications in Azure AD. Use the principle of least privilege. Requirements. Licensing Requirements Litware recently added a custom user attribute named LWLicenses to the litware.com Active Directory forest. Litware wants to manage the assignment of Azure AD licenses by modifying the value of the LWLicenses attribute. Users who have the appropriate value for LWLicenses must be added automatically to a Microsoft 365 group that has the appropriate licenses assigned. Requirements. Management Requirements Litware wants to create a group named LWGroup1 that will contain all the Azure AD user accounts for Litware but exclude all the Azure AD guest accounts. Requirements. Authentication Requirements Litware identifies the following authentication requirements: Implement multi-factor authentication (MFA) for all Litware users. Exempt users from using MFA to authenticate to Azure AD from the Boston office of Litware. Implement a banned password list for the litware.com forest. Enforce MFA when accessing on-premises applications. Automatically detect and remediate externally leaked credentials. Requirements. Access Requirements Litware identifies the following access requirements: Control all access to all Azure resources and Azure AD applications by using conditional access policies. Implement a conditional access policy that has session controls for Microsoft SharePoint Online. Control privileged access to applications by using access reviews in Azure AD. Requirements. Monitoring Requirements Litware wants to use the Fusion rule in Azure Sentinel to detect multi-staged attacks that include a combination of suspicious Azure AD sign-ins followed by anomalous Microsoft Office 365 activity.QuestionYou need to configure the MFA settings for users who connect from the Boston office. The solution must meet the authentication requirements and the access requirements. What should you include in the configuration?
Question #50 Case Study - Overview - ADatum Corporation is a consulting company in Montreal. ADatum recently acquired a Vancouver-based company named Litware, Inc. Existing Environment. ADatum Environment The on-premises network of ADatum contains an Active Directory Domain Services (AD DS) forest named adatum.com. ADatum has a Microsoft 365 E5 subscription. The subscription contains a veri?ed domain that syncs with the adatum.com AD DS domain by using Azure AD Connect. ADatum has an Azure Active Directory (Azure AD) tenant named adatum.com. The tenant has Security defaults disabled. The tenant contains the users shown in the following table. (含图) The tenant contains the groups shown in the following table. (含图) Existing Environment. Litware Environment Litware has an AD DS forest named litware.com Existing Environment. Problem Statements ADatum identi?es the following issues: • Multiple users in the sales department have up to ?ve devices. The sales department users report that sometimes they must contact the support Department to join their devices to the Azure AD tenant because they have reached their device limit. • A recent security incident reveals that several users leaked their credentials, a suspicious browser was used for a sign-in, and resources were Accessed from an anonymous IP address. • When you attempt to assign the Device Administrators role to IT_Group1, the group does NOT appear in the selection list. • Anyone in the organization can invite guest users, including other guests and non-administrators. • The helpdesk spends too much time resetting user passwords. • Users currently use only passwords for authentication. Requirements. Planned Changes - ADatum plans to implement the following changes: • Con?gure self-service password reset (SSPR). • Con?gure multi-factor authentication (MFA) for all users. • Con?gure an access review for an access package named Package1. • Require admin approval for application access to organizational data. • Sync the AD DS users and groups of litware.com with the Azure AD tenant. • Ensure that only users that are assigned speci?c admin roles can invite guest users. • Increase the maximum number of devices that can be joined or registered to Azure AD to 10. Requirements. Technical Requirements ADatum identi?es the following technical requirements: • Users assigned the User administrator role must be able to request permission to use the role when needed for up to one year. • Users must be prompted to register for MFA and provided with an option to bypass the registration for a grace period. • Users must provide one authentication method to reset their password by using SSPR. Available methods must include: - Email - Phone - Security questions - The Microsoft Authenticator app • Trust relationships must NOT be established between the adatum.com and litware.com AD DS domains. • The principle of least privilege must be used. You need to implement the planned changes for litware.com. What should you con?gure?
Introductory Info Case Study - Overview - Contoso, Ltd. is a consulting company that has a main office in Montreal and branch offices in London and Seattle. Contoso has a partnership with a company named Fabrikam, Inc. Fabrikam has an Azure Active Directory (Azure AD) tenant named fabrikam.com. Existing Environment. Existing Environment The on-premises network of Contoso contains an Active Directory domain named contoso.com. The domain contains an organizational unit (OU) named Contoso_Resources. The Contoso_Resources OU contains all users and computers. The contoso.com Active Directory domain contains the users shown in the following table. (含图) Existing Environment. Microsoft 365/Azure Environment Contoso has an Azure AD tenant named contoso.com that has the following associated licenses: Microsoft Office 365 Enterprise E5 Enterprise Mobility + Security Windows 10 Enterprise E3 Project Plan 3 Azure AD Connect is configured between Azure AD and Active Directory Domain Services (AD DS). Only the Contoso_Resources OU is synced. Helpdesk administrators routinely use the Microsoft 365 admin center to manage user Settings. User administrators currently use the Microsoft 365 admin center to manually assign licenses. All users have all licenses assigned besides the following exceptions: The users in the London office have the Microsoft 365 Phone System license unassigned. The users in the Seattle office have the Yammer Enterprise license unassigned. Security defaults are disabled for contoso.com. Contoso uses Azure AD Privileged Identity Management (PIM) to protect administrative roles. Existing Environment. Problem Statements Contoso identifies the following issues: Currently, all the helpdesk administrators can manage user licenses throughout the entire Microsoft 365 tenant. The user administrators report that it is tedious to manually configure the different license requirements for each Contoso office. The helpdesk administrators spend too much time provisioning internal and guest access to the required Microsoft 365 services and apps. Currently, the helpdesk administrators can perform tasks by using the User administrator role without justification or approval. When the Logs node is selected in Azure AD, an error message appears stating that Log Analytics integration is not enabled. Requirements. Planned Changes - Contoso plans to implement the following changes: Implement self-service password reset (SSPR). Analyze Azure audit activity logs by using Azure Monitor. Simplify license allocation for new users added to the tenant. Collaborate with the users at Fabrikam on a joint marketing campaign. Configure the User administrator role to require justification and approval to activate. Implement a custom line-of-business Azure web app named App1. App1 will be accessible from the internet and authenticated by using Azure AD accounts. For new users in the marketing department, implement an automated approval workflow to provide access to a Microsoft SharePoint Online site, group, and app. Contoso plans to acquire a company named Adatum Corporation. One hundred new ADatum users will be created in an Active Directory OU named Adatum. The users will be located in London and Seattle. Requirement. Technical Requirements Contoso identifies the following technical requirements: All users must be synced from AD DS to the contoso.com Azure AD tenant. App1 must have a redirect URI pointed to https://contoso.com/auth- response. License allocation for new users must be assigned automatically based on the location of the user. Fabrikam users must have access to the marketing departments SharePoint site for a maximum of 90 days. Administrative actions performed in Azure AD must be audited. Audit logs must be retained for one year. The helpdesk administrators must be able to manage licenses for only the users in their Respective office. Users must be forced to change their password if there is a probability that the usersidentity was compromised.QuestionYou need to meet the planned changes for the User administrator role. What should you do?
Introductory Info Case Study - Overview - Litware, Inc. is a pharmaceutical company that has a subsidiary named Fabrikam, Inc. Litware has offices in Boston and Seattle, but has employees located across the United States. Employees connect remotely to either office by using a VPN connection. Existing Environment. Identify Environment The network contains an Active Directory forest named litware.com that is linked to an Azure Active Directory (Azure AD) tenant named litware.com. Azure AD Connect uses pass-through authentication and has password hash synchronization disabled. Litware.com contains a user named User1 who oversees all application development. Litware implements Azure AD Application Proxy. Fabrikam has an Azure AD tenant named fabrikam.com. The users at Fabrikam access the resources in litware.com by using guest accounts in the litware.com tenant. Existing Environment. Cloud Environment All the users at Litware have Microsoft 365 Enterprise E5 licenses. All the built-in anomaly detection policies in Microsoft Cloud App Security are enabled. Litware has an Azure subscription associated to the litware.com Azure AD tenant. The subscription contains an Azure Sentinel instance that uses the Azure Active Directory connector and the Office 365 connector. Azure Sentinel currently collects the Azure AD sign-ins logs and audit logs. Existing Environment. On-premises Environment The on-premises network contains the servers shown in the following table. (含图) Both Litware offices connect directly to the internet. Both offices connect to virtual networks in the Azure subscription by using a site-to-site VPN connection. All onpremises domain controllers are prevented from accessing the internet. Requirements. Delegation Requirements Litware identifies the following delegation requirements: Delegate the management of privileged roles by using Azure AD Privileged Identity Management (PIM). Prevent nonprivileged users from registering applications in the litware.com Azure AD tenant. Use custom catalogs and custom programs for Identity Governance. Ensure that User1 can create enterprise applications in Azure AD. Use the principle of least privilege. Requirements. Licensing Requirements Litware recently added a custom user attribute named LWLicenses to the litware.com Active Directory forest. Litware wants to manage the assignment of Azure AD licenses by modifying the value of the LWLicenses attribute. Users who have the appropriate value for LWLicenses must be added automatically to aMicrosoft 365 group that has the appropriate licenses assigned. Requirements. Management Requirements Litware wants to create a group named LWGroup1 that will contain all the Azure AD user accounts for Litware but exclude all the Azure AD guest accounts. Requirements. Authentication Requirements Litware identifies the following authentication requirements: Implement multi-factor authentication (MFA) for all Litware users. Exempt users from using MFA to authenticate to Azure AD from the Boston office of Litware. Implement a banned password list for the litware.com forest. Enforce MFA when accessing on-premises applications. Automatically detect and remediate externally leaked credentials. Requirements. Access Requirements Litware identifies the following access requirements: Control all access to all Azure resources and Azure AD applications by using conditional access policies. Implement a conditional access policy that has session controls for Microsoft SharePoint Online. Control privileged access to applications by using access reviews in Azure AD. Requirements. Monitoring Requirements Litware wants to use the Fusion rule in Azure Sentinel to detect multi-staged attacks that include a combination of suspicious Azure AD sign-ins followed by anomalous Microsoft Office 365 activity.QuestionYou need to meet the authentication requirements for leaked credentials. What should you do? (1分)