SC-100 Practice Question: Which TWO of the following are true about Azure…

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Initiatives cannot be assigned to a management group

  Why it's wrong here

  This statement is false because Azure Policy initiatives (policy set definitions) are explicitly supported for assignment at management group scopes. In fact, the assignment engine treats initiative definitions the same as individual policy definitions, so a management group, subscription, or resource group can all be the target of an initiative assignment. Assigning an initiative to a management group applies it recursively to all nested subscriptions and resource groups, which is a common way to enforce organizational standards.

• ✓

  Initiatives can be assigned to management groups, subscriptions, or resource groups

  Why this is correct

  Microsoft Azure Policy allows both individual policy definitions and initiative definitions to be assigned at the exact same scopes: management groups, subscriptions, and resource groups. This is by design, because an initiative is simply a bundle of policy definitions that are evaluated together when assigned. Because management groups form a hierarchy, assigning an initiative at a higher scope causes it to be inherited by all descendant scopes, which is useful for enforcing standards across an entire organization.

• ✗

  An initiative can only contain one policy definition

  Why it's wrong here

  An initiative by definition is a collection of multiple policy definitions that are grouped together to achieve a specific compliance or security objective. Although the schema technically permits an initiative to include just one policy definition, the entire purpose of an initiative is to combine related policies into a single unit for easier assignment and reporting. A single policy definition should be assigned directly, not wrapped in an initiative, so saying an initiative can only contain one definition is incorrect.

• ✗

  Initiatives are predefined and cannot be customized

  Why it's wrong here

  Azure Policy includes many built-in initiative definitions, but you can also create fully custom initiatives using the Azure portal, Azure CLI, or ARM/Bicep templates. A custom initiative can reference any combination of built-in and custom policy definitions, and you can define your own parameters to make the initiative flexible across different scopes. This customization capability is essential because regulatory frameworks may not map cleanly to the built-in definitions, so organizations often need tailored initiatives.

• ✓

  Initiatives help to organize policies by grouping them under a common goal

  Why this is correct

  The core purpose of an initiative is to group multiple policy definitions under a common, high-level goal such as 'Enable Monitoring in Azure Security Center' or 'Achieve CIS Compliance.' This grouping enables you to assign all relevant policies at once, track their cumulative compliance state, and manage exceptions or exclusions centrally. Without initiatives, you would have to assign and manage dozens of separate policy definitions individually, which is inefficient and error-prone in large environments.

Go deeper

Related to this question