You need to restrict cloud apps running on CUENT1 to meet the Microsoft Defender for Endpoint requirements. Which two configurations should you…

To restrict cloud applications on an endpoint using Microsoft Defender for Endpoint (MDE), you must leverage its integration with Microsoft Defender for Cloud Apps (MDCA). This process requires two primary configurations. First, the integration must be explicitly enabled within the MDE settings under 'Advanced features' in the Microsoft 365 Defender portal. Second, you must define which applications to block. This is accomplished within the MDCA portal's 'Cloud Discovery' dashboard by identifying the target application and tagging it as "unsanctioned." Once these two steps are completed, MDE will enforce the block policy on managed devices like CUENT1.

B. The Onboarding settings are for enrolling devices into Defender for Endpoint, a prerequisite step, not for configuring the specific app-blocking policy itself.

C. Anomaly detection policies are designed to generate alerts based on unusual user behavior, not to directly block access to applications.

1. Microsoft Learn. "Integrate Microsoft Defender for Endpoint." Microsoft Docs. Under the section "How to integrate Microsoft Defender for Endpoint with Defender for Cloud Apps

" Step 1 states: "In Microsoft 365 Defender

go to Settings > Endpoints > Advanced features. For Microsoft Defender for Cloud Apps

choose On." This directly supports option D.

2. Microsoft Learn. "Govern discovered apps using Microsoft Defender for Endpoint." Microsoft Docs. This document outlines the procedure for blocking apps. Under the section "How to block apps using Defender for Endpoint

" it details the process of navigating to the Cloud Discovery dashboard or Cloud app catalog and tagging an app as Unsanctioned. This supports option A.

3. Microsoft Learn. "Onboard devices and configure Microsoft Defender for Endpoint capabilities." Microsoft Docs. This resource describes the device enrollment process

confirming that "Onboarding settings" (Option B) are for initial setup rather than policy enforcement for app control.

4. Microsoft Learn. "Get behavioral analytics and anomaly detection." Microsoft Docs. This page explains that anomaly detection policies (Option C) are for identifying risks and generating alerts

stating

"The anomaly detection policies provide out-of-the-box user and entity behavioral analytics (UEBA) and machine learning (ML) so that you can immediately run advanced threat detection across your cloud environment." This confirms they do not directly block apps.