Preparing Practice Exam…
Please wait a moment while the system generates the exam questions, answers, and study session.
Please wait a moment while the system generates the exam questions, answers, and study session.
Microsoft 365 Certified: Endpoint Administrator Associate · Microsoft
Step Sequence / Reordering Question
Add and arrange the steps in the correct execution order.
Hotspot Solution:
ChatGPT o3: Correct answers Tag the device in Defender for Endpoint Set Device value = High from the device’s page in Defender for Endpoint. This flags it as high-value for vulnerability and alert prioritisation. Tag App1 in Defender for Cloud Apps Tagging App1 as Unsanctioned (or with any tag) syncs its domains to Defender for Endpoint. This triggers an "Unsanctioned cloud app access" alert when accessed. Why not the others* Critical asset classification in Defender XDR – requires creating a rule, doesn’t apply directly to a specific device. Tag in Defender for Identity – only marks it as “Sensitive,” used for identity-based detections, not device tagging or Cloud Discovery. IP indicator – not linked to SaaS app access from Cloud Discovery data.
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
Tag Server1 as a hgih-value device: Create a critical asset classification in Microsoft Defender XDR Ensure that an alert is triggered when App1 is accessed: Tag App1 in Defender for Cloud Apps Tested
Tag Device As High Value Device: Defender for Endpoint Alert on Access: Defender for Cloud Apps (Access Policy)
ChatGPT o3: *****Correct answers***** Tag the device in Defender for Endpoint Set Device value = High from the device’s page in Defender for Endpoint. This flags it as high-value for vulnerability and alert prioritisation. Tag App1 in Defender for Cloud Apps Tagging App1 as Unsanctioned (or with any tag) syncs its domains to Defender for Endpoint. This triggers an "Unsanctioned cloud app access" alert when accessed. ****Why not the others***** Critical asset classification in Defender XDR – requires creating a rule, doesn’t apply directly to a specific device. Tag in Defender for Identity – only marks it as “Sensitive,” used for identity-based detections, not device tagging or Cloud Discovery. IP indicator – not linked to SaaS app access from Cloud Discovery data.