AZ-104 Exam QuestionsBrowse all questions from this exam

AZ-104 Exam - Question 6


Note: The question is included in a number of questions that depicts the identical set-up. However, every question has a distinctive result. Establish if the solution satisfies the requirements.

Your company makes use of Multi-Factor Authentication for when users are not in the office. The Per Authentication option has been configured as the usage model.

After the acquisition of a smaller business and the addition of the new staff to Azure Active Directory (Azure AD) obtains a different company and adding the new employees to Azure Active Directory (Azure AD), you are informed that these employees should also make use of Multi-Factor Authentication.

To achieve this, the Per Enabled User setting must be set for the usage model.

Solution: You reconfigure the existing usage model via the Azure portal.

Does the solution meet the goal?

Show Answer
Correct Answer: B

The solution does not meet the goal. You cannot change the usage model (per enabled user or per authentication) after a Multi-Factor Authentication (MFA) provider is created in Azure. Instead, you need to create a new MFA provider with the desired usage model settings to accommodate the new employees.

Discussion

17 comments
Sign in to comment
Mozbius_
Jan 16, 2022

Is it me or the grammar / text of the whole question is very poor?

xell_
Oct 13, 2022

It was very awkward to read

jackdryan
Feb 23, 2023

B is correct. You create a new Multi-Factor Authentication provider with a backup from the existing Multi-Factor Authentication provider data. You cannot change the usage model (per enabled user or per authentication) after an MFA provider is created.

Forkbeard
May 19, 2024

Very poor grammar it is, hmm.

S_SteveOption: A
Jul 19, 2021

answer is correct

pakman
Sep 29, 2021

No it is not. "You cannot change the usage model (per enabled user or per authentication) after an MFA provider is created."

Takloy
Nov 13, 2021

When S_Steve said answer is correct, it means the Answer is No.

TheCultureOption: B
Aug 1, 2023

"You can't change the usage model (per enabled user or per authentication) after an MFA provider is created." https://learn.microsoft.com/en-us/azure/active-directory/authentication/concept-mfa-authprovider

yatharthhhh_xd
Nov 26, 2023

The correct solution is to create a new conditional access policy that applies to the new employees. This policy should be configured to require MFA for the new employees when they sign in to Azure AD from any location.

fiahboneOption: B
Sep 8, 2023

Usage model is immutable. You need to create a new usage model.

MinaruOption: B
Oct 14, 2023

The solution provided does not meet the goal. To achieve the goal of setting the usage model to "Per Enabled User" for the new employees in Azure AD, you need to configure this setting specifically for those users rather than reconfiguring the existing usage model.

Winnie_the_poohOption: B
Mar 20, 2024

Depreciated As of July 1, 2019, Microsoft will no longer offer multifactor authentication server for new deployments and trial tenants. New customers who would like to require multifactor authentication from their users should use cloud-based multifactor authentication. https://aka.ms/mfa-server

anirban7172Option: B
Aug 24, 2023

option B is correct

Dan76
Sep 25, 2023

Does anyone have updated questions from 21.09.2023 (21sh of Sep) with contributor access and can send them to me through email: <a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="bfdbded1d6dad3c8d6d3d3cc8889ffd8d2ded6d391dcd0d2">[email protected]</a>. I would really appreciate it as I need to write and prepare for this exam with limited time and can't afford the contributor access. Thanks. I need to write the exam before the end of this month

nelsontsOption: B
Oct 24, 2023

B is correct.

AlfredPennyworthOption: A
Jan 3, 2024

The most suitable and direct solution for changing the MFA usage model for Azure AD is to reconfigure the existing usage model via the Azure portal. This approach is user-friendly and does not require the complexities of setting up a new MFA provider or using Azure CLI for a task that is more efficiently handled through the portal.

_gio_Option: B
Jan 13, 2024

No because you can't change usage model after MFA provider is created

Amir1909Option: A
Feb 15, 2024

Correct

tashakoriOption: B
Mar 20, 2024

No is right

mattpaulOption: B
Jun 22, 2024

B is the correct choice Get all questions from me contact me on <a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="ec9c8d9980c2818d989884899b9fddd5dbdcac83999880838387c28f8381">[email protected]</a>

Nico1973Option: A
Jul 10, 2024

Answer: A. Yes The solution provided meets the goal of setting the Per Enabled User option for the new employees to use Multi-Factor Authentication in Azure Active Directory. By reconfiguring the existing usage model via the Azure portal, you can ensure that the new employees are required to use Multi-Factor Authentication as intended.

BanthonyBOption: A
Jul 13, 2024

Yes, the solution meets the goal. Reconfiguring the existing usage model via the Azure portal to switch from the Per Authentication option to the Per Enabled User option will allow you to enable Multi-Factor Authentication (MFA) for the new employees. This change ensures that MFA is applied to specific users rather than per authentication attempt, aligning with the requirement to include the new staff in the MFA setup.