This scenario is based on how Azure AD Multi-Factor Authentication (MFA) statuses transition between Disabled, Enabled, and Enforced states, as documented in the Microsoft SC-300: Microsoft Identity and Access Administrator Study Guide and Microsoft Learn - Configure and deploy MFA in Azure Active Directory.
Let's analyze the details step-by-step using the exhibits:
* Initial MFA Configuration (February 1, 2021)
* User1: Disabled
* User2: Enabled
* User3: Enforced
* MFA Policy Setting
* "Allow users to remember multi-factor authentication on devices they trust" is enabled.
* "Number of days users can trust devices for" is 20 days.This means that once a user completes MFA on a trusted device, they won't be prompted again for 20 days on that same device.
* User Sign-in Activity:
* User1: Signs in on Feb 2 and again on Feb 21
* User2: Signs in on Feb 5
* User3: Already in Enforced state (so continuous MFA enforcement applies) State Transitions per Microsoft Documentation:
* Disabled: User cannot register or use MFA.
* Enabled: User is registered for MFA but not yet required at every sign-in. Once they complete registration, they remain Enabled until admin enforces it.
* Enforced: User must use MFA at every sign-in.
Timeline Evaluation:
* User1 was initially Disabled, so even though they sign in multiple times (Feb 2 and Feb 21), MFA remains disabled unless the admin manually changes the setting - therefore, User1 = Disabled.
* User2 was Enabled on Feb 1, and signed in on Feb 5 - this allows them to register for MFA (move from Enabled # Enforced) once registration completes. By Feb 26, they would be in Enforced state.
* User3 was already Enforced from the start, and their state remains unchanged.
Thus, by February 26, 2021, the MFA status should be:
* User1: Disabled
* User2: Enforced
* User3: Enforced
This matches Option B exactly.
Microsoft references (Azure AD MFA Overview):
"Enabled users move to Enforced when they complete MFA registration. Enforced users must use MFA every time they sign in."

Explanation:

Within the Remediation tab of Microsoft Entra Permissions Management, the Permissions subtab allows you to view, filter, and manage the permissions directly assign ed to identities. It supports operations such as Read
, Update , and Delete on granted permissions.
If you need to change a user's permissions (for example, reduce all of User1's permissions to read-only), the quick action capability in the Permissions subta b is the most efficient method. Using the quick action, you can right-size, remove, or adjust permissions for a user in bulk across their assigned permissions. This is less administrative effort than creating new roles or templates The Roles/Policies subta b (option A) deals with role definitions (CRUD operations), not directly editing a given user's permissions.
The My Requests subtab (option B) is for requesting elevated permissions, not for bulk modifying existing assignments.
The Role/Policy Template tab (option D) is for defining templates; using them is less direct and more overhead when you already have assignments to adjust.
Hence, the correct and minimal-effort choice is to use the quick action in the Permissions subtab of the Remediation tab to chan ge User1's permissions to read-only.

According to the Microsoft SC-300: Identity and Access Administrator Study Guide and the Microsoft Learn module "Publish on-premises apps for remote access using Azure AD Application Proxy", Azure AD Application Proxy enables secure remote access to internal, on-premises web applications without requiring VPN access.
In the scenario, App1 is an on-premises application hosted within the Litware network, and the technical requirements specify that it must be securely accessible to both internal and external users - including Fabrikam guest accounts - through Azure AD authentication.
Microsoft's official documentation states:
"Azure AD Application Proxy provides se cure remote access to on-premises web applications, integrating with Azure AD for single sign-on (SSO) and conditional access policies." Given that the environment already includes a server (SERVER1) running the Azure AD Application Proxy connector, and that Litware wants to enforce Azure AD Conditional Access and MFA for App1, Azure AD Application Proxy is the correct implementation.
The other options are not suitable:
* A. Policy set in Microsoft Endpoint Manager: Used for device compliance and app management, not for publishing on-premises apps.
* B. App configuration policy in Endpoint Manager: Used for mobile app configuration (e.g., MAM policies), not for access publishing.
* C. App registration in Azure AD: Used for modern cloud or SaaS apps integration, but App1 is on- premises and needs proxy access.
answer: D. Azure AD Application Proxy
Topic 2, Litware, IncOverview
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 V PN connection.
Identity 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 s ynchronization 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 litw are.com by using gu est accounts in the litware.com tenant.
Cloud Environment
All the users at Litware have Microsoft 365 Enterprise E5 licenses. All the built-in anomaly detection polices in Microsoft Cloud App Security are enabled.
Litware has an Azure s ubscription 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 au dit logs.
On-premises Environment
The on-premises network contains the severs 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 on-premises domain controllers are prevented from accessing the internet.
Delegation Requirements
Litware identifies the following delegation requirements:
* Delegate the management of privileged roles by using Azure AD Pri vileged 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.
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 Microsoft
365 group that he appropriate license assigned.
Management Requirement
Litware wants to create a group named LWGroup1 will conta in all the Azure AD user accountsfor Litware but exclude all the Azure AD guest accounts.
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
Access 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.
Monitoring Requirements
Litware wants to use the Fusion rule in Azure Sentinel to detect multi-staged that include a combination of suspicious Azure AD sign-ins followed by anomalous Microsoft Office 365 activity.

The requirement is:
"Require admin approval for application access to organizational data." According to the Microsoft SC-300 exam guide and Microsoft documentation on "Configure consent settings for applications", Azure AD provides User consent settings under Enterprise applications # Consent and permissions to control how applications can request permissions to access organizational data.
By default, users can consent to allow apps to access organizational data on their behalf, which can create security risks. To ensure tighter control, administrators can:
* Disable user consent entirely, or
* Require admin consent workflow so that when users try to grant an app access, it must first be approved by an administrator.
The SC-300 study materials explicitly describe:
"To require administrator approval before an app can access organizational data, configure the User consent settings to use the admin consent workflow." This aligns perfectly with the stated requirement - to ensure admin approval is required before apps gain access to organizational data.
Other options are incorrect:
* Authentication methods manage MFA and SSPR, not app consent.
* Access packages are part of Identity Governance for resource access, not app consent.
* Application Proxy publishes on-premises apps, not related to app consent permissions.