Courseiva

Microsoft Cybersecurity Architect (SC-100) — Questions 151–225

605 questions total · 9 pages · All types, answers revealed

Page 2

Page 3 of 9

Page 4
151
MCQmedium

Your organization wants to implement a zero-trust security model for on-premises and cloud resources. As part of this strategy, you need to ensure that all access requests are authenticated and authorized based on dynamic risk signals. Which Microsoft security solution should you use to enforce conditional access policies based on real-time risk?

A.Microsoft Entra ID Conditional Access
B.Microsoft Intune
C.Microsoft Sentinel
D.Microsoft Defender for Cloud
AnswerA

Microsoft Entra ID Conditional Access is the policy enforcement engine that operationalizes zero trust by evaluating real-time signals such as user identity, device health, location, and risk level at the moment of authentication. It dynamically allows or blocks access, or requires additional controls like MFA or session policies, integrated directly with identity authentication. This makes it the central decision point for enforcing conditional access policies, rather than a supporting or monitoring tool.

Why this answer

Microsoft Entra ID Conditional Access is the correct solution because it enables you to enforce access policies based on real-time risk signals, such as user risk, sign-in risk, and device compliance. It integrates with Identity Protection to evaluate dynamic risk levels and can block or require multi-factor authentication (MFA) accordingly, directly supporting the zero-trust principle of 'never trust, always verify'.

Exam trap

The trap here is that candidates often confuse Microsoft Sentinel (a SIEM) with a real-time access control solution, but Sentinel only provides detection and response after the fact, not inline policy enforcement during authentication.

How to eliminate wrong answers

Option B (Microsoft Intune) is wrong because it is a mobile device management (MDM) and mobile application management (MAM) solution that focuses on device compliance and app protection policies, not on real-time risk-based conditional access enforcement. Option C (Microsoft Sentinel) is wrong because it is a security information and event management (SIEM) and security orchestration automated response (SOAR) solution that aggregates logs and detects threats, but it does not natively enforce conditional access policies at the authentication layer. Option D (Microsoft Defender for Cloud) is wrong because it is a cloud security posture management (CSPM) and cloud workload protection platform (CWPP) that provides recommendations and threat protection for cloud workloads, not real-time risk-based access control for user sign-ins.

152
MCQmedium

You are designing a security solution for containers in Azure Kubernetes Service (AKS). The solution must scan container images for vulnerabilities before deployment and enforce runtime security. Which combination of Microsoft Defender for Cloud features should you enable?

A.Microsoft Defender for Containers
B.Microsoft Defender for App Service
C.Microsoft Defender for Cloud regulatory compliance dashboard
D.Microsoft Defender for Servers
AnswerA

Defender for Containers is the dedicated plan that directly scans container images in ACR (and other registries) for vulnerabilities, provides Kubernetes runtime threat detection by analyzing audit logs and node telemetry, and gives by-pod recommendations and drift prevention. It is the only Microsoft Defender for Cloud plan that natively covers the full container lifecycle on AKS, including cluster, node, and workload visibility.

Why this answer

Microsoft Defender for Containers (option A) is correct because it is the Defender for Cloud plan specifically designed for Kubernetes and container workloads, providing image vulnerability scanning in registries and at deployment, plus runtime threat detection for AKS clusters via the Defender sensor and admission control. It also delivers Kubernetes-native hardening recommendations and attack-path analysis, matching both the pre-deployment scanning and runtime enforcement requirements. Microsoft Defender for App Service (option B) protects web apps and App Service plans, not container images or AKS runtime.

The regulatory compliance dashboard (option C) only reports against standards and does not perform vulnerability scanning or runtime protection. Microsoft Defender for Servers (option D) covers VMs and server OS workloads, not container image scanning or Kubernetes runtime security.

153
MCQeasy

Your organization uses Microsoft Sentinel and wants to automatically respond to high-severity incidents without human intervention. Which feature should you configure?

A.Automation rule
B.Analytics rule
C.Workbook
D.Watchlist
AnswerA

An automation rule is the correct answer because it provides the incident-level response engine within Microsoft Sentinel. It evaluates configurable conditions (such as severity, tag, or entity properties) and then executes actions automatically—including triggering a playbook, changing incident status, assigning an owner, or adding tasks—without human intervention. Because it runs on every matching incident at creation or update, it directly implements the required automated response to Sentinel incidents.

Why this answer

Automation rules in Microsoft Sentinel allow you to define automated responses to incidents based on conditions such as severity, without requiring human intervention. When a high-severity incident is created or updated, an automation rule can trigger a playbook (via Azure Logic Apps) to perform actions like blocking an IP, resetting a user password, or creating a support ticket, enabling fully automated incident response.

Exam trap

The trap here is confusing the detection phase (analytics rules) with the response phase (automation rules), leading candidates to select analytics rules because they think 'automated response' is part of the detection logic, when in fact analytics rules only generate alerts, not automated actions.

How to eliminate wrong answers

Option B is wrong because analytics rules are used to generate alerts and incidents from raw data by defining detection logic (e.g., KQL queries), not to automate responses after an incident is created. Option C is wrong because workbooks are visualization tools that provide dashboards and reports on security data, not mechanisms for automated response actions. Option D is wrong because watchlists are collections of known indicators (e.g., IP addresses, hostnames) used for correlation and enrichment in queries, not for triggering automated remediation workflows.

154
MCQhard

Your organization plans to use Microsoft Purview to protect sensitive data in Microsoft 365. The compliance team needs to detect when users share credit card numbers via email and automatically apply encryption. Which solution should you implement?

A.Microsoft Purview Audit
B.Microsoft Purview eDiscovery
C.Microsoft Purview Information Protection
D.Microsoft Purview Data Loss Prevention (DLP)
AnswerD

Microsoft Purview Data Loss Prevention (DLP) policies continuously monitor emails for sensitive information types such as credit card numbers or social security numbers, and when a match is detected, the policy can automatically trigger protection actions. In Exchange Online, DLP leverages transport rules to apply IRM encryption to outbound messages, ensuring only intended recipients can read them. This capability directly aligns with the requirement to automatically encrypt emails based on content, making DLP the correct choice.

Why this answer

Microsoft Purview Data Loss Prevention (DLP) is the correct solution because it is specifically designed to detect sensitive data types—such as credit card numbers—in email messages and automatically apply protective actions like encryption. DLP policies can inspect email content in transit via Exchange Online, match patterns against predefined sensitive info types (e.g., credit card number regex), and trigger actions such as 'Encrypt the message' using Azure Rights Management. This directly meets the requirement to detect sharing of credit card numbers and enforce encryption automatically.

Exam trap

Microsoft often tests the distinction between Information Protection (labeling/classification) and Data Loss Prevention (content inspection and automated enforcement), leading candidates to pick Information Protection because they confuse 'protecting data' with 'detecting and acting on sensitive content.'

How to eliminate wrong answers

Option A is wrong because Microsoft Purview Audit only logs user and admin activities for forensic review; it cannot inspect email content for sensitive data or apply encryption. Option B is wrong because Microsoft Purview eDiscovery is used for searching and exporting content in legal or compliance investigations, not for real-time detection and automated protection of sensitive data in transit. Option C is wrong because Microsoft Purview Information Protection focuses on classifying and labeling documents and emails (e.g., sensitivity labels), but it does not natively scan for specific sensitive data patterns like credit card numbers or enforce automatic encryption based on content detection—that requires DLP policies to trigger the label or encryption action.

155
MCQhard

Refer to the exhibit. Your organization is required to comply with PCI DSS. You need to prioritize remediation efforts to meet PCI DSS requirements. Based on the exhibit, which recommendation should you address first?

A.Enable MFA on accounts with owner permissions
B.Migrate VMs from classic to ARM
C.Enable vulnerability assessment on SQL databases
D.Enable diagnostic logs in Key Vault
AnswerA

MFA on account owner permissions directly satisfies PCI DSS 8.3.1, which mandates multi-factor authentication for all administrative access to cardholder data environments. In Azure, the Owner role grants full control over all resource and security configurations, making it a primary target for credential compromise. Enabling MFA via Conditional Access or Azure AD security defaults is an immediate, auditable control that closes a current high-risk exposure and is a prerequisite for passing any PCI DSS assessment.

Why this answer

PCI DSS requires strong access control, including multi-factor authentication for remote access and for all accounts with administrative access. The recommendation 'MFA should be enabled on accounts with owner permissions' directly impacts PCI DSS requirements for authentication. While vulnerability assessment is important, MFA is a key control for PCI DSS.

The other recommendations are less directly related to PCI DSS.

156
MCQeasy

Your company uses Microsoft Sentinel for security operations. You need to detect brute-force attacks against Azure VMs by correlating failed sign-in events from multiple sources. Which data connector should you enable?

A.Azure Active Directory (now Microsoft Entra ID) sign-in logs connector.
B.Syslog connector.
C.Windows Security Events via AMA (Azure Monitor Agent) connector.
D.Azure Activity log connector.
AnswerC

The Windows Security Events via AMA connector is purpose-built to stream Windows Security log entries, including Event ID 4625 (failed sign-in), from Azure VMs and other Windows machines. It uses Azure Monitor Agent (AMA) to collect specified security event IDs and send them to Sentinel, enabling near-real-time detection and investigation of brute-force or credential-stuffing attempts. This connector also supports filtering by event ID, so you can efficiently ingest only 4625 and other high-value security events without overwhelming log storage.

Why this answer

The Windows Security Events via AMA connector is correct because it collects Windows security event logs—including failed logon events (Event ID 4625)—from Azure VMs into Microsoft Sentinel, enabling correlation of brute-force attempts across multiple sources. The Azure Active Directory (Microsoft Entra ID) sign-in logs connector only ingests Entra ID authentication events, not local or VM-level Windows logon failures. The Syslog connector targets Linux/network device logs (e.g., via rsyslog) and does not capture Windows Security event data.

The Azure Activity log connector records Azure control-plane operations (resource changes), not sign-in or authentication events.

157
MCQhard

Refer to the exhibit. You run this KQL query in Microsoft Sentinel. What is the primary purpose?

A.Correlate alerts across different data sources
B.Identify new high-severity alerts in the last 7 days
C.Detect entities that have been repeatedly targeted by high-severity alerts
D.Find entities with fewer than 5 high-severity alerts
AnswerC

The query groups high-severity alerts by CompromisedEntity and then filters the resulting aggregation to retain only entities with an `AlertCount > 5`. This directly identifies entities—such as users, hosts, or accounts—that have been hit by more than five high-severity alerts, indicating a pattern of repeated targeting. The `summarize` operation plus the having clause on the aggregated count is classic for detecting brute-force or persistent attack victims.

Why this answer

The KQL query uses `make_set` to aggregate distinct high-severity alert names per entity and filters for entities with more than 5 distinct alert types. This identifies entities that have been targeted by a high variety of high-severity alerts, indicating repeated or broad attack activity.

Exam trap

Candidates may overlook that `make_set` counts distinct alert names, not total alerts, and may also confuse the filter direction (`>5` vs `<5`), leading them to pick D. In reality, C is correct because a high number of distinct alert types indicates repeated targeting.

How to eliminate wrong answers

Option A is wrong because the query does not join or correlate alerts from different data sources; it only filters alerts by severity and aggregates by entity. Option B is wrong because the query does not identify new alerts; it counts distinct alert names over the last 7 days, not the recency of individual alerts. Option D is wrong because the query uses `array_length(make_set(...)) > 5`, which finds entities with more than 5 distinct high-severity alerts, not fewer than 5.

158
MCQhard

Your company uses Microsoft Purview Compliance Manager to track compliance with regulatory standards. You need to generate a report that shows the percentage of controls that are not yet implemented for the PCI DSS standard. What should you do?

A.In Compliance Manager, open the PCI DSS assessment and view the control status.
B.Create a Data Lifecycle Management policy for PCI DSS.
C.Create a custom risk assessment in Compliance Manager for PCI DSS.
D.Configure a Communication Compliance policy to monitor PCI DSS compliance.
AnswerA

Compliance Manager ships with a pre-built PCI DSS v3.2.1 or v4.0 assessment template that maps each requirement to customer actions and Microsoft-managed controls. Opening that assessment shows per-control status (e.g., Completed, In progress, Not started), implementation and testing evidence, ownership, and corrective actions. This is the direct, supported UI for monitoring PCI DSS compliance posture, and the status reflected is exactly what an auditor would expect to see.

Why this answer

The correct option is A: in Compliance Manager, open the PCI DSS assessment and view the control status, because Compliance Manager assessments include a controls view that shows each control's implementation status and progress percentages for the specific standard, which directly provides the percentage of controls not yet implemented. This is the built-in reporting surface for tracking regulatory compliance progress against PCI DSS. Option B is incorrect because Data Lifecycle Management policies govern retention and deletion of content, not compliance control reporting.

Option C is incorrect because custom risk assessments are for assessing risks, not for reporting control implementation percentages for a regulatory standard. Option D is incorrect because Communication Compliance policies detect policy violations in communications, not PCI DSS control implementation status.

159
MCQmedium

You are designing a secure access solution for a manufacturing company's IoT devices that send telemetry to Azure IoT Hub. The devices run on a private network with no internet access except through a firewall. You need to ensure that device-to-cloud communication is authenticated and encrypted, and that device credentials are rotated regularly. What should you include in the design?

A.Configure Azure Firewall to authenticate and encrypt device traffic.
B.Use X.509 certificates with Azure Device Provisioning Service (DPS) for automatic enrollment and certificate rotation.
C.Use shared access signature (SAS) tokens with a central key management system.
D.Assign managed identities to each IoT device.
AnswerB

X.509 certificates, when integrated with Azure Device Provisioning Service (DPS), enable automatic enrollment of IoT devices and support certificate rotation through DPS's built-in lifecycle management. DPS uses the certificate's common name (CN) to map devices to IoT Hub identities, and you can configure certificate renewal by attaching new certificates to the same enrollment group or individual enrollment. This meets all three requirements—authentication, encryption (via TLS with the certificate), and automated rotation—without manual per-device intervention.

Why this answer

Option B is correct because X.509 certificates provide mutual TLS authentication and encryption for device-to-cloud traffic to IoT Hub, and Azure Device Provisioning Service (DPS) supports automatic enrollment plus certificate rotation workflows (for example, via enrollment groups and rolling certificate updates), which directly meets the requirement for regularly rotated device credentials. Azure Firewall (A) is a network security control and does not authenticate or encrypt IoT device application traffic end-to-end. SAS tokens (C) can authenticate devices but are symmetric shared secrets that are harder to rotate safely at scale and do not provide the same certificate-based identity lifecycle as DPS-managed X.509.

Managed identities (D) are for Azure resources accessing Azure services and cannot be assigned to external IoT devices.

160
MCQeasy

Your company is deploying Microsoft Sentinel to centralize security logs from Azure, on-premises, and other clouds. You need to ensure logs are ingested cost-effectively while maintaining search performance for the last 30 days. What should you configure?

A.Store logs in Azure Blob Storage and use Azure Data Explorer for queries.
B.Use Log Analytics workspace with 30-day interactive retention and set long-term retention for older data.
C.Use Sentinel's free tier for 30 days and then move to paid tier.
D.Ingest logs into Azure Event Hubs and then into Sentinel.
AnswerB

A Log Analytics workspace with 30-day interactive retention provides Sentinel-native KQL query performance for the most recent month of security data, while long-term retention (archiving) keeps older telemetry in the same workspace at a lower storage cost without losing access—you can run search jobs to triage historical events. This configuration aligns with Sentinel’s architecture: Log Analytics is the underlying data store, interactive retention is optimized for frequent incident-hunting queries, and archived data remains queryable when needed, balancing cost and operational efficiency.

Why this answer

Option B is correct because Microsoft Sentinel stores ingested data in a Log Analytics workspace, where the interactive retention setting controls how long data remains available for fast KQL queries and analytics rules. Setting 30-day interactive retention satisfies the search-performance requirement for the last 30 days, while configuring long-term retention for older data keeps historical logs at a lower cost. The other options do not fit: Azure Blob Storage with Azure Data Explorer (A) is not Sentinel's native ingestion and query path, Sentinel has no 30-day free tier that then converts to paid (C), and Event Hubs (D) is only an ingestion pipeline, not a retention or query configuration.

161
MCQhard

Your organization uses Microsoft Sentinel. You need to design a solution to detect and automatically respond to a potential brute-force attack against an on-premises application that is published via Azure AD Application Proxy. The solution should block the attacker's IP address in Azure AD Conditional Access for one hour after detecting more than 10 failed login attempts within 5 minutes. What should you implement?

A.Create a Microsoft Purview Data Loss Prevention policy to block the IP address based on the login pattern.
B.Create a Microsoft Sentinel analytics rule that triggers on a KQL query detecting the failed logins, then use a playbook to add the IP to a Conditional Access block list via the Azure AD API.
C.Deploy a web application firewall (WAF) in front of the application and configure rate limiting to block the IP.
D.Configure a Microsoft Entra ID Protection sign-in risk policy to automatically block the user's sign-in after detecting anomalous activity.
AnswerB

Microsoft Sentinel can ingest sign-in logs from Azure AD Application Proxy. An analytics rule with a KQL query can detect the brute-force pattern, and when triggered, a playbook can call the Azure AD API to add the IP to a Conditional Access block list for one hour, effectively blocking the attacker.

Why this answer

You can create a Microsoft Sentinel analytics rule with a KQL query that detects more than 10 failed login attempts within 5 minutes. When the rule triggers, it runs a playbook that uses the Azure AD API to add the attacker's IP to a Conditional Access block list, blocking further access for one hour. Option A is incorrect because Microsoft Purview DLP policies are for data protection, not authentication blocking.

Option C is incorrect because a WAF rate limit blocks at the network layer but does not integrate with Azure AD Conditional Access, and it cannot read authentication logs from Azure AD App Proxy. Option D is incorrect because Microsoft Entra ID Protection sign-in risk policies are user-based and cannot block specific IPs or apply custom logic like a 1-hour block.

162
MCQmedium

Your company plans to use Microsoft Sentinel to detect threats across multiple Azure subscriptions. You need to design a cost-effective solution that ingests logs from all subscriptions. What should you use?

A.Use Azure Lighthouse to manage cross-subscription connectivity
B.Deploy a single Sentinel workspace and configure data collection rules to collect logs from all subscriptions
C.Create a separate Sentinel workspace for each subscription
D.Use Azure Policy to assign a Log Analytics workspace to each subscription
AnswerB

A single Microsoft Sentinel workspace, deployed once in a Log Analytics workspace, can serve as the central aggregation point for all subscriptions by configuring data collection rules (DCRs) and diagnostic settings to route resource logs, activity logs, and security signals into that one workspace. This design minimizes cost by avoiding duplicate ingestion and separate retention, simplifies querying and incident correlation across the entire environment, and allows you to manage one set of analytics rules, workbooks, and automation. For example, you can use Azure Policy to ensure all subscriptions apply the same DCR, pointing to the central workspace, thus combining enforcement with truly centralized ingestion.

Why this answer

Option B is correct because Microsoft Sentinel is built on a Log Analytics workspace, and a single workspace can ingest data from multiple Azure subscriptions via data collection rules (DCRs) and diagnostic settings, avoiding duplicated workspace and Sentinel costs. This centralized design is the most cost-effective since Sentinel pricing (ingestion and retention) applies per workspace, so consolidating into one workspace prevents paying for multiple Sentinel instances. Azure Lighthouse (A) is for delegated resource management across tenants, not for log ingestion into Sentinel.

Creating a separate workspace per subscription (C) multiplies Sentinel and Log Analytics costs and fragments detection. Azure Policy (D) can assign a workspace via DeployIfNotExists, but assigning a workspace per subscription still results in multiple workspaces rather than the single cost-effective workspace the scenario requires.

163
MCQmedium

Your organization uses Microsoft Purview. You need to design a solution that automatically detects and classifies sensitive data such as passport numbers stored in Microsoft OneDrive. The solution should apply a 'Highly Confidential' sensitivity label without user intervention. What should you configure?

A.Create an auto-labeling policy in Microsoft Purview that targets OneDrive and includes the 'Passport Number' sensitive info type.
B.Create a Data Loss Prevention (DLP) policy that blocks sharing of files with passport numbers.
C.Enable auditing in Microsoft Purview to track where passport numbers are stored.
D.Configure a manual sensitivity label and train users to apply it.
AnswerA

An auto-labeling policy in Microsoft Purview is designed to automatically evaluate content against sensitive info types like 'Passport Number' and apply the corresponding sensitivity label without user interaction. By targeting OneDrive locations, the policy continuously scans files, and when a match is found, it assigns the label and can enforce encryption or protection. This directly fulfills the requirement because classification happens automatically based on content inspection, not on user discretion or manual workflow.

Why this answer

Option A is correct because an auto-labeling policy in Microsoft Purview is the feature designed to automatically detect sensitive information types (such as 'Passport Number') in locations like OneDrive and apply a sensitivity label like 'Highly Confidential' without user intervention. Auto-labeling policies use the sensitive info type as a condition and can apply the label directly to matching content. Option B is incorrect because a DLP policy blocks or restricts sharing; it does not apply sensitivity labels.

Option C is incorrect because auditing only records activity and does not classify or label data. Option D is incorrect because manual labeling requires user action, which contradicts the no-user-intervention requirement.

164
MCQhard

Refer to the exhibit. You are analyzing an Azure PowerShell script that checks a blob property. The output of the last command returns 'False'. What does this indicate about the blob storage configuration?

A.Diagnostic logging is not configured for the container.
B.Access time tracking is disabled for the storage account.
C.The blob has an immutability policy applied.
D.Server-side encryption is disabled for the blob.
AnswerB

The Azure PowerShell output likely reveals that the storage account's LastAccessTimeTrackingPolicy.Enabled property is set to False. When this account-level feature is disabled, reads against blobs do not refresh their LastAccessTime property, leaving it stale or empty regardless of how frequently the blob is accessed. Enabling this policy via Set-AzStorageAccount -EnableLastAccessTimeTracking is a prerequisite for seeing current last-access timestamps, so the disabled state directly explains the unexpected value.

Why this answer

The correct answer is B: Access time tracking is disabled for the storage account. In Azure Storage, the blob property that reports whether last-access time tracking is enabled returns False when the account-level setting `LastAccessTimeTrackingPolicy` is not enabled, meaning the service is not recording last access times for blobs. Options A, C, and D are unrelated to this property: diagnostic logging is configured via Azure Monitor diagnostic settings, immutability policies are set through container/blob immutability settings, and server-side encryption is always enabled for Azure Storage blobs and is not reported by this property.

165
MCQhard

Your organization uses Microsoft Sentinel as its SIEM. You need to design a solution to automatically respond to detected threats in Azure resources. The response must include isolating the affected virtual machine and creating a support ticket. Which approach should you use?

A.Create a Microsoft Sentinel automation rule that triggers a playbook when an incident is generated. The playbook uses Azure Logic Apps to isolate the VM and create a ticket in your IT service management tool.
B.Create an Azure Policy initiative that automatically remediates non-compliant resources
C.Create a Microsoft Sentinel analytics rule that runs a KQL query and automatically sends an email to the security team
D.Create an Azure Automation runbook that runs on a schedule to check for threats and isolate VMs
AnswerA

An automation rule in Microsoft Sentinel is the native, event-driven mechanism that fires when an incident is generated, and it can invoke a playbook without any human intervention. The playbook, built in Azure Logic Apps, contains the orchestration steps to isolate the compromised VM—for example, by calling Microsoft Defender for Cloud or Azure Resource Manager to apply a network security group or an isolation action—and then create a ticket in your IT service management tool through its connector. This tightly integrates detection and response, ensuring a repeatable, auditable, and low-latency reaction to a security incident.

Why this answer

Microsoft Sentinel automation rules can trigger playbooks (Azure Logic Apps) when incidents are generated. Logic Apps provide native connectors to isolate Azure VMs (via the Azure Resource Manager connector) and create tickets in IT service management tools (e.g., ServiceNow, Jira), meeting both requirements in a single automated workflow.

Exam trap

The trap here is confusing scheduled or policy-based automation (Options B and D) with event-driven incident response, which requires a trigger tied to Sentinel incident creation and a playbook capable of multi-step actions like VM isolation and ITSM ticket creation.

How to eliminate wrong answers

Option B is wrong because Azure Policy initiatives enforce compliance at resource creation or configuration drift, not real-time threat response; they cannot isolate a VM already under attack or create a support ticket. Option C is wrong because analytics rules generate alerts or incidents but cannot perform automated actions like VM isolation or ticket creation; they only trigger email notifications. Option D is wrong because an Azure Automation runbook on a schedule cannot respond to threats in real time; it lacks integration with Sentinel incident triggers and cannot create tickets in an ITSM tool without custom code.

166
Matchingmedium

Match each security operations tool to its primary function.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts
Matches

Security information and event management

Extended detection and response (XDR)

Cloud security posture management

Identity risk detection and remediation

Data governance and compliance

Why these pairings

These tools form the Microsoft security operations stack. Sentinel handles SIEM/SOAR, Defender XDR provides XDR across domains, and Defender for Cloud secures cloud workloads.

167
MCQeasy

Your company uses Azure Virtual Machines (VMs) running Windows Server. You need to ensure that only approved applications can run on the VMs. Which Azure security feature should you use?

A.Azure Firewall
B.Azure Policy with application control
C.Microsoft Defender for Cloud
D.Just-in-Time VM access
AnswerB

Azure Policy with application control is the correct choice because it can enforce host-level application allowlisting on Azure VMs through Windows Defender Application Control (WDAC) or AppLocker via custom policy definitions. These policies are assigned across management groups or subscriptions, and they evaluate and enforce which executables are allowed to run, denying everything else. Since Azure Policy continuously audits and can remediate noncompliant resources, it provides the necessary governance and enforcement mechanism required for application control.

Why this answer

Azure Policy with application control is correct because it lets you enforce that only approved applications run on your Windows Server VMs by using the Guest Configuration extension to audit or deploy Windows Defender Application Control (WDAC) / AppLocker policies at scale. This directly addresses the requirement to restrict execution to approved applications. Azure Firewall (A) filters network traffic, not which applications execute on the VM.

Microsoft Defender for Cloud (C) provides security posture and threat protection but does not itself enforce an application allowlist. Just-in-Time VM access (D) restricts inbound management ports, not application execution.

168
MCQhard

You are designing a security solution for an Azure Kubernetes Service (AKS) cluster that runs containerized workloads. The cluster must be integrated with Microsoft Defender for Cloud for threat detection, and you need to ensure that container images are scanned for vulnerabilities before deployment. What should you configure?

A.Enable Microsoft Defender for Cloud Apps to discover and assess container vulnerabilities.
B.Deploy Azure Policy for Kubernetes with built-in policies to enforce image scanning.
C.Enable Azure Defender for Containers in Microsoft Defender for Cloud and integrate with Azure Container Registry for image scanning.
D.Configure Microsoft Sentinel to collect container logs and detect vulnerabilities.
AnswerC

Enable Azure Defender for Containers in Microsoft Defender for Cloud, which natively integrates with Azure Container Registry to provide vulnerability assessment for AKS workloads. When this option is enabled, Defender for Cloud scans every image in ACR using a Qualys-based scanner, which detects OS and package-level CVEs and provides remediation recommendations. This is the only option that directly provides image vulnerability scanning for containers, and it also adds runtime threat detection for AKS clusters, making it the correct and comprehensive answer for the security solution design.

Why this answer

The correct option is C: enabling Azure Defender for Containers in Microsoft Defender for Cloud and integrating it with Azure Container Registry provides native vulnerability scanning of container images and threat detection for AKS workloads. Defender for Containers specifically includes image scanning in ACR (on push and periodic rescanning) and surfaces findings in Defender for Cloud, which matches the requirement to scan images before deployment. Option A is wrong because Microsoft Defender for Cloud Apps is a CASB for SaaS discovery and governance, not container image scanning.

Option B is wrong because Azure Policy for Kubernetes enforces configuration and admission controls but does not itself perform vulnerability scanning of images. Option D is wrong because Microsoft Sentinel is a SIEM/SOAR platform for log collection and analytics, not an image vulnerability scanner.

169
Multi-Selecthard

A company wants to automate incident response in Microsoft 365 Defender. Which THREE actions can be automated using automated investigation and response (AIR) capabilities? (Choose three.)

Select 3 answers
A.Block a file hash across the organization.
B.Reset a user's password.
C.Isolate a device from the network.
D.Create a new user account.
E.Delete a malicious email from all mailboxes.
AnswersA, C, E

AIR can block indicators of compromise.

Why this answer

Microsoft 365 Defender's automated investigation and response (AIR) can automatically block a file hash at the tenant level using threat intelligence and cloud-delivered protection. When a malicious file is detected, AIR can create an indicator to block the hash across all endpoints via Microsoft Defender for Endpoint, preventing further execution.

Exam trap

Candidates often mistake identity-related actions like password resets as part of AIR, but these are handled by separate Azure AD Identity Protection workflows. AIR actions are limited to endpoint, email, and collaboration containment.

170
MCQhard

Your organization is designing a secure network infrastructure for a multi-cloud environment that includes Azure, AWS, and on-premises datacenters. The security team requires that all traffic between these environments be inspected for threats and that any malicious traffic be automatically blocked. The solution must minimize complexity and use a single pane of glass for policy management. Which Azure service should you use as the central hub?

A.Azure Front Door
B.Network Security Groups (NSGs)
C.Azure DDoS Protection
D.Azure Firewall
AnswerD

Azure Firewall is a fully stateful, centrally managed firewall-as-a-service that provides both network and application-level filtering (including FQDN rules and threat intelligence) for Azure virtual networks and hybrid connections over ExpressRoute or VPN. Deployed in a hub virtual network, it can inspect all inter-environment traffic via user-defined routes and forced tunneling, with native integration into Azure Monitor for centralized logging and alerting. This combination of centralized policy management, advanced inspection, and hybrid/multi-cloud applicability makes it the correct choice for a secure network infrastructure.

Why this answer

Azure Firewall (option D) is the correct choice because it provides a centralized, cloud-native firewall service that can inspect and filter traffic across Azure, AWS, and on-premises connections through a hub-and-spoke or Virtual WAN topology, with a single management plane via Azure Firewall Manager for policy and threat intelligence-based blocking. It supports FQDN filtering, threat intelligence, and IDPS, making it suitable for multi-cloud traffic inspection and automatic malicious traffic blocking while minimizing complexity. Azure Front Door (A) is a global HTTP/HTTPS load balancer and WAF for web applications, not a general network traffic inspection hub for multi-cloud and on-premises traffic.

Network Security Groups (B) are stateful packet filters at the subnet/NIC level with no central management pane or advanced threat inspection. Azure DDoS Protection (C) only mitigates volumetric DDoS attacks against Azure resources and does not inspect or block general malicious traffic across hybrid and multi-cloud environments.

171
Multi-Selecteasy

Which TWO of the following are features of Microsoft Defender for Cloud that help secure infrastructure? (Choose two.)

Select 2 answers
A.Secure Score
B.Incident investigation
C.Just-in-time VM access
D.Privileged Identity Management
E.User and Entity Behavior Analytics (UEBA)
AnswersA, C

Secure Score is a core feature of Microsoft Defender for Cloud that aggregates security findings and provides a numeric score based on the implementation of security controls and best practices. It helps organizations prioritize remediation actions by comparing current posture against benchmarks like Azure Security Benchmark and CIS. The score reflects the percentage of healthy security recommendations, and improving it directly reduces attack surface across compute, network, storage, and identity resources. It is not a separate product but an actionable dashboard within Defender for Cloud's Cloud Security Posture Management (CSPM) capability.

Why this answer

Secure Score (A) is a core Microsoft Defender for Cloud capability that continuously assesses your Azure resources and subscriptions against security recommendations and benchmarks, aggregating the results into a numeric score so you can prioritize hardening actions for your infrastructure. Just-in-time (JIT) VM access (C) is also a Defender for Cloud feature that reduces the attack surface of virtual machines by blocking inbound management ports (RDP 3389, SSH 22) by default and opening them only for approved, time-limited requests from authorized IPs. Both directly serve Defender for Cloud's mission of strengthening and monitoring infrastructure security posture.

Incident investigation (B) and User and Entity Behavior Analytics (E) are capabilities of Microsoft Sentinel (the SIEM/SOAR solution), not Defender for Cloud. Privileged Identity Management (D) is a separate Microsoft Entra ID (Azure AD) service for just-in-time privileged role activation and access reviews, not a Defender for Cloud infrastructure feature.

Exam trap

The trap here is that candidates confuse Defender for Cloud's posture management features (Secure Score, JIT) with Microsoft Sentinel's investigation and analytics capabilities (Incident investigation, UEBA), or with Azure AD's identity governance features (PIM), because all are part of the Microsoft security portfolio but serve distinct roles.

172
Multi-Selecthard

You are designing a solution to protect sensitive data in Azure Blob Storage. The data must be encrypted at rest using customer-managed keys (CMK) stored in Azure Key Vault. Additionally, you need to ensure that only specific virtual networks can access the storage account, and all access must be logged. Which three configurations should you implement? (Choose three.)

Select 3 answers
A.Enable Azure Storage logging for read and write requests
B.Enable Azure Storage encryption with customer-managed keys in Key Vault
C.Configure a firewall and virtual network service endpoint for the storage account
D.Enable Azure Files encryption at rest
E.Enable soft delete for blobs
AnswersA, B, C

Enabling Azure Storage logging captures read and write requests against blobs, producing the audit trail the scenario demands. Diagnostic logging records authenticated access details, satisfying the requirement that all access to the sensitive data be logged for later review.

Why this answer

Option B is correct because the scenario explicitly requires encryption at rest with customer-managed keys (CMK) stored in Azure Key Vault, which is achieved by configuring the storage account to use CMK encryption referencing a Key Vault key. Option C is correct because restricting access to specific virtual networks requires configuring the storage account firewall (network rules) and enabling a virtual network service endpoint (Microsoft.Storage) on the designated subnets so traffic reaches the storage account over the Azure backbone. Option A is correct because the requirement that all access be logged is satisfied by enabling Azure Storage logging (diagnostic logging for read and write requests) for the blob service, capturing authentication and access details.

Option D is incorrect because Azure Files encryption at rest is unrelated to Blob Storage and does not address CMK, network restriction, or logging for blobs. Option E is incorrect because soft delete for blobs is a data-protection/recovery feature that retains deleted blobs; it does not provide encryption with CMK, network access control, or access logging.

173
MCQhard

An organization is implementing a Zero Trust identity strategy. They have a mix of on-premises Active Directory and Azure AD. They want to enforce conditional access policies that require device compliance for accessing sensitive apps. However, some users report that their devices are not being evaluated for compliance even though they are enrolled in Microsoft Intune. What should the organization check first?

A.Ensure Intune compliance policies are assigned to the correct user groups
B.Confirm that devices are Azure AD Joined
C.Check if users have enabled multi-factor authentication
D.Verify that devices are registered in Azure AD
AnswerD

Device registration in Azure AD creates the unique device identity that ties the user, device, and compliance state together. Conditional Access’s 'Require device to be marked as compliant' grant depends on the device being registered (via Azure AD Join or Azure AD Registered) and having its compliance status reported by Intune. Without this registration, the compliance claim is absent, and the access request is blocked.

Why this answer

Device compliance evaluation in a hybrid identity environment requires that devices are registered in Azure AD (Azure AD Registration) so that Azure AD can associate the device identity with Intune compliance data. Even if a device is enrolled in Intune, without Azure AD registration, Conditional Access policies cannot evaluate its compliance status because the device identity is not recognized by Azure AD during authentication.

Exam trap

The trap here is that candidates assume Intune enrollment alone is sufficient for device compliance evaluation, but Azure AD registration is the prerequisite that links the device identity to Azure AD for Conditional Access to enforce compliance policies.

How to eliminate wrong answers

Option A is wrong because Intune compliance policies must be assigned to the correct user groups, but this does not affect whether a device is evaluated for compliance; it only determines which users' devices receive the policy. Option B is wrong because devices do not need to be Azure AD Joined; they can be Azure AD Registered (workplace-joined) or Hybrid Azure AD Joined, and Azure AD Joined is not a prerequisite for compliance evaluation. Option C is wrong because multi-factor authentication is an authentication requirement, not a device compliance requirement; enabling MFA does not cause a device to be evaluated for compliance.

174
MCQeasy

Your organization is implementing a Zero Trust security model. Which Microsoft security solution should you use to enforce conditional access policies based on user, device, location, and real-time risk signals?

A.Microsoft Entra ID Conditional Access
B.Microsoft Defender for Cloud Apps
C.Microsoft Intune
D.Microsoft Purview
AnswerA

Microsoft Entra ID Conditional Access is the direct policy engine for access control in a Zero Trust architecture. It continuously evaluates signals such as user identity, group membership, location, device compliance, and real-time risk (from Entra ID Protection) to enforce granular decisions like allow, deny, or require MFA. Because it applies these conditions to every sign-in and session in real time, it is the core mechanism for implementing 'explicit verification' in Zero Trust.

Why this answer

Microsoft Entra ID Conditional Access is the correct solution because it is the native policy engine in Azure AD that evaluates signals from user identity, device compliance, location (IP ranges or countries), and real-time risk from Microsoft Entra ID Protection to enforce access decisions. It directly implements the 'explicit verification' and 'assume breach' principles of Zero Trust by blocking or requiring step-up authentication based on these dynamic conditions.

Exam trap

The trap here is that candidates often confuse Microsoft Defender for Cloud Apps as the primary policy enforcement point because of its session monitoring capabilities, but it is actually a downstream consumer of Conditional Access decisions, not the engine that evaluates user, device, location, and risk signals in real time.

How to eliminate wrong answers

Option B is wrong because Microsoft Defender for Cloud Apps is a Cloud Access Security Broker (CASB) that provides shadow IT discovery, session controls, and data protection, but it does not natively enforce conditional access policies based on user, device, location, and risk signals—it integrates with Conditional Access for those decisions. Option C is wrong because Microsoft Intune is a Mobile Device Management (MDM) and Mobile Application Management (MAM) solution that manages device compliance and app protection policies, but it does not evaluate real-time risk signals or enforce access policies at the authentication layer. Option D is wrong because Microsoft Purview is a data governance, compliance, and information protection solution focused on data classification, labeling, and eDiscovery, not on enforcing authentication-time conditional access based on user, device, location, or risk.

175
MCQhard

Your organization uses Microsoft Entra ID with external identities. You need to design a solution that allows partners to self-service sign up using their existing Azure AD or Microsoft account credentials, while preventing them from accessing other resources. What should you use?

A.Microsoft Entra B2C
B.Microsoft Entra Identity Protection
C.Microsoft Entra B2B collaboration
D.Direct federation with partner's IdP
AnswerC

Microsoft Entra B2B collaboration is the correct choice because it allows external users to access apps with their own existing identities, and its self-service sign-up feature lets partners initiate access by providing their details without requiring a pre-configured federation trust. B2B collaboration creates guest accounts in your tenant, supports integration with various identity providers including Microsoft Entra ID and Google, and is designed specifically for business-to-business partnerships. This satisfies both the self-service and existing-credential requirements of the scenario.

Why this answer

Microsoft Entra B2B collaboration is correct because it lets you invite external partners as guest users who can redeem invitations and sign in with their existing work/school account (Azure AD) or Microsoft account, while access is scoped only to the resources you explicitly share. Guest users in B2B are represented in your tenant and governed by Conditional Access and entitlement management, so they cannot access other resources by default. Entra B2C is for customer-facing apps with local or social identities, not partner collaboration in your corporate tenant.

Identity Protection provides risk-based sign-in and user risk policies, not partner onboarding. Direct federation with a partner's IdP requires configuring a SAML/WS-Fed trust per partner and does not provide the self-service invitation and redemption model of B2B.

176
MCQmedium

A company is deploying Microsoft Defender for Cloud to protect a multi-cloud environment that includes Azure and AWS. The security team wants to prioritize the highest-risk recommendations. Which feature should they use to identify and focus on the most critical security issues?

A.Use Secure Score and its recommendations
B.Regulatory Compliance dashboard
C.Enable Defender for Cloud's enhanced security features
D.Review attack path analysis
AnswerA

Secure Score quantifies organizational security posture as a percentage by scoring controls across workloads. Each recommendation is mapped to a control and shows the potential score increase if remediated, directly enabling risk-based prioritization. Defender for Cloud's recommendations page defaults to sorting by Secure Score impact, so this is the primary mechanism for deciding what to remediate first.

Why this answer

Secure Score in Microsoft Defender for Cloud aggregates all security recommendations and assigns a score based on their relative risk and impact. By focusing on recommendations that most improve the Secure Score, the security team can systematically prioritize the highest-risk issues across both Azure and AWS resources. This directly aligns with the goal of identifying and focusing on the most critical security issues.

Exam trap

The trap here is that candidates often confuse 'enhanced security features' (which enable advanced detections) with 'prioritization features' (which rank recommendations by risk), leading them to select Option C instead of recognizing that Secure Score is the dedicated prioritization mechanism.

How to eliminate wrong answers

Option B is wrong because the Regulatory Compliance dashboard is designed to track adherence to specific compliance standards (e.g., SOC 2, ISO 27001) and does not inherently prioritize recommendations by risk; it focuses on compliance gaps rather than overall security risk. Option C is wrong because enabling enhanced security features (e.g., Defender for Servers, Defender for SQL) expands the scope of monitoring and threat detection but does not itself provide a prioritization mechanism; it is a prerequisite for advanced protections, not a prioritization tool. Option D is wrong because attack path analysis is a visual tool that maps potential attack vectors but is used for deep investigation of specific threats, not for broad prioritization of all recommendations; it is reactive and scenario-specific, not a holistic risk-ranking feature.

177
MCQeasy

Your company uses Microsoft Purview to classify and protect sensitive data. You need to automatically detect and protect credit card numbers in documents stored in SharePoint Online. Which solution should you implement?

A.Configure Azure Information Protection to automatically apply protection.
B.Apply a sensitivity label that encrypts documents with credit card numbers.
C.Create a Data Loss Prevention (DLP) policy to detect credit card numbers and block sharing.
D.Use Microsoft Defender for Cloud Apps to scan documents for credit card numbers.
AnswerC

A Microsoft Purview DLP policy is the correct tool because it uses built-in sensitive information types—such as 'Credit Card Number' with Luhn checksum validation—to inspect content stored in SharePoint Online and OneDrive for Business both at rest and when shared. Upon detection, the policy can automatically block external sharing, deny access, or display a policy tip to the user, thereby directly preventing the data loss scenario described in the question.

Why this answer

The correct answer is C: create a Data Loss Prevention (DLP) policy to detect credit card numbers and block sharing. In Microsoft Purview, DLP policies are the built-in mechanism that inspects SharePoint Online content for sensitive information types such as credit card numbers and enforces protective actions like blocking external sharing or restricting access. This directly matches the requirement to automatically detect and protect credit card numbers in SharePoint Online documents.

Option A is incorrect because Azure Information Protection is a labeling/encryption client, not a policy engine that automatically detects sensitive data in SharePoint. Option B is incomplete because a sensitivity label alone does not automatically detect credit card numbers unless combined with auto-labeling conditions, and it does not block sharing. Option D is incorrect because Defender for Cloud Apps focuses on cloud app discovery, session controls, and anomaly detection rather than enforcing DLP rules on SharePoint content.

178
MCQhard

A company deploys Azure Bastion in a VNet. They want to allow a security engineer to connect to a Windows VM in a peered VNet using Azure Bastion. The engineer can see the VM in the portal but cannot connect. Which configuration is most likely missing?

A.The Azure Bastion subnet size is /28.
B.The peered VNet does not have 'Allow Azure Bastion Communication' enabled on the peering connection.
C.The VM's subnet does not have an inbound NSG rule allowing RDP (3389) from the Azure Bastion subnet.
D.The VM does not have Azure AD authentication enabled.
AnswerB

The 'Allow Azure Bastion Communication' setting on a VNet peering connection is specifically required for Bastion to communicate with resources in a peered VNet. This setting must be enabled on both sides of the peering relationship: the VNet that contains the Bastion host and the VNet that contains the target VM. If this setting is disabled on either side, the Bastion service cannot establish a session to the VM's private IP, even if other network paths are open. The peering setting is the explicit gate for cross-VNet Bastion access, making it the correct root cause.

Why this answer

Azure Bastion requires the 'Allow Azure Bastion Communication' setting to be enabled on the peering connection for the peered VNet. Without this, the Bastion service cannot route traffic to the target VM in the peered VNet, even though the VM is visible in the portal. This setting allows the Bastion's control plane and data plane to communicate across the peering link.

Exam trap

The trap here is that candidates assume NSG rules on the VM subnet are the primary blocker, but Azure Bastion's peering requirement is a distinct, often-missed setting that controls cross-VNet connectivity.

How to eliminate wrong answers

Option A is wrong because a /28 subnet size is the minimum required for Azure Bastion and is not a connectivity issue; the engineer can see the VM, indicating the Bastion is deployed correctly. Option C is wrong because Azure Bastion uses its own private IPs (from the AzureBastionSubnet) to connect to VMs, and NSG rules on the VM's subnet are not required—Bastion bypasses them via the service's built-in network hardening. Option D is wrong because Azure AD authentication is optional for RDP connections via Bastion; the default username/password or certificate-based authentication works without Azure AD.

179
MCQeasy

You are designing a secure access solution for an Azure Kubernetes Service (AKS) cluster that hosts a critical application. You need to ensure that only authorized users can access the Kubernetes API server. Which authentication method should you use?

A.Use Kubernetes service account tokens.
B.Use AKS managed identities for each user.
C.Use Azure RBAC for Kubernetes authorization.
D.Integrate AKS with Microsoft Entra ID for authentication.
AnswerD

AKS can be integrated with Microsoft Entra ID so that the Kubernetes API server delegates authentication to the Entra ID tenant. Users obtain an Entra ID token (e.g., via device code or OIDC) and present it to the API server; the server validates the token and maps the user to a cluster role. This solves the problem of managing separate Kubernetes identities for each human user, provides multi-factor authentication, conditional access, and centralized lifecycle management, and enables per-user auditing. Without this integration, AKS simply can't natively authenticate human users to the API server, so this is the correct approach for a secure access solution centered on user authentication.

Why this answer

The correct option is D: integrate AKS with Microsoft Entra ID for authentication, because this scenario requires authenticating human users who access the Kubernetes API server, and Entra ID integration provides centralized identity-based authentication with conditional access, MFA, and group-based access. AKS supports Entra ID integration so that kubectl and other clients obtain Entra ID tokens that the API server validates, ensuring only authorized users can authenticate. Option A is not suitable because service account tokens are for workloads and automation inside the cluster, not for authenticating external users.

Option B is incorrect because managed identities are Azure resource identities for services, not per-user Kubernetes API authentication. Option C is incorrect because Azure RBAC for Kubernetes authorization controls what an already-authenticated principal can do, not how users are authenticated.

180
MCQhard

Refer to the exhibit. You are reviewing a Conditional Access policy in Microsoft Entra ID. The policy is enabled but users who are detected as high risk are still able to sign in. What is the most likely reason?

A.No users or groups are assigned to the policy
B.The policy state is set to 'enabled' but not 'enforced'
C.The user risk level is set to 'high' but sign-in risk is 'medium'
D.The grant control is set to 'block' but should be 'require MFA'
AnswerA

Conditional Access policies only evaluate sign-ins for identities explicitly included in the assignments. With no users or groups assigned, the policy is enabled yet never applies, so high-risk users sign in unimpeded despite the configured risk condition.

Why this answer

A Conditional Access policy must have at least one user or group assigned to it to be evaluated. If no users or groups are assigned, the policy is effectively inactive, even if enabled. In this scenario, the policy is enabled but not applied to any identities, so high-risk users are not subject to its controls.

Exam trap

The SC-100 exam often tests the misconception that an enabled policy is automatically applied to all users, but the trap here is that the policy must have explicit assignments to take effect.

How to eliminate wrong answers

Option B is wrong because Conditional Access policies do not have an 'enforced' state; they are either 'enabled' or 'disabled'. An enabled policy is active and enforced. Option C is wrong because the user risk level and sign-in risk are separate conditions; setting user risk to 'high' does not require sign-in risk to be set, and the policy would still block high-risk users if assigned.

Option D is wrong because the grant control 'block' is the correct setting to prevent sign-ins; changing it to 'require MFA' would allow sign-ins with MFA, not block them.

181
Multi-Selecteasy

Which TWO Microsoft Purview features can be used to classify and label data in Microsoft 365?

Select 2 answers
A.Retention policies
B.eDiscovery
C.Auto-labeling policies
D.Audit logs
E.Sensitive info types
AnswersC, E

Auto-labeling policies in Microsoft Purview automatically apply sensitivity labels to documents and emails when they meet specified conditions, such as containing sensitive info types or matching trainable classifiers. These policies can run in simulation mode to test their impact, then be configured to auto-apply labels, directly fulfilling the requirement to classify content by labeling it based on detected data characteristics.

Why this answer

Auto-labeling policies (C) are a Microsoft Purview Information Protection capability that automatically applies sensitivity labels to content by scanning items for sensitive data, so they directly classify and label data in Microsoft 365. Sensitive info types (E) are the pattern-based classifiers (for example, credit card or national ID patterns) that define what sensitive data looks like and are used by auto-labeling and other Purview rules to classify data. Retention policies (A) govern how long content is kept or deleted rather than classifying or labeling it, eDiscovery (B) is used for identifying and collecting content for legal cases, and Audit logs (D) record user and admin activity for investigation and compliance reporting, so none of these three perform classification or labeling.

182
MCQmedium

Your company uses Microsoft Sentinel as its SIEM. You need to design a solution that automatically responds to high-severity incidents by creating a ticket in ServiceNow and notifying the security team via Teams. Which Sentinel feature should you configure?

A.Workbooks
B.Automation rules
C.Analytics rules
D.Hunting queries
AnswerB

Automation rules are the core mechanism in Microsoft Sentinel for centrally managing and executing automated response actions. They run whenever an incident is created or updated, and can perform actions such as triggering playbooks, changing incident severity, assigning ownership, adding tags, or applying custom logic. You can scope automation rules by analytics rule, severity, or other conditions, making them the purpose-built and correct answer for automating response in Sentinel.

Why this answer

Automation rules in Microsoft Sentinel are designed to trigger automated responses to incidents based on conditions like severity. They can integrate with external systems via playbooks (Azure Logic Apps) to create ServiceNow tickets and send Teams notifications, making them the correct choice for this requirement.

Exam trap

The trap here is that candidates often confuse Analytics rules (which generate alerts) with Automation rules (which respond to incidents), failing to recognize that incident response orchestration requires the latter's trigger-and-action pipeline.

How to eliminate wrong answers

Option A is wrong because Workbooks are visualization tools for querying and displaying data, not for automated response actions. Option C is wrong because Analytics rules generate alerts from log data but do not directly orchestrate multi-step responses like ticket creation or Teams notifications. Option D is wrong because Hunting queries are proactive, ad-hoc searches for threats and do not provide automated incident response capabilities.

183
Multi-Selecthard

Which THREE Microsoft security solutions can be used to detect and respond to threats across hybrid cloud environments? (Choose three.)

Select 3 answers
A.Microsoft Defender for Cloud
B.Microsoft Sentinel
C.Microsoft Defender for Office 365
D.Microsoft Intune
E.Microsoft Defender for Identity
AnswersA, B, E

Microsoft Defender for Cloud is a cloud-native application protection platform (CNAPP) specifically designed to detect and respond to threats across hybrid and multicloud environments. It provides security alerts for compute, storage, databases, and containers, extending on-premises coverage through Azure Arc. Unlike email or device management tools, Defender for Cloud directly performs workload-level threat detection, making it a correct solution for this scenario.

Why this answer

Microsoft Defender for Cloud (A) is correct because it provides Cloud Security Posture Management (CSPM) and Cloud Workload Protection Platform (CWPP) capabilities that continuously assess and protect Azure, AWS, GCP, and on-premises resources, generating security alerts and recommendations across hybrid environments. Microsoft Sentinel (B) is correct because it is a cloud-native SIEM and SOAR solution that ingests data from hybrid sources via connectors, correlates it with analytics rules, and enables automated threat detection and response through playbooks. Microsoft Defender for Identity (E) is correct because it monitors on-premises Active Directory Domain Services signals and integrates with Defender for Cloud Apps and Sentinel to detect identity-based attacks such as lateral movement and credential theft in hybrid identity scenarios.

Microsoft Defender for Office 365 (C) is not correct because it focuses on protecting email, collaboration, and Office apps from phishing and malware, not on broad hybrid cloud threat detection and response. Microsoft Intune (D) is not correct because it is a mobile device and endpoint management (MDM/MAM) service for configuration and compliance, not a threat detection and response solution for hybrid cloud workloads.

Exam trap

The trap here is that candidates often confuse Microsoft Defender for Office 365 with a broader hybrid cloud security solution, but it is limited to the Microsoft 365 suite and does not cover compute, network, or identity threats across hybrid cloud workloads.

184
MCQhard

A financial services company is designing a secure infrastructure for their Azure SQL Database. They need to encrypt data at rest using customer-managed keys (CMK) stored in a key vault with soft-delete and purge protection enabled. The encryption must be transparent to applications. What should they configure?

A.Azure Information Protection
B.Dynamic Data Masking
C.Always Encrypted
D.Transparent Data Encryption (TDE) with Azure Key Vault
AnswerD

Transparent Data Encryption (TDE) with Azure Key Vault is the correct choice because it performs real-time encryption and decryption of the entire database, including backups and transaction logs, at the storage layer. Using customer-managed keys in Azure Key Vault provides advanced key control and separation of duties, satisfying compliance requirements without requiring any application changes. TDE is a transparent, whole-database encryption solution ideales for financial services environments.

Why this answer

Azure SQL Database supports Transparent Data Encryption (TDE) with CMK in Azure Key Vault. Always Encrypted is for column-level encryption. Dynamic Data Masking is for masking, not encryption.

Azure Information Protection is for classification.

185
MCQhard

Your company is deploying a new AI-powered customer service chatbot using Azure OpenAI Service. The chatbot will access customer data stored in Azure Cosmos DB. The security team requires that all data in transit is encrypted, and that the chatbot only accesses data necessary for its function. Additionally, the chatbot must use managed identities to authenticate to Cosmos DB. You need to design the security architecture. Which combination of controls should you implement?

A.Restrict network access to the chatbot's IP address. Use a system-assigned managed identity and assign the Cosmos DB Account Reader role.
B.Use a connection string with the Cosmos DB account key and enforce TLS 1.2. Grant the chatbot's managed identity contributor role.
C.Enable TLS enforcement on Cosmos DB. Use a managed identity for the chatbot and assign the Cosmos DB Built-in Data Reader role. Configure the chatbot to authenticate using the managed identity.
D.Use Azure AD authentication with a service principal and assign the Cosmos DB Built-in Data Contributor role. Enforce TLS 1.2.
AnswerC

Enabling TLS on Cosmos DB encrypts all data in transit, protecting the AI chatbot's queries and responses from interception. A system-assigned or user-assigned managed identity for the chatbot lets it authenticate to Azure AD without storing any secrets in code or configuration. Assigning the Cosmos DB Built-in Data Reader role grants only read access to the actual data containers (the data plane), satisfying the function's read-only requirement while following least privilege.

Why this answer

It enforces TLS for data in transit, uses a managed identity for authentication, and assigns the Cosmos DB Built-in Data Reader role to implement least privilege access. Option A is incorrect because IP restrictions alone do not provide authentication and the Account Reader role does not allow data access. Option B is incorrect because using a connection string exposes secrets and the Contributor role grants excessive permissions.

Option D is incorrect because it uses a service principal instead of a managed identity, which is a requirement.

186
MCQmedium

Your company uses Microsoft Defender XDR to protect endpoints. The security team wants to implement automated response actions when a malicious file is detected on a device. Which Microsoft security feature should you configure to automatically isolate the affected device from the network?

A.Automated investigation and response (AIR) capabilities
B.Microsoft Sentinel automation rules
C.Attack surface reduction rules
D.Microsoft Intune compliance policies
AnswerA

Automated investigation and response (AIR) is a built-in Microsoft Defender XDR engine that orchestrates detection, investigation, and remediation across endpoints. When malicious activity such as a suspected ransomware or credential theft is identified, AIR can automatically perform device isolation — a native action that severs the endpoint's network connections while preserving communication with Defender for Endpoint services. This isolation can be executed without human intervention or with approval depending on the automation level configured, making it the appropriate capability for this requirement.

Why this answer

Automated investigation and response (AIR) in Microsoft Defender XDR is the correct feature because it includes built-in playbooks that can automatically isolate a device from the network when a malicious file is detected. AIR leverages the Microsoft 365 Defender portal's automation capabilities to run investigation steps and execute response actions, such as device isolation, without manual intervention. This directly meets the requirement for automated response upon file detection.

Exam trap

The trap here is that candidates often confuse the proactive prevention capabilities of Attack surface reduction rules with the automated response capabilities of AIR, or they overestimate the real-time response abilities of Intune compliance policies, which are designed for configuration enforcement rather than incident response actions like network isolation.

How to eliminate wrong answers

Option B is wrong because Microsoft Sentinel automation rules are designed for cloud-scale SIEM and SOAR across multiple data sources, not for endpoint-specific automated isolation triggered by Defender XDR detections; they require custom analytics and playbooks to achieve similar behavior, making them less direct for this use case. Option C is wrong because Attack surface reduction rules are proactive policies that block or audit specific behaviors (e.g., Office apps creating child processes) to prevent infection, but they do not perform automated response actions like device isolation after a file is already detected as malicious. Option D is wrong because Microsoft Intune compliance policies enforce device configuration and health requirements (e.g., requiring encryption or a minimum OS version) and can trigger conditional access blocks, but they cannot automatically isolate a device from the network in real time based on a malicious file detection; that action is outside Intune's scope.

187
MCQhard

A company needs to design a secure DevOps pipeline using GitHub Actions and Microsoft Defender for Cloud. They want to scan infrastructure-as-code (IaC) templates for misconfigurations before deployment. What should they integrate?

A.Microsoft Defender for Cloud Infrastructure as Code scanning
B.Microsoft Purview Compliance Manager
C.Microsoft Sentinel
D.Microsoft Defender for Cloud Apps
AnswerA

Microsoft Defender for Cloud Infrastructure as Code scanning is the correct choice because it directly integrates with DevOps platforms like GitHub and Azure DevOps to continuously scan Infrastructure as Code templates (e.g., ARM, Bicep, Terraform) in pull requests and pipelines. It leverages Defender for Cloud's security recommendations and policy library to identify misconfigurations before deployment, preventing insecure cloud resources from ever being provisioned. This is a native cloud security posture management capability purpose-built for IaC validation.

Why this answer

Microsoft Defender for Cloud includes a native Infrastructure as Code (IaC) scanning capability that integrates directly with GitHub Actions. This feature automatically analyzes IaC templates (such as ARM, Bicep, Terraform, and CloudFormation) for security misconfigurations during the CI/CD pipeline, providing pre-deployment guardrails. By failing the pipeline on critical findings, it ensures only compliant infrastructure is deployed, aligning with the secure DevOps principle of shifting security left.

Exam trap

The trap here is that candidates often confuse Microsoft Defender for Cloud's IaC scanning with Microsoft Sentinel's threat detection capabilities, mistakenly thinking Sentinel can scan code before deployment, when in fact Sentinel only analyzes logs and alerts from already-deployed resources.

How to eliminate wrong answers

Option B (Microsoft Purview Compliance Manager) is wrong because it focuses on regulatory compliance posture management and risk assessments, not on scanning IaC templates for misconfigurations in a DevOps pipeline. Option C (Microsoft Sentinel) is wrong because it is a SIEM and SOAR solution for threat detection and incident response after deployment, not a pre-deployment IaC scanning tool. Option D (Microsoft Defender for Cloud Apps) is wrong because it is a CASB (Cloud Access Security Broker) for controlling user access and data protection in SaaS applications, not for scanning infrastructure code.

188
Multi-Selectmedium

Which TWO of the following are valid methods to secure Azure Kubernetes Service (AKS) workloads?

Select 2 answers
A.Integrate Azure AD for cluster authentication
B.Apply Network Security Groups to pod subnets
C.Deploy Azure Firewall in front of the AKS cluster
D.Use Azure Front Door to protect API endpoints
E.Use Azure Policy with Azure Policy for AKS (Gatekeeper)
AnswersA, E

Integrating Azure AD for AKS cluster authentication authenticates Kubernetes identities against Azure AD, enabling identity-based access control. It supports assigning Kubernetes RBAC roles to Azure AD users, groups, or service principals, and allows conditional access policies to protect the cluster API server. This provides a control-plane security mechanism that centrally manages access and audits via Azure AD sign-in logs, rather than relying on local Kubernetes accounts.

Why this answer

Option A is correct because integrating Azure Active Directory (Azure AD) with AKS enables cluster authentication and authorization via Azure RBAC, allowing you to control who can access the Kubernetes API server and manage workloads using identity-based controls rather than static credentials. Option E is correct because Azure Policy for AKS uses the Gatekeeper admission controller (Open Policy Agent) to enforce policies on pods and cluster resources at admission time, preventing non-compliant workloads from being deployed and thus hardening the workload configuration. Option B is not the intended answer because Network Security Groups apply at the subnet/NIC level for network traffic filtering, not specifically for securing AKS workloads at the pod or admission level, and pod-level security typically uses Kubernetes Network Policies.

Option C is not correct in this context because Azure Firewall provides network perimeter protection and egress filtering but does not directly secure AKS workloads themselves. Option D is not correct because Azure Front Door is a global HTTP/HTTPS load balancer and WAF for web applications, not a mechanism for securing AKS workloads internally.

189
Multi-Selecteasy

A company wants to implement a Zero Trust security model. Which TWO principles are fundamental to Zero Trust? (Choose two.)

Select 2 answers
A.Verify explicitly.
B.Use perimeter-based security.
C.Trust internal network.
D.Trust but verify.
E.Assume breach.
AnswersA, E

Verify explicitly is the foundational Zero Trust principle that mandates every access request be authenticated, authorized, and encrypted based on all available data points, including user identity, device health, location, and data sensitivity. It eliminates any implicit trust derived from network location or previous interactions, requiring continuous validation for each transaction. This principle ensures that access is granted only after a thorough, real-time assessment, making it the correct core principle for Zero Trust.

Why this answer

Option A (Verify explicitly) is correct because Zero Trust requires every access request to be authenticated and authorized based on all available data points—user identity, device health, location, and resource sensitivity—rather than granting implicit trust based on network location. Option E (Assume breach) is correct because Zero Trust operates on the principle that threats may already exist inside the environment, so organizations must minimize blast radius, segment access, encrypt traffic end-to-end, and use analytics to detect and respond to anomalies. Option B (Use perimeter-based security) is incorrect because Zero Trust explicitly rejects the castle-and-moat perimeter model in favor of identity-centric controls that follow the user and device.

Option C (Trust internal network) is incorrect because Zero Trust assumes no implicit trust for traffic originating from the corporate LAN or VPN. Option D (Trust but verify) is incorrect because it implies initial trust is granted before verification, which contradicts Zero Trust's requirement to verify every request explicitly and continuously.

Exam trap

The trap here is that candidates often confuse 'trust but verify' (Option D) with Zero Trust, but Microsoft explicitly defines Zero Trust as 'never trust, always verify,' making 'trust but verify' a legacy approach that still assumes initial trust.

190
MCQmedium

Your organization uses Microsoft Sentinel for security information and event management (SIEM). You need to create an analytics rule that detects when a user account is created outside of business hours from an unusual IP address. Which type of rule should you use?

A.Anomaly rule
B.Scheduled query rule
C.ML Behavior Analytics rule
D.Fusion rule
AnswerB

Scheduled query rules in Microsoft Sentinel let you author a KQL query that runs at a defined interval (for example, every 5 minutes) and can alert when the result set meets a specified condition. With KQL you can filter sign-in activity, aggregate by user, and compare the count of failed attempts to your threshold, giving you full control over the detection logic. This is the only rule type among the options that supports arbitrary custom KQL and deterministic alerting for a specific pattern.

Why this answer

The correct option is B, a Scheduled query rule, because this rule type lets you write a KQL query against your log data (e.g., SecurityEvent or AuditLogs) and schedule it to run at defined intervals, which is exactly what's needed to detect user account creation events filtered by time-of-day and unusual source IP conditions. Scheduled query rules support custom detection logic, entity mapping, and alert/incident generation, making them ideal for this scenario. Anomaly rules (A) are built-in templates that detect deviations from learned baselines and don't let you author arbitrary detection logic for specific conditions like account creation outside business hours.

ML Behavior Analytics rules (C) are also prebuilt Microsoft-defined detections for specific behaviors, not customizable queries. Fusion rules (D) correlate multiple signals across products to detect multi-stage attacks and are not designed for a single custom condition like this.

191
Drag & Dropmedium

Order the steps to configure Azure Key Vault firewall and virtual network service endpoints.

Drag or tap steps into the slots.

Steps
Order
1Step 1
2Step 2
3Step 3
4Step 4

Why this order

The correct sequence for configuring Azure Key Vault firewall and virtual network service endpoints begins by enabling the service endpoint for Microsoft.KeyVault on the target subnet. Next, you add a virtual network rule in the Key Vault firewall settings that references that subnet. Optionally, you can configure the firewall to allow trusted Microsoft services.

Finally, you save the configuration to apply all changes. This order ensures that network rules are valid and the firewall behaves as expected.

192
Multi-Selectmedium

Your organization uses Microsoft Entra ID and Microsoft Intune. You need to design a solution that allows only hybrid Azure AD joined devices to access a sensitive application. The solution must also require that the device is compliant with company policies. Which two components should you configure? (Choose TWO.)

Select 2 answers
A.Intune app protection policy
B.Conditional Access policy with 'Require multifactor authentication'
C.Conditional Access policy with 'Require hybrid Azure AD joined device'
D.Intune device enrollment
E.Intune device compliance policy
AnswersC, E

A Conditional Access policy targeting the sensitive application with the 'Require hybrid Azure AD joined device' grant control blocks every device lacking that join state, satisfying the hybrid-only constraint at authentication time. Combined with a compliance requirement, it enforces both conditions before a token is issued.

Why this answer

Option C is correct because a Conditional Access policy with the 'Require hybrid Azure AD joined device' grant control enforces that only devices registered as hybrid Azure AD joined can access the sensitive application, directly satisfying the device-trust requirement. Option E is correct because an Intune device compliance policy defines and evaluates the rules (such as OS version, encryption, and password requirements) that determine whether a device is compliant, and Conditional Access can then require a compliant device. Together, C and E let Conditional Access grant access only when the device is both hybrid Azure AD joined and compliant.

Option A is not correct because Intune app protection policies (MAM) protect app data on mobile devices and do not enforce hybrid Azure AD join or device compliance for Conditional Access. Option B is not correct because requiring multifactor authentication verifies the user, not the device's join state or compliance. Option D is not correct because device enrollment merely onboards devices into Intune; it does not itself enforce the hybrid join or compliance requirements at access time.

Exam trap

SC-100 often tests whether candidates confuse device compliance with device join state or MFA, leading them to select app protection policies or MFA-only Conditional Access when the requirement explicitly demands hybrid join and compliance.

193
MCQhard

Your company is migrating to a cloud-native security operations center (SOC) using Microsoft Sentinel. You need to design a solution that automatically investigates and remediates common incidents like brute-force attacks on Azure VMs. The solution should use playbooks triggered by analytics rules. Which Microsoft service should you use to create the playbooks, and what is the recommended authentication method?

A.Power Automate with user account
B.Azure Automation with service principal
C.Azure Logic Apps with managed identity
D.Azure Functions with API key
AnswerC

Azure Logic Apps is the underlying service for Sentinel playbooks, offering a native Microsoft Sentinel trigger that provides incident context to workflow actions. When a Logic Apps workflow uses a managed identity, it accesses Azure AD-protected resources without storing secrets, simplifying credential management and enabling granular role assignments; this aligns with cloud-native security principles and is the recommended authentication model.

Why this answer

Azure Logic Apps is the recommended platform for Sentinel playbooks. Managed identity is the preferred authentication method because it avoids credential management and supports automation. Azure Automation is for runbooks, not playbooks.

Service principal is possible but not recommended due to credential management.

194
MCQmedium

Wide World Importers uses Azure Active Directory (now Microsoft Entra ID) and Microsoft 365. They have a hybrid identity with password hash sync. They want to implement a passwordless authentication strategy to improve security and user experience. They have a mix of Windows 10/11 devices and mobile devices (iOS/Android). They also have some shared computers in kiosk mode. The solution must support all user scenarios and align with Microsoft's authentication best practices. What should you recommend?

A.Use SMS-based authentication for all users. Deploy OATH tokens for shared computers. Implement Azure AD Conditional Access to require passwordless for admins only.
B.Implement Windows Hello for Business for all Windows devices. Use smart cards for mobile devices. Use FIDO2 keys for shared computers.
C.Implement Windows Hello for Business for Windows 10/11 devices. Deploy Microsoft Authenticator for mobile devices for passwordless sign-in. Use FIDO2 security keys for shared computers and kiosk scenarios. Enable combined registration for self-service password reset and Microsoft Authenticator.
D.Use the Microsoft Authenticator app for all users. Configure passwordless sign-in with the app. Use QR codes for kiosk computers.
AnswerC

Windows Hello for Business covers Windows 10/11 with hardware-bound credentials, Microsoft Authenticator enables phone sign-in for iOS/Android, and FIDO2 keys suit shared kiosks where per-user enrolment is impractical. Combined registration lets users set up SSPR and Authenticator together, satisfying the mixed-device and kiosk constraints.

Why this answer

It aligns with Microsoft's passwordless authentication best practices by using Windows Hello for Business for Windows 10/11 devices (which supports biometric and PIN-based sign-in), Microsoft Authenticator for mobile devices (enabling phone-sign-in passwordless authentication), and FIDO2 security keys for shared computers and kiosk scenarios (which provide hardware-backed, phishing-resistant credentials). Combined registration streamlines the user enrollment process for both SSPR and Microsoft Authenticator, ensuring a seamless deployment across all device types.

Exam trap

The trap here is that candidates may assume SMS-based authentication or smart cards are acceptable passwordless methods, but Microsoft's best practices explicitly exclude SMS due to security weaknesses and smart cards due to lack of mobile device support, while FIDO2 keys are the only recommended solution for shared/kiosk computers.

How to eliminate wrong answers

Option A is wrong because SMS-based authentication is not truly passwordless (it relies on a phone number and one-time code, which is susceptible to SIM-swap attacks and does not meet Microsoft's passwordless best practices), and OATH tokens for shared computers are not a recommended passwordless solution for kiosk scenarios (FIDO2 keys are preferred for phishing resistance). Option B is wrong because smart cards are not a practical or supported passwordless solution for mobile devices (iOS/Android do not natively support smart card authentication without additional hardware and middleware), and Windows Hello for Business is not available on all Windows devices (it requires Windows 10/11 Pro or Enterprise with TPM 2.0, and shared computers in kiosk mode may not support it). Option D is wrong because using Microsoft Authenticator for all users ignores Windows Hello for Business for Windows devices (which provides a better integrated experience), and QR codes for kiosk computers are not a supported passwordless authentication method for shared devices (FIDO2 keys are required for kiosk scenarios).

195
Multi-Selectmedium

Your organization is designing a privileged access strategy using Microsoft Entra ID. Which TWO configurations should be part of the design to protect privileged accounts?

Select 2 answers
A.Require multi-factor authentication for all administrative roles via Conditional Access
B.Enable security defaults
C.Implement Privileged Identity Management (PIM) for just-in-time access
D.Enable self-service password reset for admins
E.Disable multi-factor authentication for emergency admin accounts
AnswersA, C

Conditional Access allows MFA policies to be scoped specifically to administrative roles (e.g., Global Administrator, Privileged Role Administrator), applying risk-based and device-compliance conditions at sign-in. This provides granular control over when and where MFA is enforced, which is essential for privileged access because stolen admin credentials become insufficient without a second factor. Unlike blanket security defaults, this can also exclude break-glass accounts while still securing all other admins.

Why this answer

Options A and C are correct. Option A: Conditional Access with MFA for admin roles reduces risk of credential theft. Option C: Privileged Identity Management (PIM) provides just-in-time access and approval workflows.

Option B is wrong because security defaults enforce MFA for all users but lack granularity for privileged roles. Option D is wrong because self-service password reset is not specific to privileged accounts and does not protect against misuse. Option E is wrong because disabling MFA would weaken security.

196
MCQmedium

Refer to the exhibit. You are reviewing an Azure Policy definition. What does this policy accomplish?

A.Requires that all network security rules have destination port range between 22 and 3389
B.Denies all inbound traffic except SSH and RDP
C.Allows only SSH and RDP inbound traffic
D.Denies creation of network security rules that allow traffic to ports other than 22 and 3389
AnswerD

This is correct because the policy definition uses the 'deny' effect on Microsoft.Network/networkSecurityGroups/securityRules whose destinationPortRange or destinationPortRanges include values not in ['22', '3389']. When a user or service attempts to create or update an NSG rule that permits traffic to any port other than 22 or 3389, the Resource Manager deployment is rejected before the rule is applied, making it impossible to add such a rule to an NSG. The policy does not, however, automatically delete existing noncompliant rules; it applies at deployment time, so already-existing rules that violate the condition remain until manually changed or removed.

Why this answer

The correct option is D: the policy denies creation of network security rules that allow traffic to ports other than 22 and 3389. Azure Policy definitions with a deny effect evaluate the properties of a resource being deployed—here, the destinationPortRange of a network security rule—and block the deployment when the condition is met, so rules permitting any port outside 22 and 3389 are rejected. Option A is wrong because the policy does not require ports to fall within a range; it blocks rules that allow ports other than the two specified.

Option B is wrong because the policy targets NSG rule definitions in Azure Resource Manager, not live inbound traffic flows. Option C is wrong because the policy does not permit or allow traffic; it only denies noncompliant rule creation.

197
Multi-Selectmedium

You are designing a solution to protect Microsoft 365 data from insider threats. Which TWO Microsoft Purview features should you use?

Select 2 answers
A.Microsoft Purview Insider Risk Management
B.Microsoft Purview Data Loss Prevention (DLP)
C.Microsoft Purview Communication Compliance
D.Microsoft Purview Audit (Premium)
E.Microsoft Purview eDiscovery (Premium)
AnswersA, B

Microsoft Purview Insider Risk Management applies machine learning and behavioral analytics to signal anomalies in user activity—such as mass file downloads, unusual external sharing, or data staging—and then scores the risk to enable investigation and response. It is purpose-built to identify exfiltration patterns that indicate malicious or negligent insiders, making it the most directly relevant control for this scenario. Its built-in investigation workflow, templates, and correlation across activity signals provide proactive detection that other tools lack.

Why this answer

Microsoft Purview Insider Risk Management (A) is correct because it is the purpose-built solution for detecting and remediating insider threat activity, using machine learning and behavioral signals (such as mass downloads, exfiltration to personal cloud storage, or unusual file access) to surface risky user activity and trigger investigation workflows. Microsoft Purview Data Loss Prevention (B) is also correct because DLP policies can identify and block sensitive information (for example, credit card numbers, HIPAA data, or custom sensitive info types) from being shared inappropriately across Exchange Online, SharePoint, OneDrive, Teams, and endpoint devices, directly mitigating insider exfiltration scenarios. Communication Compliance (C) is not the right fit here because it focuses on monitoring and reviewing potentially inappropriate or policy-violating communications (harassment, regulatory compliance in chats/email), not on detecting or preventing data exfiltration by insiders.

Audit (Premium) (D) provides long-term retention and high-value forensic events for investigations, but it is a logging/investigation capability rather than a protective control against insider threats. eDiscovery (Premium) (E) is designed for legal hold, identification, collection, and review of content for litigation or investigations, not for proactively protecting data from insider risk.

Exam trap

The trap here is that candidates often confuse Data Loss Prevention (DLP) as the primary insider threat tool, but DLP is a content-aware policy enforcement mechanism that blocks or alerts on data sharing based on rules, whereas Insider Risk Management focuses on behavioral analytics and user risk scoring to detect threats that DLP might miss, such as slow data exfiltration or credential misuse.

198
MCQhard

Contoso Ltd. is a multinational organization with a hybrid environment consisting of on-premises Active Directory and Azure AD (now Microsoft Entra ID). They use Microsoft Defender for Cloud Apps, Microsoft Sentinel, and Microsoft 365 Defender. The security operations team has noticed that several high-severity alerts from Microsoft 365 Defender are not being forwarded to Microsoft Sentinel, causing delayed response. The team has confirmed that the data connector between Microsoft 365 Defender and Sentinel is enabled and appears healthy. However, only low-severity alerts appear in Sentinel. Further investigation reveals that the Microsoft 365 Defender portal has a configured rule set that suppresses high-severity alerts for certain users deemed low risk. The security operations manager wants to ensure all high-severity alerts are sent to Sentinel without changing the suppression rules in Microsoft 365 Defender, as those rules are required for operational efficiency. What should the team do to ensure high-severity alerts are ingested into Sentinel?

A.Modify the suppression rules in Microsoft 365 Defender to not suppress high-severity alerts.
B.In the Microsoft 365 Defender data connector in Sentinel, enable the option to include suppressed alerts.
C.Use the Microsoft Graph Security API connector in Sentinel to ingest alerts instead.
D.Create a separate Logic App to fetch high-severity alerts from Microsoft 365 Defender API and send them to Sentinel.
AnswerB

The Microsoft 365 Defender data connector in Microsoft Sentinel includes a configuration option called 'include suppressed alerts' that, when enabled, ingests all alerts regardless of their suppression status in Defender. This setting is the intended, supported mechanism to ensure high-severity alerts that are suppressed in the Defender console still appear in Sentinel for correlation, hunting, and incident response. Enabling this option preserves the existing suppression rules for day-to-day analyst workflows while giving Sentinel full visibility, exactly satisfying the manager's requirement to keep suppression rules unchanged and preventing missed alerts.

Why this answer

The Microsoft 365 Defender data connector in Microsoft Sentinel includes a configuration setting to 'Include suppressed alerts.' Enabling this option forces Sentinel to ingest all alerts from Microsoft 365 Defender, including those that are suppressed by rule sets in the Defender portal. This satisfies the requirement to forward high-severity alerts without modifying the suppression rules that the operations team relies on for operational efficiency.

Exam trap

The trap here is that candidates assume suppressed alerts are permanently hidden and cannot be ingested, leading them to choose either modifying the suppression rules (Option A) or building a custom workaround (Option D), when in fact the Sentinel connector has a specific toggle to include suppressed alerts.

How to eliminate wrong answers

Option A is wrong because it directly contradicts the requirement to keep the suppression rules unchanged; modifying the rules would break operational efficiency. Option C is wrong because the Microsoft Graph Security API connector ingests alerts from various Microsoft security products but does not bypass the suppression logic applied within Microsoft 365 Defender; suppressed alerts would still be omitted unless the API is specifically configured to include them, which is not a standard option. Option D is wrong because creating a separate Logic App to fetch high-severity alerts via the Microsoft 365 Defender API would be a complex, custom workaround that duplicates functionality already built into the Sentinel connector, and it would still need to handle the suppression flag to retrieve suppressed alerts, making it less efficient and more error-prone than the native connector option.

199
Multi-Selectmedium

A company is implementing a Zero Trust identity strategy. They want to ensure that only compliant and managed devices can access corporate resources. Which THREE components should they include in their solution? (Choose three.)

Select 3 answers
A.Microsoft Intune for device management and compliance policies
B.Azure AD device registration
C.Azure AD Conditional Access policies
D.Azure AD Application Proxy
E.Azure AD B2B collaboration
AnswersA, B, C

Microsoft Intune enforces device compliance and management state, which Microsoft Entra ID then evaluates through Conditional Access before granting resource access. This directly satisfies the stem's requirement that only compliant, managed devices connect, supplying the device signal Zero Trust needs for policy enforcement.

Why this answer

Microsoft Intune (A) is the correct MDM/MAM service for enforcing device compliance policies (e.g., encryption, OS version, jailbreak detection) and marking devices as managed or compliant, which is the foundation for device-based Zero Trust access. Azure AD device registration (B) is required so devices have an identity in Azure AD (registered, joined, or hybrid-joined), enabling Conditional Access to evaluate device state and compliance signals. Azure AD Conditional Access policies (C) are the policy engine that enforces the requirement that only compliant and managed devices can access corporate resources, using conditions and grant controls tied to device compliance.

Azure AD Application Proxy (D) is a remote-access/publishing solution for on-premises web apps and does not enforce device compliance or management. Azure AD B2B collaboration (E) governs external guest user access and is unrelated to ensuring devices are managed and compliant.

Exam trap

The trap here is that candidates may confuse Azure AD Application Proxy (a publishing tool) with a device compliance mechanism, or assume Azure AD B2B collaboration can enforce device management for external users, when in fact neither component evaluates device health or management status.

200
MCQeasy

You need to design a security operations strategy for a hybrid environment using Microsoft Sentinel. Your environment includes on-premises servers and Azure VMs. Which data connector should you use to collect security events from both sources?

A.Azure Activity log connector
B.Windows Security Events via AMA connector
C.Office 365 connector
D.Syslog connector
AnswerB

The Windows Security Events via AMA connector uses the Azure Monitor Agent to collect Windows operating system security events, including common Event IDs such as 4624 (successful logon) and 4625 (failed logon), from both Azure VMs and Arc-enabled on-premises servers. Because it relies on AMA, it provides a single, consistent agent for hybrid environments and supports data collection rules to filter specific security event IDs. This direct, native collection path makes it the correct choice for the scenario.

Why this answer

The Windows Security Events via AMA connector is correct because the Azure Monitor Agent (AMA) can be installed on both on-premises Windows servers (via Azure Arc) and Azure VMs, allowing Windows security events to be collected and ingested into Microsoft Sentinel from both sources. This connector uses Data Collection Rules (DCRs) to define which event sets (e.g., All Events, Common, Minimal) are streamed to the Log Analytics workspace. The Azure Activity log connector only captures Azure control-plane/subscription-level operations, not OS security events from servers.

The Office 365 connector ingests audit logs from Microsoft 365 services, and the Syslog connector targets Linux/Unix or network appliances via syslog, not Windows security events.

Exam trap

Candidates may mistakenly choose the Azure Activity log connector, thinking it covers all Azure resource logs, but it does not capture Windows Security Events from VMs.

201
MCQeasy

The exhibit shows a conditional access policy from Microsoft Entra ID Identity Protection. When will this policy require MFA?

A.When user risk is medium or high AND sign-in risk is high
B.When either user risk is medium or sign-in risk is high
C.When user risk is medium or high, regardless of sign-in risk
D.When sign-in risk is high, regardless of user risk
AnswerA

In Microsoft Entra Conditional Access, when both user risk and sign-in risk are specified as conditions, they are evaluated together using AND logic. The policy only applies when the user risk is medium or high and the sign-in risk is high simultaneously, so both conditions are required to trigger access controls. This matches the policy configuration exactly.

Why this answer

The conditional access policy shown in the exhibit uses the 'Require MFA' grant control with conditions set for user risk (medium or high) AND sign-in risk (high). In Microsoft Entra ID Identity Protection, when both risk levels are evaluated together with an AND operator, MFA is only triggered when both conditions are met simultaneously. This ensures that MFA is enforced only when the user account itself is compromised (medium/high user risk) and the current sign-in session is also risky (high sign-in risk), providing a layered security response.

Exam trap

The trap here is that candidates often confuse the AND operator with OR, assuming that either risk condition alone would trigger MFA, but the exhibit explicitly shows both conditions must be satisfied simultaneously.

How to eliminate wrong answers

Option B is wrong because it describes an OR condition (either user risk medium OR sign-in risk high), but the policy uses an AND operator, meaning both conditions must be true. Option C is wrong because it ignores the sign-in risk condition entirely, suggesting MFA is required regardless of sign-in risk, which contradicts the policy's explicit requirement for high sign-in risk. Option D is wrong because it ignores the user risk condition, stating MFA is required when sign-in risk is high regardless of user risk, but the policy requires user risk to be medium or high as well.

202
MCQhard

A government agency, Northwind, is deploying a sensitive application on Azure App Service Environment (ASE) v3. The application handles classified data and must meet FedRAMP High requirements. You need to design a security solution that includes: (1) encryption at rest for the app's content and configuration, (2) encryption in transit with TLS 1.2 or higher, (3) network isolation using VNet integration and private endpoints, (4) identity-based access to Azure SQL Database using managed identity, and (5) certificate management for custom domains using Azure Key Vault. Which of the following designs meets all requirements?

A.Deploy the app on a multi-tenant App Service plan, enforce HTTPS only with TLS 1.2, use a system-assigned managed identity to access Azure SQL Database, and configure TLS/SSL certificates from Azure Key Vault.
B.Deploy the app on an ASE v3 in a VNet, enforce HTTPS only with TLS 1.2, use a system-assigned managed identity to access Azure SQL Database, and configure TLS/SSL certificates from Azure Key Vault.
C.Deploy the app on an ASE v3 in a VNet, enforce HTTPS only with TLS 1.2, use a user-assigned managed identity to access Azure SQL Database, and configure TLS/SSL certificates from App Service certificates.
D.Deploy the app on an ASE v3 in a VNet, enforce HTTPS only with TLS 1.2, use a service principal to access Azure SQL Database, and configure TLS/SSL certificates from Azure Key Vault.
AnswerB

ASE v3 provides the isolated VNet deployment, HTTPS-only with TLS 1.2 satisfies encryption in transit, the system-assigned managed identity enables passwordless Microsoft Entra ID authentication to Azure SQL Database, and Key Vault supplies the custom-domain certificates, meeting every stated constraint.

Why this answer

Option B is correct because ASE v3 provides a fully isolated, single-tenant App Service environment deployed into a customer VNet, which is required for FedRAMP High and network isolation. It also correctly combines HTTPS-only with TLS 1.2, a system-assigned managed identity for passwordless Azure SQL authentication, and Key Vault for certificate management — all of which are supported natively in ASE v3. The other options either use multi-tenant App Service (not isolated) or substitute components that don't meet the full requirement set.

Exam trap

SC-100 often tests the assumption that multi-tenant App Service with TLS and managed identity is 'good enough' for high-compliance workloads, when the exam expects recognition that single-tenant ASE v3 plus Key Vault-backed certificates is mandatory for FedRAMP High isolation.

How to eliminate wrong answers

Option A is wrong because a multi-tenant App Service plan does not provide the network isolation or single-tenant hosting required for FedRAMP High classified workloads, even though the other controls are valid. Option C is wrong because it uses App Service certificates instead of Azure Key Vault, which fails the explicit certificate management requirement and lacks the centralized key lifecycle controls needed for classified data. Option D is wrong because it uses a service principal instead of a managed identity, which requires storing and rotating credentials and does not meet the identity-based access requirement as cleanly as managed identity.

203
MCQmedium

You are designing a hybrid identity solution for an organization that uses Microsoft Entra ID and an on-premises Active Directory. The organization requires that users who are located in a remote office without a direct VPN connection to the main office can authenticate against on-premises resources using their Entra ID credentials. The solution must minimize latency and support passwordless authentication. Which feature should you implement?

A.Configure Microsoft Entra Application Proxy
B.Implement Microsoft Entra Kerberos authentication
C.Enable Microsoft Entra Conditional Access policies
D.Deploy Microsoft Entra Connect Sync with password hash synchronization
AnswerB

Implement Microsoft Entra Kerberos authentication is the correct approach because it lets Entra ID issue a Kerberos ticket-granting ticket (TGT) for a synchronized user, enabling access to on-premises Kerberos-protected resources without the user authenticating directly against local Active Directory. This works with passwordless credentials such as FIDO2 security keys and Windows Hello for Business, and it reduces latency by avoiding a separate on-premises authentication round-trip. The Entra ID instance effectively acts as a cloud-based KDC, but it still relies on on-premises domain controllers to issue service tickets.

Why this answer

Microsoft Entra Kerberos authentication enables users to authenticate to on-premises resources using their Entra ID credentials without requiring a VPN, and it supports passwordless methods like FIDO2 and Windows Hello for Business. Option A is incorrect because Entra Application Proxy is designed for publishing on-premises web applications, not for general authentication. Option C is incorrect because Conditional Access policies enforce access controls but do not provide authentication or passwordless capabilities.

Option D is incorrect because Entra Connect Sync with password hash synchronization only syncs password hashes and does not support real-time passwordless authentication without a VPN.

204
MCQeasy

Your organization uses Microsoft Sentinel for security operations. You need to ensure that all incidents are automatically assigned to the appropriate analyst team based on the type of threat. What should you configure?

A.Use a watchlist to map threat types to teams and trigger a logic app.
B.Modify the analytics rule to include a custom field for the assigned team.
C.Create a playbook that assigns ownership based on incident properties.
D.Configure an automation rule to set the incident owner based on custom conditions.
AnswerD

Automation rules are the native Sentinel feature that lets you set incident properties—including owner—based on conditions like severity, tags, or rule name, and they execute automatically when an incident is created or updated. This is a built-in action with no external dependencies, so it runs reliably, quickly, and with minimal configuration, making it the correct solution. You can specify a user or group as owner, and the rule will apply that assignment when the incident matches your custom conditions.

Why this answer

The correct option is D: configure an automation rule to set the incident owner based on custom conditions. Microsoft Sentinel automation rules are designed to run on incident creation or updates and can assign an owner (analyst or team) using conditions such as the incident's title, severity, tactics, or custom details, which directly matches the requirement to route incidents by threat type. Option A is wrong because a watchlist alone does not assign incidents and would require an unnecessary logic app; watchlists are reference data, not automation triggers.

Option B is wrong because analytics rules generate incidents and can add custom details or entity mappings, but they do not assign incident ownership to a team. Option C is wrong because playbooks are Logic Apps triggered by automation rules or analytics rules and are used for response actions, not as the primary mechanism for setting incident owner based on conditions.

Exam trap

A common mistake is to think that playbooks are needed for incident assignment, but automation rules provide a simpler and more direct way to set incident owners based on conditions.

205
MCQmedium

A multinational company is implementing a Zero Trust security model. The security team needs to ensure that all access requests to critical applications are evaluated based on user identity, device health, and real-time risk signals. Which Microsoft solution should they use to centralize policy enforcement?

A.Microsoft Defender for Cloud Apps
B.Microsoft Entra Conditional Access
C.Azure AD Identity Protection
D.Microsoft Purview Compliance Manager
AnswerB

Microsoft Entra Conditional Access is the core policy engine in Microsoft's identity stack that evaluates sign-in requests against signal combinations such as user risk, device compliance, and geographic location. At the point of authentication, it applies granular policies—like requiring MFA or blocking access—by emitting 'access controls' that the authentication stack must satisfy. This makes it the central enforcement point for zero-trust principles, ensuring every access attempt is explicitly verified before granting access.

Why this answer

Microsoft Entra Conditional Access is the correct choice because it is the policy engine in Microsoft Entra ID that centralizes access decisions by evaluating signals such as user identity, group membership, device compliance/health, location, and real-time risk before granting access to applications. This aligns directly with Zero Trust's 'verify explicitly' principle, since Conditional Access enforces grant controls (for example, require MFA or a compliant device) and session controls at the point of access. Microsoft Defender for Cloud Apps is a CASB for discovering and governing cloud app usage, not the central policy enforcement point for identity-based access.

Azure AD Identity Protection detects and reports risky users and sign-ins and feeds risk signals into Conditional Access, but it does not itself centralize access policy enforcement. Microsoft Purview Compliance Manager is a compliance assessment and improvement tool, not an access control solution.

206
MCQeasy

A small business uses Microsoft 365 Business Premium and wants to secure their Windows 10 devices with Microsoft Intune. They need to ensure that only devices compliant with the company's security policies can access corporate email. What should they configure?

A.Azure AD Application Proxy
B.Windows Defender Firewall rules
C.Microsoft Defender for Cloud Apps session policy
D.Conditional Access policy requiring compliant device
AnswerD

A Conditional Access policy requiring a compliant device blocks sign-in from devices that are not Intune-enrolled and verified against compliance policies, such as requiring disk encryption or an up-to-date OS. When the user attempts to access Exchange Online, Azure AD evaluates the device's compliance claim from Intune and either grants, blocks, or triggers remediation in real time. For Microsoft 365 Business Premium, Intune is included, so this is the appropriate mechanism to prevent non-compliant devices from reading email.

Why this answer

Conditional Access in Microsoft Entra ID can require device compliance before granting access to Exchange Online. Device compliance policies in Intune define the security requirements. Azure AD Application Proxy is for on-prem apps.

Microsoft Defender for Cloud Apps is for cloud app security. Windows Defender Firewall is for network security.

207
MCQmedium

Your company uses Microsoft Sentinel as a SIEM. You need to create an analytics rule that detects when a user account is created outside of business hours. The rule should trigger an incident for investigation. Which type of analytics rule should you use?

A.Anomaly rule
B.Fusion rule
C.Scheduled query rule
D.NRT query rule
AnswerC

Scheduled query rules in Microsoft Sentinel are the appropriate choice because they run on a defined cadence (e.g., every 5 minutes or hourly) and execute a KQL query against ingested data. You can set a schedule that matches the desired time window, and the rule will trigger an incident if the query returns results. This allows you to easily implement a condition like 'alert when events occur during a specific time range' by embedding that time filter in the query and scheduling the rule to run accordingly.

Why this answer

A scheduled query rule is the correct choice because it allows you to define a KQL query that checks for user account creation events (e.g., from the SecurityEvent or AuditLogs table) and then use the query scheduling settings to run the query at a specific interval. You can then add a condition in the rule logic to filter for events occurring outside business hours (e.g., using the `datetime_part` function to check the hour of the event). When the query returns results, Sentinel automatically generates an incident for investigation.

Exam trap

The trap here is that candidates often confuse scheduled query rules with NRT query rules, assuming that 'near-real-time' is always better for time-sensitive detections. While NRT rules run every minute, they have significant limitations, including a fixed 1-minute lookback, limited KQL support, and no custom scheduling. For a detection based on the hour of an event, a scheduled query rule is the appropriate and recommended choice because it allows full KQL and configurable scheduling to reliably detect all relevant events, not just those in the most recent minute.

How to eliminate wrong answers

Option A is wrong because anomaly rules use machine learning to detect unusual patterns over time without a predefined query, and they cannot be configured with a specific KQL query to filter for account creation outside business hours. Option B is wrong because Fusion rules correlate alerts from multiple products to detect multistage attacks, and they do not allow you to define a custom query for a single event type like user account creation. Option D is wrong because NRT (near-real-time) query rules run queries every minute with a 1-minute lookback, which is not suitable for checking events against a static time window like 'outside business hours' and does not support the same flexible scheduling and incident creation logic as scheduled query rules.

208
Multi-Selecteasy

Which TWO of the following are valid methods to secure traffic between on-premises and Azure?

Select 2 answers
A.Azure Front Door
B.ExpressRoute with MACsec
C.Azure Traffic Manager
D.Azure CDN
E.Site-to-Site VPN
AnswersB, E

ExpressRoute with MACsec is a valid layer-2 encryption method: ExpressRoute provides a private, dedicated connection that avoids the public internet, and MACsec (802.1AE) adds end-to-end data-link encryption between your edge router and Microsoft's edge. This combination ensures confidentiality and integrity for traffic that would otherwise traverse shared provider infrastructure, making it a robust way to secure hybrid connectivity.

Why this answer

ExpressRoute with MACsec provides encryption at Layer 2 using the IEEE 802.1AE standard, securing traffic between on-premises and Azure over a private connection without traversing the public internet. Site-to-Site VPN uses IPsec (IKEv1/IKEv2) to encrypt traffic over the public internet, establishing a secure tunnel between the on-premises VPN device and Azure VPN Gateway. Both are valid methods for securing traffic, with ExpressRoute+MACsec offering lower latency and higher throughput for private connectivity.

Exam trap

The trap here is that candidates often confuse Azure Front Door or Traffic Manager as security solutions because they offer TLS termination or DDoS protection, but neither provides encrypted site-to-site connectivity between on-premises and Azure; they are traffic routing and acceleration services, not VPN or private connection methods.

209
MCQmedium

You are the security architect for a company that uses Azure Virtual Machines (VMs) running Windows Server and Linux. The company has a regulatory requirement that all VM disks must be encrypted at rest, including temporary disks and disk caches. You need to recommend a solution that meets the requirement and minimizes administrative overhead. What should you recommend?

A.Enable Azure Disk Encryption (ADE) on each VM.
B.Use Azure Storage Service Encryption (SSE) for all VM disks.
C.Configure BitLocker on Windows VMs and DM-Crypt on Linux VMs.
D.Enable encryption at host for all VMs.
AnswerD

Encryption at host encrypts all data written to the VM, including temporary disks and disk caches, at the host level. It is enabled per VM or VM scale set and does not require managing encryption keys inside the guest OS, reducing administrative overhead. This meets the requirement for all disks and caches to be encrypted at rest.

Why this answer

Encryption at host is the only option that encrypts all VM data, including temporary disks and disk caches, at the host level. It requires no guest OS configuration and simplifies key management compared to Azure Disk Encryption. The other options either do not cover temporary disks and caches or add unnecessary administrative complexity.

Exam trap

The trap here is confusing Azure Disk Encryption with encryption at host, assuming both cover temporary disks and caches.

210
Multi-Selecthard

You are designing a network security strategy for a multicloud environment that includes Azure and Amazon Web Services (AWS). The company requires that all traffic between the two clouds be encrypted and inspected for threats. You need to recommend a solution that meets the following requirements: - Minimize latency. - Use Microsoft-provided security services where possible. - Ensure traffic is inspected at Layers 3-7. Which TWO options should you include in your design?

Select 2 answers
A.Azure Virtual WAN with a secured hub that includes Azure Firewall and Firewall Manager.
B.Azure Firewall with forced tunneling to an on-premises inspection appliance.
C.Azure Policy with built-in network security policies.
D.Azure Front Door Premium with Web Application Firewall (WAF) policy.
E.AWS Transit Gateway with AWS Network Firewall for inspection.
AnswersA, E

Azure Virtual WAN is a global transit networking service that interconnects VNets, branches, and remote sites through a full mesh of Microsoft-managed hubs. When deployed as a secured hub, it embeds Azure Firewall as a centralized, scalable L3-7 inspection point, and Firewall Manager enforces consistent security policies across all hubs and virtual networks. This architecture dynamically routes inter-cloud and branch traffic through the firewall, providing transit connectivity and comprehensive inspection that exactly matches the multicloud network security requirement.

Why this answer

Azure Virtual WAN with a secured hub integrates Azure Firewall and Firewall Manager to provide a centralized, Microsoft-managed inspection point for traffic between Azure and AWS. This design minimizes latency by routing inter-cloud traffic through Microsoft's global backbone rather than over the public internet, and it supports Layer 3-7 inspection via Azure Firewall's application and network rules. Similarly, on the AWS side, AWS Transit Gateway with AWS Network Firewall provides a centralized, managed inspection point for traffic between VPCs and other connected networks, including inter-cloud traffic.

It also minimizes latency by routing traffic through AWS's global infrastructure and supports Layer 3-7 inspection. Together, these two components satisfy all requirements: encrypted and inspected traffic between the two clouds, minimized latency, use of Microsoft-provided services where possible (Azure Firewall), and Layers 3-7 inspection on both sides.

Exam trap

Candidates may confuse Azure Front Door (a global load balancer and WAF for web traffic) with a general-purpose inter-cloud inspection solution, overlooking that it only handles HTTP/HTTPS and cannot inspect non-web protocols or traffic between cloud networks. Similarly, they might think only one cloud-side solution is needed, but in a multicloud environment, both sides must provide inspection for true end-to-end security.

211
MCQhard

Refer to the exhibit. You are deploying an ARM template for a Windows VM. The adminPassword parameter references a secret in Key Vault. However, the deployment fails with an access denied error. What is the most likely cause?

A.The secret value contains special characters that need to be escaped.
B.The template should use the secret's URI directly instead of a parameter reference.
C.The deployment principal lacks 'Get' and 'List' permissions on the Key Vault secret.
D.The Key Vault is in a different resource group than the deployment.
AnswerC

The ARM template engine uses the deployment principal's Azure AD token to authenticate to Key Vault and must have `Get` and `List` permissions on the referenced secret; `List` is required to resolve the latest version when no specific version is provided, and `Get` is required to actually read the secret value. Without these in the Key Vault access policy (or RBAC role), the deployment returns an `AccessDenied` error. This is precisely the condition seen in the exhibit, where the template and parameter file are syntactically correct but the deployment fails.

Why this answer

When referencing a Key Vault secret in an ARM template parameter, the user or service principal deploying the template must have 'Get' and 'List' permissions on the secret. If the deployment principal does not have those permissions, access is denied. Option A is wrong because special characters in secrets are supported, but the deployment still requires permissions.

Option B is wrong because the template uses a parameter reference to the secret, not the secret's URI directly; that is the correct approach. Option D is wrong because the Key Vault can be in a different resource group than the deployment, as long as the deployment principal has the necessary permissions.

212
Multi-Selecthard

A company is deploying a new application that uses Azure Cosmos DB. The security requirements include: data encryption at rest, data encryption in transit, and the ability to audit all data access. Which THREE of the following should you implement?

Select 3 answers
A.Use Azure SQL Database instead of Cosmos DB
B.Require TLS for all connections to Cosmos DB
C.Use Azure Active Directory authentication for Cosmos DB
D.Enable encryption at rest with customer-managed keys
E.Enable diagnostic logging for Cosmos DB
AnswersB, D, E

Requiring TLS for all connections to Cosmos DB enforces encryption in transit, using TLS 1.2 or later as the minimum protocol version. This prevents eavesdropping, man-in-the-middle attacks, and tampering while data is on the wire between client applications, SDKs, and the Cosmos DB service endpoints. TLS also helps meet compliance standards that explicitly mandate in-transit confidentiality, but it does not protect data at rest on the storage backend—that is a separate control.

Why this answer

Option B is correct because requiring TLS for all Cosmos DB connections enforces data encryption in transit, protecting data as it moves between clients and the service. Option D is correct because enabling encryption at rest with customer-managed keys ensures stored data is encrypted and gives the organization control over the key lifecycle, satisfying the encryption-at-rest requirement. Option E is correct because enabling diagnostic logging for Cosmos DB captures data-plane and control-plane operations, providing the audit trail needed to monitor and audit all data access.

Option A is incorrect because replacing Cosmos DB with Azure SQL Database does not meet the stated application requirement to use Cosmos DB and does not by itself address all three security controls. Option C is incorrect because Azure AD authentication addresses identity and access control, not encryption at rest, encryption in transit, or auditing of data access.

213
MCQmedium

A security architect needs to design a solution that provides a unified view of security alerts from multiple clouds (Azure, AWS, GCP) and on-premises systems. The solution must also support automated response using playbooks. Which Microsoft service should they use?

A.Microsoft Defender XDR
B.Microsoft Defender for Cloud
C.Microsoft Purview
D.Microsoft Sentinel
AnswerD

Microsoft Sentinel is a cloud-native SIEM and SOAR that natively ingests data from Azure and, via built-in connectors, from AWS, Google Cloud, other SaaS platforms, and on-premises sources such as syslog and CEF, allowing centralized multi-cloud log collection. Its analytical rules use Kusto Query Language to detect suspicious activity and trigger automated response playbooks built on Azure Logic Apps, providing real-time containment like device isolation or account disablement. Sentinel's architecture includes Common Event Format (CEF) and Syslog agents for on-premises, plus API connectors for AWS CloudTrail and GCP, making it the only option that fulfills the full multi-cloud SIEM/SOAR requirement with integrated UEBA and threat intelligence.

Why this answer

Microsoft Sentinel is the correct choice because it is a cloud-native SIEM (Security Information and Event Management) and SOAR (Security Orchestration, Automation, and Response) solution that ingests security alerts from multiple clouds (Azure, AWS, GCP) and on-premises systems via connectors. It supports automated response through playbooks built on Azure Logic Apps, enabling unified alert management and remediation workflows.

Exam trap

The trap here is confusing Microsoft Defender for Cloud (a CSPM tool) with Microsoft Sentinel (a SIEM/SOAR), as both appear in the Azure portal and deal with security alerts, but only Sentinel provides native multi-cloud SIEM ingestion and automated playbook orchestration for cross-cloud incident response.

How to eliminate wrong answers

Option A is wrong because Microsoft Defender XDR is an extended detection and response solution focused on correlating signals across Microsoft 365, endpoints, and identities, but it does not natively ingest alerts from AWS, GCP, or on-premises systems for a unified multi-cloud SIEM view. Option B is wrong because Microsoft Defender for Cloud is a cloud security posture management (CSPM) and workload protection platform that provides security recommendations and alerts primarily for Azure and hybrid environments, but it lacks the native multi-cloud SIEM ingestion and SOAR playbook automation of Sentinel. Option C is wrong because Microsoft Purview is a data governance, risk, and compliance solution (e.g., data classification, eDiscovery, insider risk management) and does not provide SIEM alert correlation or automated response playbooks for security incidents.

214
MCQeasy

Your company is developing a Microsoft Teams app that accesses user profiles. You need to ensure the app only accesses minimal required data. What should you implement?

A.Admin consent for all scopes
B.Application permissions for Microsoft Graph
C.Delegated permissions with User.Read
D.Delegated permissions with User.Read.All
AnswerC

Delegated permissions with User.Read are the correct choice because the app calls Microsoft Graph with a token that includes the signed-in user's identity and consent scope. This scope is the minimal privilege needed to read the current user's profile—name, email, photo, and other basic attributes—while preventing access to other users' data. The user or an administrator can consent to this scope during app usage, and it aligns with the Teams app's requirement to access only the caller's own profile.

Why this answer

The correct option is C: Delegated permissions with User.Read. Delegated permissions let the app act on behalf of the signed-in user, and User.Read is the least-privileged Microsoft Graph scope that allows reading the signed-in user's own profile, satisfying the requirement for minimal data access. Option A is unnecessary because admin consent for all scopes grants far broader access than needed.

Option B is wrong because application permissions run without a signed-in user and typically require broader tenant-wide access. Option D is excessive since User.Read.All allows reading all users' full profiles, not just the current user's minimal data.

215
MCQhard

Your organization uses Microsoft Intune to manage devices. You need to ensure that corporate data on personally owned devices is removed when a user leaves the company, but personal data remains intact. What should you use?

A.Selective wipe (retire)
B.Conditional Access policy
C.Full wipe
D.Device compliance policy
AnswerA

Intune's retire action performs a selective wipe: it deletes only the organization's managed data, such as corporate email, VPN and Wi-Fi profiles, app configs, and protected app containers, then unenrolls the device. It deliberately preserves personal photos, personal apps, and other user data, making it the correct choice for BYOD when you must remove company information without damaging the user's private content.

Why this answer

Selective wipe (retire) is the correct choice because it removes only corporate data from a personally owned device enrolled in Microsoft Intune, while preserving the user's personal data. This is achieved by targeting managed app data and corporate profiles, leaving personal apps, photos, and settings intact. It aligns with the requirement to protect corporate information upon employee departure without affecting the user's personal property.

Exam trap

The trap here is that candidates often confuse 'selective wipe' with 'full wipe' or assume that a Conditional Access policy can enforce data removal, when in fact only selective wipe provides granular corporate data removal while preserving personal data.

How to eliminate wrong answers

Option B is wrong because Conditional Access policies control access to resources based on conditions like device compliance or location, but they do not perform data removal or wipe operations. Option C is wrong because a full wipe resets the device to factory defaults, erasing both corporate and personal data, which violates the requirement to keep personal data intact. Option D is wrong because device compliance policies enforce security settings (e.g., requiring encryption or a minimum OS version) but do not remove data; they only mark devices as compliant or non-compliant.

216
MCQmedium

Your organization uses Microsoft Defender XDR for incident response. You need to design a process to automatically isolate a compromised device when a high-severity incident is triggered. Which automation approach should you use?

A.Create a compliance policy in Microsoft Intune that marks the device as noncompliant
B.Configure an Azure Automation runbook to poll Defender alerts and isolate devices
C.Set up a Power Automate flow triggered by email notifications from Defender
D.Use automation rules in Microsoft Sentinel with a playbook that runs a Defender for Endpoint isolation action
AnswerD

Microsoft Sentinel automation rules are event-driven: when an incident matches criteria (e.g., a high-severity malware incident on a specific device), the rule triggers a playbook built on Logic Apps. That playbook uses the Microsoft Defender for Endpoint connector to run the 'Isolate machine' action, which calls the Defender for Endpoint API to sever the device's network connectivity while maintaining communication with the management plane. This is a native, first-party integration that responds immediately and can be extended with manual approval steps or additional enrichment actions.

Why this answer

Microsoft Sentinel's automation rules can directly trigger a playbook (Azure Logic App) that executes the Microsoft Defender for Endpoint 'Isolate device' action. This provides near-real-time, event-driven isolation without polling, aligning with the requirement to automatically isolate a compromised device when a high-severity incident is triggered in Defender XDR.

Exam trap

The trap here is that candidates confuse 'marking a device as noncompliant' (Option A) with actual network isolation, or assume that any automation (Options B and C) is sufficient, overlooking the requirement for event-driven, low-latency integration with Defender for Endpoint's native isolation capability.

How to eliminate wrong answers

Option A is wrong because a compliance policy in Microsoft Intune marks a device as noncompliant but does not perform device isolation; it can trigger conditional access or wipe actions, not the network-level isolation needed for incident response. Option B is wrong because polling Defender alerts via an Azure Automation runbook introduces latency and inefficiency, and it bypasses the native event-driven automation capabilities of Microsoft Sentinel and Defender XDR. Option C is wrong because email notifications are unreliable and introduce delay; Power Automate flows triggered by email cannot guarantee timely, automated isolation and lack direct integration with Defender for Endpoint's isolation API.

217
MCQhard

You are designing a security solution for Azure API Management. The requirements include: protecting APIs from abuse, throttling requests, and validating JSON payloads. Which combination of features should you use?

A.Managed Identities and Azure AD authentication
B.Azure Web Application Firewall (WAF) on Application Gateway
C.Rate limiting policies, validate-json policy, and OAuth 2.0
D.Azure Firewall and Network Security Groups
AnswerC

The correct combination applies API Management inbound policies in sequence: rate-limit or quota policies throttle requests per subscription, key, or IP address; validate-json verifies the JSON request body against a defined schema and rejects malformed payloads; and OAuth 2.0 with validate-jwt ensures access tokens are signed, unexpired, and carry the required scopes. Together these policies directly satisfy throttling, validation, and secure access control at the API gateway level.

Why this answer

Option C is correct because API Management natively provides rate limiting and quota policies to throttle requests and protect against abuse, the validate-json policy to validate JSON payloads against a schema, and OAuth 2.0 support to secure API access via authorization servers. These features directly satisfy the stated requirements within the APIM gateway itself. Option A addresses identity and authentication but does not provide throttling or JSON schema validation.

Option B offloads protection to Application Gateway WAF, which handles web attack patterns but not APIM-level rate limiting or JSON payload schema validation. Option D provides network-layer filtering with Azure Firewall and NSGs, which cannot inspect JSON payloads or apply API-level throttling.

218
MCQeasy

Your organization is implementing a zero-trust security model and needs to ensure that all access to cloud resources is verified in real-time. You plan to use Microsoft Entra ID Conditional Access. Which policy component enforces real-time verification of user identity and device compliance before granting access?

A.Enable Microsoft Secure Score
B.Use Azure AD Application Proxy
C.Conditional Access policy with conditions and grant controls
D.Assign users and groups to the policy
AnswerC

Conditional Access policies are the core enforcement mechanism for zero trust in Azure AD. They combine conditions such as user or group membership, location, device state, and sign-in risk with grant controls like requiring MFA, a compliant device, or a hybrid Azure AD joined device. These policies enforce real-time verification for every access attempt, ensuring that access is granted only when all configured conditions and controls are satisfied, aligning with the zero trust principle of 'verify explicitly'.

Why this answer

Conditional Access policies with conditions and grant controls enforce real-time verification by evaluating signals such as user identity, device compliance (via Microsoft Intune), and location before allowing access to cloud resources. The grant controls block or require multi-factor authentication (MFA) or device compliance, ensuring zero-trust principles of explicit verification and least privilege.

Exam trap

The trap here is that candidates confuse policy assignment (users/groups) with the enforcement mechanism (conditions and grant controls), thinking that merely assigning a policy to a user group enforces real-time verification, when in fact the conditions and grant controls are the components that perform the actual evaluation and access decision.

How to eliminate wrong answers

Option A is wrong because Microsoft Secure Score is a security posture measurement tool, not a policy component that enforces real-time access verification. Option B is wrong because Azure AD Application Proxy provides secure remote access to on-premises web applications, not real-time identity and device compliance checks for cloud resources. Option D is wrong because assigning users and groups to a policy defines scope but does not enforce real-time verification; the conditions and grant controls are the components that perform the actual evaluation and enforcement.

219
MCQhard

A company is deploying a new application that will store sensitive customer data in Azure SQL Database. The security team requires that all data at rest be encrypted using a customer-managed key stored in Azure Key Vault. Additionally, they need to ensure that the database can be restored to a point in time and that the encryption key is rotated every 90 days. Which combination of features should you configure?

A.Enable TDE with service-managed keys and use Azure Policy to enforce rotation.
B.Use Always Encrypted with column master key in Azure Key Vault and manual rotation.
C.Use Azure Storage Service Encryption with customer-managed keys and enable soft delete.
D.Enable TDE with customer-managed keys in Azure Key Vault and configure automatic key rotation.
AnswerD

Transparent Data Encryption with customer-managed keys in Azure Key Vault encrypts the entire SQL database by using a symmetric Database Encryption Key (DEK) that is itself protected by an asymmetric TDE protector stored in the vault. You can enable automatic rotation on the TDE protector, which configures Azure SQL to automatically use the latest version of the key from Azure Key Vault without any manual intervention. This gives the organization full control over key management and satisfies the requirement for automated, periodic rotation.

Why this answer

Option D is correct because Transparent Data Encryption (TDE) with customer-managed keys (CMK) in Azure Key Vault encrypts Azure SQL Database data at rest, and TDE supports point-in-time restore (PITR) via automated backups while allowing automatic key rotation through the Key Vault key rotation policy. Configuring TDE with a CMK satisfies the requirement that the encryption key be customer-managed and rotated every 90 days. Option A is wrong because service-managed keys do not meet the customer-managed key requirement, and Azure Policy cannot itself rotate TDE protector keys.

Option B is wrong because Always Encrypted protects data in use and in transit at the client, not data at rest as required, and manual rotation does not meet the 90-day automated rotation need. Option C is wrong because Azure Storage Service Encryption applies to Azure Storage, not Azure SQL Database, and soft delete is a Key Vault data-protection feature, not a database encryption solution.

220
MCQeasy

A company uses Microsoft Defender for Cloud Apps to discover and control Shadow IT. They want to block the use of a newly discovered unsanctioned app. What should they do?

A.Create a Conditional Access policy to block the app
B.Use Microsoft Purview Data Loss Prevention to block the app
C.Mark the app as unsanctioned in Defender for Cloud Apps
D.Block the app's domain in Microsoft Intune
AnswerC

Defender for Cloud Apps presents discovered apps in the Shadow IT dashboard, where an admin can mark an app as unsanctioned to actively block it. Unsanctioning is the native CASB control point that works with the Conditional Access App Control (reverse proxy) or app connectors to terminate sessions and prevent access to the app for all users. This is the exact feature designed to govern newly discovered unsanctioned cloud applications, and it works even for apps that are not federated with Microsoft Entra ID.

Why this answer

Marking an app as unsanctioned in Microsoft Defender for Cloud Apps is the direct mechanism to block access to a discovered Shadow IT app. When an app is marked unsanctioned, Defender for Cloud Apps automatically enforces a block by integrating with Conditional Access to prevent users from accessing the app, and it can also generate alerts and session controls. This action is specifically designed for the discovered app governance workflow within Defender for Cloud Apps.

Exam trap

The trap here is that candidates often assume creating a Conditional Access policy directly is the correct action, but the SC-100 exam tests the understanding that marking the app as unsanctioned in Defender for Cloud Apps is the prerequisite step that triggers the automatic Conditional Access policy enforcement.

How to eliminate wrong answers

Option A is wrong because creating a Conditional Access policy to block the app is not the first step; the app must first be marked as unsanctioned in Defender for Cloud Apps, which then automatically creates the necessary Conditional Access policy via the app governance integration. Option B is wrong because Microsoft Purview Data Loss Prevention (DLP) is designed to prevent data exfiltration and sensitive data sharing, not to block access to an entire unsanctioned app. Option D is wrong because blocking the app's domain in Microsoft Intune would only affect managed devices and does not address the broader Shadow IT discovery and control workflow that Defender for Cloud Apps provides.

221
MCQmedium

Trey Research, a biotech firm, is developing a machine learning model on Azure Machine Learning that uses sensitive genomic data. The data is stored in Azure Blob Storage. The company requires that all data be encrypted at rest using customer-managed keys stored in Azure Key Vault, and that access to the storage account be restricted to the Azure Machine Learning workspace and specific data scientists via Azure AD authentication. Additionally, the storage account must be accessible only from the company's virtual network. Which of the following configurations should you implement?

A.Enable encryption at rest with a customer-managed key, configure a firewall to allow the Machine Learning workspace's IP range, and grant data scientists access via storage account access keys.
B.Enable encryption at rest with a service-managed key, configure a private endpoint, and grant data scientists access using Azure RBAC with the Storage Blob Data Reader role.
C.Enable encryption at rest with a customer-managed key, configure a private endpoint for the storage account, and grant the Machine Learning workspace and data scientists access using Azure RBAC with the Storage Blob Data Contributor role.
D.Enable encryption at rest with a customer-managed key, configure a service endpoint for the storage account, and grant the Machine Learning workspace access using a SAS token.
AnswerC

Customer-managed keys in Key Vault satisfy the encryption-at-rest requirement, the private endpoint restricts the storage account to the virtual network, and Azure RBAC with Storage Blob Data Contributor grants least-privilege access via Microsoft Entra ID. Together these meet all three stated constraints.

Why this answer

It provides encryption at rest with a customer-managed key (CMK) stored in Azure Key Vault, a private endpoint to restrict access to the company's virtual network, and Azure RBAC with the Storage Blob Data Contributor role for both the Machine Learning workspace and data scientists, ensuring Azure AD authentication. Option A is wrong because firewall rules using IP ranges are less secure than private endpoints, and granting access via storage account access keys bypasses Azure AD authentication. Option B is wrong because it uses a service-managed key, which does not meet the customer-managed key requirement.

Option D is wrong because a service endpoint is less secure than a private endpoint, and using a SAS token does not provide Azure AD-based access control.

222
MCQhard

Your organization uses Microsoft Sentinel as a SIEM. The security team wants to use Microsoft Copilot for Security to assist in incident investigation. You need to ensure that Copilot can access Sentinel data while meeting compliance requirements. Which integration should you configure?

A.Deploy a playbook to query Sentinel data
B.Enable Microsoft Copilot for Security plugin for Sentinel
C.Enable Sentinel's Threat Intelligence connectors
D.Use Microsoft Defender for Cloud
AnswerB

Enabling the Microsoft Copilot for Security plugin for Sentinel is the direct, secure integration that lets Copilot query and interact with Sentinel data using natural language. When enabled, a security analyst can ask Copilot questions like 'summarize the most recent high-severity alerts' or 'show all open incidents involving user X,' and Copilot translates that into KQL queries against Sentinel's underlying Log Analytics workspace. This plugin explicitly bridges Copilot to Sentinel, providing incident summaries, guided investigations, and context-aware responses, which is exactly what the organization needs to leverage Copilot as a SIEM interface.

Why this answer

The Microsoft Copilot for Security plugin for Sentinel is the correct integration because it enables Copilot to directly query and analyze Sentinel data through a native, compliant connection. This plugin uses Sentinel's API and role-based access control (RBAC) to ensure that Copilot only accesses data the user is authorized to see, meeting compliance requirements without additional data movement.

Exam trap

The trap here is that candidates often confuse enabling Threat Intelligence connectors (Option C) with granting data access, but those connectors only import external threat data and do not provide Copilot with read access to Sentinel's internal logs or incidents.

How to eliminate wrong answers

Option A is wrong because deploying a playbook to query Sentinel data introduces unnecessary complexity and latency; playbooks are designed for automated response workflows, not for providing real-time, compliant data access to Copilot. Option C is wrong because enabling Sentinel's Threat Intelligence connectors only ingests external threat intelligence feeds into Sentinel, it does not grant Copilot access to Sentinel's existing security data or logs. Option D is wrong because Microsoft Defender for Cloud is a separate cloud security posture management (CSPM) tool that does not natively integrate with Copilot for Security to access Sentinel data; it focuses on workload protection, not SIEM data access.

223
MCQeasy

A SOC analyst needs to investigate a potential privilege escalation using Azure AD roles. Which Microsoft 365 Defender data source would be most useful to review?

A.Microsoft 365 Defender identity logs
B.Azure Active Directory audit logs
C.Microsoft Defender for Cloud Apps logs
D.Microsoft 365 audit logs
AnswerB

Azure AD audit logs (now part of Microsoft Entra ID) provide a comprehensive, immutable record of directory events, including role assignments, role activations, and permission changes. These logs precisely capture the actor, target, timestamp, and metadata for every privilege-modification action, making them the definitive source for tracing how a user acquired elevated rights or escalated privileges.

Why this answer

Azure AD audit logs (now part of the Azure Monitor / Microsoft Entra audit logs) are the authoritative source for tracking changes to Azure AD roles, including role assignments, activations of Privileged Identity Management (PIM) roles, and modifications to directory roles. Since the question specifically involves privilege escalation using Azure AD roles, these logs contain the necessary details such as who assigned a role, when, and from which IP address, making them the most directly relevant data source.

Exam trap

Microsoft often tests the distinction between Azure AD audit logs (which track directory configuration changes like role assignments) and Microsoft 365 audit logs (which track user activity across workloads), leading candidates to mistakenly choose the broader Microsoft 365 audit logs when the question specifically targets Azure AD role changes.

How to eliminate wrong answers

Option A is wrong because Microsoft 365 Defender identity logs (derived from Microsoft Defender for Identity) focus on on-premises Active Directory security events and lateral movement detection, not Azure AD role assignments or changes. Option C is wrong because Microsoft Defender for Cloud Apps logs primarily track user activities within cloud applications (e.g., file downloads, app permissions) and do not natively capture Azure AD role assignment events. Option D is wrong because Microsoft 365 audit logs cover a broad range of user and admin activities across Exchange, SharePoint, and Teams, but they do not include the granular Azure AD role assignment and activation events that are specifically recorded in Azure AD audit logs.

224
MCQeasy

Your organization uses Microsoft Intune for mobile device management. You need to ensure that only compliant devices can access corporate email. What should you configure?

A.Configure an app protection policy in Intune.
B.Create a device configuration policy in Intune.
C.Create a Conditional Access policy in Microsoft Entra ID that requires compliant device.
D.Create a device compliance policy in Intune.
AnswerC

Conditional Access enforces the compliance signal from Intune at authentication time, so only devices meeting your compliance policy obtain a token for Exchange Online. This directly satisfies the requirement that solely compliant devices reach corporate email, blocking unmanaged or non-compliant endpoints.

Why this answer

Conditional Access in Microsoft Entra ID can enforce device compliance for access. Option A is incorrect because app protection policies protect data within apps but do not control device-level access. Option B is incorrect because device configuration policies define settings but do not enforce compliance-based access.

Option D is incorrect because device compliance policies define compliance requirements, but Conditional Access is needed to enforce them.

225
MCQhard

Refer to the exhibit. A security architect is reviewing an ARM template that deploys an Azure Storage container. They want to ensure the container is not publicly accessible. What is the security implication of this template?

A.The container allows public access
B.The template creates a container with versioning enabled
C.The template enables encryption at rest
D.The template does not configure network rules, so the container may be accessible from the internet, but only to authenticated users
AnswerD

The template does not define any network access restrictions, such as virtual network rules, IP rules, or a default action of Deny. As a result, the storage account is reachable from the internet, but because the container's publicAccess is set to None, only authenticated requests (using account keys, SAS, or Microsoft Entra) are accepted. This is a distinct security concern: the storage endpoint is publicly exposed, even though data access requires authentication.

Why this answer

Option D is correct because the ARM template does not define any network rules (such as a virtual network rule or IP firewall rule) for the storage account, so the storage endpoint remains reachable from the internet; however, since public blob access is not enabled, anonymous access is denied and only authenticated requests with valid credentials or SAS tokens can succeed. This means the container is not publicly accessible in the anonymous sense, but the lack of network restrictions still exposes the endpoint to authenticated access from any network. Option A is wrong because nothing in the template enables anonymous public access to the container.

Option B is wrong because versioning is a data-protection feature, not a public-access control, and it is not the security implication being asked about. Option C is wrong because encryption at rest is enabled by default for Azure Storage and is unrelated to whether the container is publicly reachable.

Page 2

Page 3 of 9

Page 4

All pages