Describe the capabilities of Microsoft security solutions →easyMultiple ChoiceObjective-mapped

SC-900 Practice Question: Describe the capabilities of Microsoft security solutions

Exhibit

Refer to the exhibit.
```json
{
  "properties": {
    "displayName": "Marketing Group",
    "description": "Users in marketing department",
    "membershipRule": "(user.department -eq \"Marketing\")",
    "membershipRuleProcessingState": "On",
    "groupTypes": ["DynamicMembership"]
  }
}
```

Refer to the exhibit. You are configuring a Microsoft Entra ID group. What does the exhibit represent?

⚠ Common exam trap

It's easy for candidates to confuse dynamic security groups with Microsoft 365 groups, but the key differentiator is the group type (Security vs. Microsoft 365) shown in the exhibit, not the rule syntax itself.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

A dynamic security group based on department attribute.

The exhibit shows a rule syntax of `(user.department -eq "Sales")`, which is the expression used to dynamically add or remove members based on the department attribute. This is the defining characteristic of a dynamic security group in Microsoft Entra ID, where membership is evaluated automatically when user attributes change.

Answer analysis

Option-by-option breakdown

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

✓
A dynamic security group based on department attribute.
Why this is correct
The JSON clearly indicates a dynamic security group through `groupTypes` containing "Security" and "DynamicMembership". The `membershipRule` property, specifically `(user.department -eq "Sales")`, defines the criteria for automatic membership based on the user's 'department' attribute. This configuration ensures that any user whose department is "Sales" is automatically added to or removed from the group, providing efficient and attribute-driven management.
✗
A Microsoft 365 group with dynamic membership.
Why it's wrong here
A Microsoft 365 group would typically have `mailEnabled` set to true and its `groupTypes` property would include "Unified" or "Microsoft365" in addition to "DynamicMembership". The provided JSON's `groupTypes` array only specifies "Security" and "DynamicMembership", explicitly omitting the characteristics of a Microsoft 365 group. Therefore, this group is not configured as a Microsoft 365 group, despite having dynamic membership capabilities.
✗
A dynamic group based on user location.
Why it's wrong here
The `membershipRule` in the JSON explicitly uses `user.department -eq "Sales"` as the criterion for group membership. This rule is based on the 'department' attribute of user objects, not their location. If the group were based on user location, the rule would reference attributes such as `user.country`, `user.city`, or `user.state` for dynamic membership evaluation.
✗
A static security group with assigned members.
Why it's wrong here
The presence of `groupTypes` including "DynamicMembership" and a defined `membershipRule` unequivocally identifies this as a dynamic group, not a static one. Static security groups do not utilize membership rules; instead, their members are individually and manually assigned by an administrator. This configuration automates membership based on attributes, which is a core characteristic distinguishing it from a static group.

Go deeper

SC-900 Practice Question: Describe the capabilities of Microsoft security solutions

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question