SC-100 is about to receive a minor update at the end of the month, just some changes for naming and branding fixes, with no change to the topics covered in the objectives. Last year SC-100 received a major restructure, and rather than go through and highlight all the changes, it’s easier if we focus on the end result of those changes. Overall, there wasn’t a major change in the content the exam will focus on, instead it was the streamlining of the objective categories that was the focus.

The biggest challenges I hear about from people who are preparing for this exam, or have attempted it, is that they usually encounter something that they aren’t aware of, or at least aren’t very familiar with it. This is usually a byproduct of perhaps having strong skills in some areas of the exam, but not necessarily having exposure to other things the exam includes.

The easiest example to illustrate this could be someone who works on Azure solutions, but with very little Microsoft 365 exposure, or vice versa, which is very common in some organisations. If we convert that into what you really should be doing with this exam is making sure you aren’t just looking at the exam descriptions for topics you should be aware of, but also make sure you are looking closely at the MCRA diagrams to make sure there isn’t anything lurking that you may not be aware of.

Let’s take a look at the simplified domain objectives and the ones that they replaced

  • Updated domain objectives and weighting
    • Design solutions that align with security best practices and priorities (20–25%)
    • Design security operations, identity, and compliance capabilities (30–35%)
    • Design security solutions for infrastructure (20–25%)
    • Design security solutions for applications and data (20–25%)
  • Previous domain objectives and weighting
    • Design a Zero Trust strategy and architecture (30–35%)
    • Evaluate Governance Risk Compliance (GRC) technical strategies and security operations
      strategies (10–15%)
    • Design security for infrastructure (10–15%)
    • Design a strategy for data and applications (15–20%)
    • Recommend security best practices and priorities (20–25%)

Design solutions that align with security best practices and priorities (20–25%)

Design a resiliency strategy for ransomware and other attacks based on Microsoft Security Best Practices

Design solutions that align with the Microsoft Cybersecurity Reference Architectures (MCRA) and Microsoft cloud security benchmark (MCSB)

Design solutions that align with the Microsoft Cloud Adoption Framework for Azure and the Azure Well-Architected Framework

Design security operations, identity, and compliance capabilities (30–35%)

Design solutions for security operations

Design solutions for identity and access management

Design solutions for securing privileged access

Design solutions for regulatory compliance

Design security solutions for infrastructure (20–25%)

Design solutions for security posture management in hybrid and multicloud environments

Design solutions for securing server and client endpoints

Specify requirements for securing SaaS, PaaS, and IaaS services

Design security solutions for applications and data (20–25%)

Design solutions for securing Microsoft 365

Design solutions for securing applications

Design solutions for securing an organization’s data