SC-300 · Question #42
Note: This question is part of series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might…
The correct answer is B. No. Why B (No) is Correct: The Bulk Update feature in the Multi-Factor Authentication portal is used to import or export user MFA states (enabled/disabled/enforced), not to selectively enable MFA for a specific group. While it processes a CSV file, it simply updates individual user…
Question
Note: This question is part of series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. You have an Azure Active Directory (Azure AD) tenant that contains a group named Group1. You need to enable multi-factor authentication (MFA) for the users in Group1 only. Solution: From Multi-Factor Authentication, you select Bulk update, and you provide a CSV file that contains the members of Group1. Does this meet the goal?
Options
- AYes
- BNo
How the community answered
(24 responses)- A17% (4)
- B83% (20)
Explanation
Why B (No) is Correct: The Bulk Update feature in the Multi-Factor Authentication portal is used to import or export user MFA states (enabled/disabled/enforced), not to selectively enable MFA for a specific group. While it processes a CSV file, it simply updates individual user states in bulk - it does not configure MFA conditionally for a group, meaning it doesn't enforce MFA only for Group1 members on an ongoing basis; new members added to Group1 would not automatically inherit MFA.
Why A (Yes) is Wrong: Although Bulk Update technically could enable MFA for the current members listed in a CSV, it is a one-time static action and does not dynamically apply MFA based on group membership. The goal requires a targeted, group-based enforcement, not a manual per-user update.
The Correct Approach: The proper solution is to use Azure AD Conditional Access policies, which allow you to target a specific group (Group1) and require MFA dynamically, including for new members added to the group.
Memory Tip: Think of Bulk Update as a "snapshot in time" tool - it affects individual users listed in a file at that moment, but it's not group-aware or dynamic. For group-based MFA, always think Conditional Access.
Topics
Community Discussion
No community discussion yet for this question.