SC-100 domain - 23% of the exam

Design Solutions that Align with Security Best Practices and Priorities

Design Solutions that Align with Security Best Practices and Priorities is 23% of the SC-100 exam. These are the objectives it covers, each with practice questions, with every answer explained.

The domain in numbers

72
Practice questions
3
Objectives
20
Medium
52
Hard

Where people go wrong

  • Counting replication as protection against ransomware

    The wrong answers reach for geo-replication, Site Recovery, a synchronised standby or extra regional copies and treat the duplicate as resilience. Replication carries encrypted or tampered data to every replica, so failover only moves the compromised state elsewhere, and a privileged attacker can delete replicated copies as easily as the original. The correct designs keep a clean restore point out of the attacker's reach: immutable, time-locked storage, offline backups in an isolated recovery environment, or retention that reaches back beyond the attacker's dwell time.

    See it in a sample question
  • Assigning Microsoft frameworks to the wrong job

    Five Microsoft resources get swapped for one another. The Microsoft Cybersecurity Reference Architectures are diagrams showing where each capability and control belongs. The Microsoft cloud security benchmark is the prescriptive, standards-mapped control set that Defender for Cloud scores. The Well-Architected Framework assesses the design of individual workloads, the Cloud Adoption Framework guides governance and migration across the cloud journey, and the Rapid Modernization Plan sequences early high-impact risk reduction. Wrong options hand one resource the role of another.

    See it in a sample question
  • Offering detection where prevention or containment is required

    Endpoint protection, centralised analytics and alerting on exploitation attempts appear as wrong options in questions that ask to stop an access path or limit spread. These controls act once an attempt or an intrusion has begun. Privileged access isolation with just-in-time elevation closes the escalation route, enforced patch deployment closes the unpatched-server entry point, and deny-by-default segmentation limits how far a foothold reaches. A requirement that names prevention or blast radius is answered by a control that removes the path rather than one that reports on it.

    See it in a sample question
  • Choosing an Azure Policy effect that reports instead of blocking or fixing

    Azure Policy effects get matched to the wrong outcome. An audit effect only flags resources after they exist, append changes metadata, deployIfNotExists adds settings after creation, and deny blocks create or update requests but does nothing to resources already deployed. Stopping public IP addresses at creation needs deny. Bringing existing virtual machines into compliance needs a remediation task running a deployIfNotExists policy. The wrong options are real effects aimed at a different outcome.

    See it in a sample question
  • Treating sign-in controls as isolation for privileged administration

    Multifactor authentication, device compliance, just-in-time activation and risk-based step-up are offered as the fix for administrators who work from everyday laptops that also handle email and browsing. Each strengthens or shortens access, yet the session still starts on a device exposed to phishing and token theft. The enterprise access model places control-plane administration on hardened privileged access workstations isolated from email and web browsing, with just-in-time elevation added on top.

    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 Solutions that Align with Security Best Practices and Prioritieshard

A financial services organisation wants its backup design to survive a ransomware operator who has already gained Global Administrator rights in Microsoft Entra ID and intends to delete or encrypt all backups before detonating. Which backup design property most directly satisfies this resiliency requirement?

  • ABackups are written to immutable, time-locked storage that no administrator role can delete or alter until the retention period expires. Correct
  • BBackups are replicated to a second Azure region so that a regional outage cannot make the restore points unavailable.
  • CBackups are encrypted at rest with customer-managed keys held in an Azure Key Vault that the backup service can read automatically.
  • DBackups run more frequently so that the recovery point objective is reduced to under fifteen minutes for every protected workload.
Ransomware-resilient backups must be immutable and retention-locked so that even a fully compromised privileged identity cannot destroy the restore points. Ransomware actors specifically target backups using stolen privileged credentials before encrypting production, so the design must make restore points undeletable by any role. Immutable, time-locked storage enforces this at the platform level rather than relying on access control that the attacker already holds.

Why A is correct: Immutability with a retention lock enforces the assume-breach principle so that even a fully compromised privileged identity cannot delete or encrypt the protected restore point, which is exactly what the requirement demands.

Why B is wrong: Geo-replication defends against a datacentre or regional failure and seems resilient, but a privileged attacker can issue deletion against replicated copies just as easily, so it does not counter a malicious insider-level identity.

Why C is wrong: Encryption at rest protects backup confidentiality and is tempting because it sounds like hardening, but it does nothing to stop a Global Administrator from deleting the backups outright, so it misses the stated threat.

Why D is wrong: A tighter recovery point objective improves data freshness and is appealing for resilience metrics, but more frequent copies in deletable storage are equally destroyable by the compromised admin, so the threat is unaddressed.

Free sampleDesign Solutions that Align with Security Best Practices and Prioritieshard

An architect is starting a security design and wants a single Microsoft reference that shows, end to end, how identity, endpoint, SaaS, infrastructure, operational technology, and security operations capabilities fit together and where each control belongs across the estate, so the team can reason about coverage and placement before selecting products. Which Microsoft resource is purpose-built to provide this end-to-end control-placement map?

  • AThe Microsoft cloud security benchmark, which provides the end-to-end map of where identity, endpoint, infrastructure, and security operations controls belong across the whole estate before products are selected.
  • BThe Microsoft Cybersecurity Reference Architectures, which provide the end-to-end diagrammatic map of how identity, endpoint, SaaS, infrastructure, operational technology, and security operations capabilities fit together and where each control belongs. Correct
  • CThe Cloud Adoption Framework for Azure, which provides the end-to-end map of how identity, endpoint, infrastructure, and security operations controls fit together and where each control belongs across the estate.
  • DThe Azure Well-Architected Framework, which provides the end-to-end map of how identity, endpoint, infrastructure, and security operations controls fit together and where each control belongs across the estate.
Recognise the Microsoft Cybersecurity Reference Architectures as the end-to-end diagrams that show capability fit and control placement across every security domain. The MCRA are diagram-led reference architectures whose role is to show how Microsoft security capabilities interlock across identity, endpoint, SaaS, infrastructure, operational technology, and operations, and where each control belongs. This distinguishes them from the MCSB, which scores posture against controls, and from CAF and WAF, which guide adoption and workload design rather than control placement.

Why A is wrong: The MCSB is tempting because it is authoritative and control-mapped, but it is a prescriptive control baseline for assessing posture rather than the architectural diagram that shows how capabilities fit together and where each control belongs.

Why B is correct: The MCRA are explicitly the set of reference diagrams that show how Microsoft security capabilities map across every domain and where controls sit, which is exactly the end-to-end placement map the requirement describes.

Why C is wrong: The Cloud Adoption Framework is appealing because it spans the whole cloud journey, but it sequences governance and migration activities rather than diagramming how individual security capabilities and controls are placed across domains.

Why D is wrong: The Well-Architected Framework is tempting because its security pillar shapes design quality, but it offers workload design principles and trade-offs rather than the cross-domain capability-placement architecture the requirement needs.

Free sampleDesign Solutions that Align with Security Best Practices and Prioritieshard

While designing a ransomware resiliency strategy, an architect is asked to identify the single highest-leverage protection to prioritise first according to Microsoft Security Best Practices, because most large-scale ransomware incidents pivot through one common control failure. Which priority should the design address first?

  • ADeploying Microsoft Defender for Endpoint to every workstation and server so that malicious binaries are blocked at execution time.
  • BSecuring privileged access by isolating administrative identities and enforcing just-in-time elevation through Microsoft Entra Privileged Identity Management. Correct
  • CImplementing immutable backups so that encrypted production data can always be restored after a successful detonation.
  • DEnabling Microsoft Sentinel analytics rules tuned to detect lateral movement and mass file-encryption behaviour across the estate.
Microsoft prioritises securing privileged access as the first ransomware defence because operators depend on escalating to admin rights to spread and destroy. Human-operated ransomware almost always escalates to high-privilege accounts to move laterally, disable defences, and delete backups. Eliminating standing privilege with just-in-time elevation removes the dependency the campaign relies on, which is why Microsoft ranks it ahead of detection and recovery controls.

Why A is wrong: Endpoint protection is essential and tempting as a first move, but it is a detection and prevention layer that attackers routinely evade, whereas removing standing privileged access denies the escalation the campaign relies on, so it is not the first priority.

Why B is correct: Microsoft guidance ranks protecting privileged access as the top ransomware priority because operators escalate to admin rights to spread payloads and destroy backups, so removing standing privilege closes the path the attack depends on.

Why C is wrong: Recoverable backups are a critical pillar and appealing because recovery is the visible outcome, but they assume the attack has already succeeded, so prioritising them before privileged access leaves the breach path open.

Why D is wrong: SIEM analytics improve detection speed and are attractive for visibility, but detection alerts after compromise has begun, so it does not prevent the privileged-access escalation that Microsoft ranks as the leading priority.

Free sampleDesign Solutions that Align with Security Best Practices and Prioritiesmedium

During the govern stage of the Cloud Adoption Framework, an organisation finds that developers occasionally deploy public IP addresses and storage accounts with public network access, breaching policy only discovered weeks later in an audit. The architect wants the governance design to stop these non-compliant resources from being created in the first place. Which Azure Policy effect best meets this preventive requirement?

  • AA deny effect that blocks the creation or update of resources with public IP addresses or public storage network access before they are provisioned. Correct
  • BAn audit effect that records each non-compliant deployment so the governance team has a complete report to review at the end of every month.
  • CAn append effect that adds a cost-centre tag to each new resource so the finance team can attribute spend to the responsible application team.
  • DA deployIfNotExists effect that automatically attaches a diagnostic setting to any storage account after it has been created in the subscription.
Use the Azure Policy deny effect to block non-compliant resource creation at the control plane, providing a preventive governance guardrail rather than detective audit. Cloud Adoption Framework governance distinguishes preventive guardrails from detective controls, and the Azure Policy deny effect rejects non-compliant create or update requests before the resource ever exists. Audit, append and deployIfNotExists effects each react after deployment, so only deny satisfies a requirement to stop the resource being created.

Why A is correct: A deny effect stops non-compliant resources from being provisioned at the control plane, which delivers the preventive guardrail the govern stage requires rather than merely reporting violations after the fact.

Why B is wrong: An audit effect produces useful compliance evidence and is tempting because it gives visibility, but it only flags resources after they exist, so the non-compliant deployments still happen and the preventive requirement is unmet.

Why C is wrong: An append effect is genuine governance tooling and appealing for accountability, but it modifies metadata rather than blocking risky configurations, so public IPs and public storage access are still created freely.

Why D is wrong: A deployIfNotExists effect is powerful for remediating configuration gaps and is tempting because it sounds automatic, but it acts after creation to add settings, so it cannot prevent a public-facing resource from being deployed in the first place.

Free sampleDesign Solutions that Align with Security Best Practices and Prioritieshard

An enterprise wants its privileged administrators to be unable to lose backup-deletion or recovery-vault control even if their day-to-day workstation is compromised by ransomware. Which privileged access design best meets this resiliency requirement?

  • AGranting administrators a permanent standing role for the recovery vault but requiring a second approver before any deletion operation completes.
  • BApplying a Conditional Access policy that requires multifactor authentication and a compliant device whenever any administrator signs in to the recovery vault management portal.
  • CRequiring administrators to perform recovery-vault operations only from a dedicated, hardened privileged access workstation with just-in-time elevation through Microsoft Entra Privileged Identity Management. Correct
  • DEnrolling administrator accounts in Microsoft Entra ID Protection so that risky sign-ins to the recovery vault are detected and automatically blocked by risk-based policy.
Protecting backup and recovery control requires hardened privileged access workstations plus just-in-time elevation so sensitive actions never originate from a compromised everyday device. The enterprise access model separates privileged operations onto dedicated hardened devices and removes standing rights via just-in-time elevation. This ensures a ransomware foothold on a normal workstation cannot reach backup-deletion or vault controls, which session-based or risk-based sign-in controls alone cannot guarantee.

Why A is wrong: Dual approval on deletion adds a useful check and is tempting, but the standing role remains usable from a compromised workstation for many actions, so it does not isolate privileged access from the breached device as required.

Why B is wrong: Requiring multifactor authentication and device compliance strengthens sign-in and is a sensible baseline, but a ransomware foothold on the workstation can ride an already-authenticated session, so this alone does not isolate the privileged action from the compromised device.

Why C is correct: Combining a hardened privileged access workstation with just-in-time elevation ensures the sensitive operation cannot originate from a compromised everyday device and grants no standing rights, which directly satisfies the stated resiliency requirement.

Why D is wrong: Risk-based blocking catches anomalous sign-ins and is attractive, but it is probabilistic and does not prevent a compromised but unflagged workstation from issuing deletion, so it does not guarantee the isolation the requirement demands.

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.