SC-100 domain - 27% of the exam

Design Security Operations, Identity, and Compliance Capabilities

Design Security Operations, Identity, and Compliance Capabilities is 27% of the SC-100 exam. These are the objectives it covers, each with practice questions, with every answer explained.

The domain in numbers

87
Practice questions
4
Objectives
22
Medium
65
Hard

Where people go wrong

  • Mixing up Privileged Identity Management and entitlement management

    Privileged Identity Management and entitlement management each own a different job, and the wrong options swap them. Privileged Identity Management makes directory and Azure roles eligible, so they are activated just in time with approval and a multifactor challenge, but it has no self-service request flow for partners or consultants. Entitlement management publishes access packages with sponsor approval and automatic expiry, yet it grants assignments rather than per-activation elevation, so it cannot require approval or step-up when a privileged role is assumed.

    See it in a sample question
  • Treating sign-in time controls as session time enforcement

    Reducing token lifetime, adding a location condition or scoring risk at sign-in all look like ways to react to a mid-session change. Each acts when a token is issued or refreshed, so an access token already granted stays valid until it expires. Continuous access evaluation gives Exchange Online and SharePoint Online a channel to Microsoft Entra ID, so a revocation, a risky-user event or a Conditional Access location change ends or challenges the live session within minutes.

    See it in a sample question
  • Confusing Defender for Cloud compliance with Purview Compliance Manager

    A scored, control-by-control view of live Azure resources against a named standard is the job of the Microsoft Defender for Cloud regulatory compliance dashboard, which also covers Amazon Web Services and Google Cloud once connected. Sentinel, Azure Policy alone and Purview Compliance Manager are offered instead, but a SIEM raises alerts, Policy lacks the mapped standard view, and Compliance Manager relies on attested evidence. The reverse applies to a procedural privacy standard, where Compliance Manager custom assessments hold owners and evidence.

    See it in a sample question
  • Confusing Defender XDR with Sentinel

    Defender XDR and Sentinel are treated as interchangeable. Defender XDR correlates Microsoft email, identity and endpoint alerts into a single incident, so linked low-severity alerts surface as one attack chain. It does not ingest arbitrary firewall, third-party or multicloud logs or run broad orchestration playbooks, which is Sentinel as SIEM and SOAR. Wrong options rebuild XDR correlation with scheduled rules, retire Sentinel, or name Defender for Cloud or Purview Audit as the central plane.

    See it in a sample question
  • Offering data loss prevention for discovery, retention and audit

    Data loss prevention appears whenever a requirement mentions sensitive data, but it inspects content as a sharing action happens. It builds no inventory of where regulated identifiers are stored, runs no subject rights request, cannot make records unalterable for a retention period, and keeps no searchable record of who accessed mailboxes. Those jobs go to a Microsoft Purview Data Map scan with sensitive information types, Priva Subject Rights Requests, a retention policy with a preservation lock, and Purview Audit with longer retention.

    See it in a sample question

Objectives in this domain

What to study

The official documents this domain's practice questions cite most.

Sample questions from this domain

Free sampleDesign Security Operations, Identity, and Compliance Capabilitieshard

A professional services firm grants partner staff guest access to internal Microsoft Entra ID applications and finds that guest accounts accumulate long after projects end. The design must let business owners grant time-bound access through a self-service request and have that access recertified or removed automatically when it is no longer justified. Which design best satisfies this external-identity governance requirement?

  • APlace every guest into Microsoft Entra Privileged Identity Management so that they must activate their access just in time and the activation expires after a fixed window each day.
  • BUse Microsoft Entra entitlement management access packages with connected organisations and assignment expiry, combined with scheduled access reviews of the guests inside each package. Correct
  • CApply a Conditional Access policy that requires guests to perform multi-factor authentication and to sign in only from a compliant device before reaching internal applications.
  • DTighten the external collaboration settings so that invitations can be issued only by administrators and only for partner domains on an explicit allow list.
Entitlement management with access packages, assignment expiry, and access reviews provides the full self-service and recertification lifecycle for B2B guests. Entitlement management treats external collaboration as a governed lifecycle: access packages bundle the resources a partner needs, connected organisations and approval workflows handle self-service requests, assignment expiry forces re-request, and access reviews recertify or strip access that is no longer justified. No single sign-in control or just-in-time role tool delivers that end-to-end governance for guests.

Why A is wrong: Privileged Identity Management gives just-in-time elevation and looks like lifecycle control, but it is built for privileged role and group activation rather than self-service partner onboarding and recurring recertification, so it does not fit broad guest access governance.

Why B is correct: Entitlement management lets business owners publish access packages that partners request for themselves, sets time-bound assignments that expire, and pairs with access reviews so unjustified guest access is recertified or revoked, which is exactly the lifecycle the requirement describes.

Why C is wrong: Requiring multi-factor authentication and device compliance strengthens how guests connect and is tempting as a control, but it only governs the act of signing in and never addresses who still holds access or when it should be removed, so the accumulation problem remains.

Why D is wrong: Restricting who may invite guests and to which domains controls the front door and seems like governance, but it does nothing to expire existing assignments or recertify standing guest access, so stale accounts still build up over time.

Free sampleDesign Security Operations, Identity, and Compliance Capabilitieshard

A bank wants its session controls to react when a user's access is revoked or their token is flagged as risky mid-session, rather than waiting up to an hour for the existing access token to expire. The design must apply to Exchange Online and SharePoint Online access from Microsoft Entra ID. Which capability should the architect specify to meet this near-real-time enforcement requirement?

  • AEnable continuous access evaluation so that supported services receive revocation and critical-event signals and reject the existing token within minutes of the change. Correct
  • BTighten the Conditional Access sign-in frequency to a short interval so that users are forced to re-authenticate against the latest policy at frequent points during the day.
  • CConfigure Microsoft Entra ID Protection risk policies so that a user flagged as high risk is blocked the next time they attempt to authenticate to a protected application.
  • DShorten the configurable access token lifetime through a token lifetime policy so that issued tokens stop working far sooner than the default window allows.
Continuous access evaluation enforces revocation and critical events in near real time, which fixed token lifetimes and sign-in frequency cannot. Continuous access evaluation lets Microsoft Entra ID push critical events such as account disablement, password change, and elevated user risk directly to supporting resource providers, which then reject an already issued access token within minutes instead of honouring it until expiry. This closes the window that any fixed token lifetime or re-authentication interval leaves open.

Why A is correct: Continuous access evaluation establishes a near-real-time channel between Microsoft Entra ID and supported resources such as Exchange Online and SharePoint Online, so revocation or a risky-user event invalidates the live token almost immediately rather than at expiry.

Why B is wrong: Reducing sign-in frequency does reapply policy more often and feels responsive, but it still only acts at the next scheduled prompt rather than the moment of revocation, so it cannot deliver the near-real-time enforcement the requirement demands.

Why C is wrong: Risk policies score the identity and gate the next authentication, which is tempting because risk is involved, but they evaluate at sign-in and do not terminate an access token that has already been issued, so the active session continues.

Why D is wrong: A shorter token lifetime narrows the exposure window and looks like a direct fix, but it still leaves a fixed gap between revocation and expiry and Microsoft now steers customers to continuous evaluation instead, so it does not meet the requirement.

Free sampleDesign Security Operations, Identity, and Compliance Capabilitiesmedium

An insurer operates workloads in Azure, AWS, and Google Cloud and must report a single regulatory compliance posture against the Microsoft cloud security benchmark across all three clouds to its regulator. Which design delivers this multicloud assurance most directly?

  • AStream the security findings from each cloud into Microsoft Sentinel and build a workbook that visualises Microsoft cloud security benchmark control coverage across the three providers.
  • BDeploy Azure Arc to the AWS and Google Cloud virtual machines and apply Azure Policy guest configuration so the benchmark controls are evaluated on every server.
  • CApply Microsoft Purview Compliance Manager assessments for each cloud provider and combine the resulting scores into one report for the regulator.
  • DConnect the AWS and Google Cloud accounts to Microsoft Defender for Cloud and assign the Microsoft cloud security benchmark standard so all three clouds report in one compliance dashboard. Correct
Achieve unified multicloud benchmark compliance by onboarding AWS and Google Cloud to Microsoft Defender for Cloud, not by aggregating signals in a SIEM. Microsoft Defender for Cloud provides native AWS and Google Cloud connectors that assess each provider's resources against standards including the Microsoft cloud security benchmark, so a single regulatory compliance dashboard spans all three clouds, which a SIEM workbook or manual assessments cannot continuously deliver.

Why A is wrong: Microsoft Sentinel can ingest multicloud signals and a workbook can visualise them, which is tempting, but a SIEM does not natively assess each cloud's configuration against the benchmark or generate the maintained scored compliance view required.

Why B is wrong: Azure Arc with guest configuration extends policy to servers and seems to unify governance, but it only assesses operating-system settings on connected machines, not the cloud platform services, so it cannot produce a full benchmark posture.

Why C is wrong: Microsoft Purview Compliance Manager tracks control implementation through assessments and is appealing for reporting, but it relies on manual evidence rather than continuously evaluating live multicloud resource configuration against the benchmark.

Why D is correct: Microsoft Defender for Cloud can onboard AWS and Google Cloud through native connectors and assess them against the Microsoft cloud security benchmark alongside Azure, producing the unified multicloud regulatory compliance posture the requirement demands.

Free sampleDesign Security Operations, Identity, and Compliance Capabilitieshard

A security operations design must detect hands-on-keyboard attacks that move from a compromised mailbox to identity theft and then to lateral movement across endpoints, where each individual product alert looks low severity but the chained sequence is a serious breach. The architect needs the design to recognise the linked behaviour as one incident rather than scattered single-product alerts. Which capability most directly delivers this outcome?

  • AMicrosoft Defender for Endpoint behavioural detections, which raise high-fidelity endpoint alerts whenever malicious process behaviour is observed on a device.
  • BMicrosoft Entra ID Protection risk policies, which combine sign-in and user risk signals to block or challenge suspicious authentications automatically.
  • CMicrosoft Defender XDR cross-workload incident correlation, which links related email, identity, and endpoint alerts into a single incident that reflects the full attack chain. Correct
  • DMicrosoft Sentinel scheduled analytics rules, which run individual queries on a timer to detect each suspicious activity as a separate alert.
Defender XDR cross-workload correlation unites low-severity email, identity, and endpoint alerts into one incident that exposes a full attack chain. Modern intrusions cross product boundaries, so individually weak alerts only become meaningful when chained. Defender XDR is built to correlate email, identity, and endpoint signals into a single incident reflecting the kill chain, which single-workload detections and timer-based rules cannot natively assemble.

Why A is wrong: Defender for Endpoint is tempting because it produces strong endpoint alerts, but it sees only the device layer and cannot stitch the mailbox compromise and identity theft into the same incident, so the cross-domain chain stays fragmented.

Why B is wrong: Entra ID Protection is appealing because identity theft is part of the chain, but it focuses on identity risk and authentication response rather than correlating email and endpoint activity into one breach narrative, so it covers only a segment.

Why C is correct: Defender XDR correlates signals across the email, identity, and endpoint workloads and groups the linked low-severity alerts into one incident that reveals the full attack chain, which is exactly the unified view of chained behaviour the design requires.

Why D is wrong: Scheduled analytics rules are plausible because Sentinel can correlate, but a set of per-activity scheduled rules tends to emit separate alerts unless heavily engineered, whereas the native cross-workload incident logic of Defender XDR delivers the chained correlation out of the box.

Free sampleDesign Security Operations, Identity, and Compliance Capabilitiesmedium

A privacy regulation gives individuals the right to obtain a copy of all personal data an organisation holds about them, and the legal team needs a design that locates that data across Microsoft 365 and fulfils these subject rights requests through a managed workflow. Which Microsoft capability should the architect select?

  • AMicrosoft Purview Data Loss Prevention policies that detect personal data in transit and block it from leaving the tenant when a request is received.
  • BMicrosoft Priva Subject Rights Requests that discover the individual's personal data across Microsoft 365 and manage the request through to fulfilment. Correct
  • CMicrosoft Purview eDiscovery cases that search mailboxes and sites for the individual's identifiers and export the matching items for the legal team to deliver.
  • DMicrosoft Defender for Cloud Apps governance policies that quarantine files containing personal data until the subject's request has been reviewed and approved.
Map a data subject access right to Microsoft Priva Subject Rights Requests rather than to discovery, DLP, or SaaS governance tooling. Privacy rights such as the right of access require finding all of a person's personal data and managing the response under deadlines, and Microsoft Priva Subject Rights Requests automates discovery, review, and fulfilment for that purpose, where eDiscovery and DLP only search or block content without the privacy workflow.

Why A is wrong: Microsoft Purview Data Loss Prevention stops unauthorised sharing of sensitive data and feels privacy-adjacent, but it neither discovers all of a subject's data nor runs a rights-request fulfilment workflow, so it misses the stated need.

Why B is correct: Microsoft Priva Subject Rights Requests is purpose-built to locate an individual's personal data across the tenant and drive the access request through a managed review and fulfilment workflow, which is exactly the privacy obligation described.

Why C is wrong: Microsoft Purview eDiscovery can search and export content and is tempting for locating a person's data, but it is built for legal hold and investigation, lacking the privacy-specific subject-rights-request automation the regulation expects.

Why D is wrong: Microsoft Defender for Cloud Apps governs SaaS usage and risky file activity and seems to touch personal data, but it does not discover a subject's full data footprint or produce a fulfilment package, so it does not satisfy the right of access.

Other domains in this exam

See also the SC-100 cert hub, the study guide, and the cheat sheet.

Examworthy is not affiliated with or endorsed by Microsoft. Original, blueprint-aligned practice material only.