exam questions

Exam AZ-104 All Questions

View all questions & answers for the AZ-104 exam

Exam AZ-104 topic 1 question 7 discussion

Actual exam question from Microsoft's AZ-104
Question #: 7
Topic #: 1
[All AZ-104 Questions]

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's Azure solution 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 CLI.
Does the solution meet the goal?

  • A. Yes
  • B. No
Show Suggested Answer Hide Answer
Suggested Answer: B 🗳️

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
rigonet
Highly Voted 3 years, 2 months ago
ANSWER: B - No You cannot change the usage model after creating the provider.
upvoted 23 times
jackdryan
1 year, 9 months ago
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.
upvoted 2 times
...
...
SeMo0o0o0o
Most Recent 3 months ago
Selected Answer: B
B is correct
upvoted 1 times
...
Nico1973
4 months, 4 weeks ago
Answer: B. No Explanation: The solution provided does not meet the goal of configuring the Per Enabled User setting for the new employees to use Multi-Factor Authentication. To achieve the desired outcome, the Per Enabled User setting should be configured directly for the new employees, not by reconfiguring the existing usage model via the Azure CLI.
upvoted 1 times
...
tashakori
8 months, 2 weeks ago
No is right
upvoted 1 times
...
_gio_
10 months, 3 weeks ago
Selected Answer: B
B agree with rigonet
upvoted 1 times
...
leoiq91
11 months ago
B is correct
upvoted 1 times
...
Metavess
1 year, 3 months ago
A usage model can not be changed once a Multi Factor Authentication has been created.
upvoted 1 times
...
TheCulture
1 year, 4 months ago
Selected Answer: B
Aaaaaah! Same question, same answer! :^) "You can't change the usage model (per enabled user or per authentication) after an MFA provider is created." from https://learn.microsoft.com/en-us/azure/active-directory/authentication/concept-mfa-authprovider
upvoted 2 times
...
dhivyamohanbabu
1 year, 5 months ago
Option B is correct
upvoted 2 times
...
Andre369
1 year, 6 months ago
Selected Answer: A
Yes, the provided solution meets the goal of configuring the usage model for Multi-Factor Authentication (MFA) for the new employees added to Azure Active Directory (Azure AD) after the acquisition. Using the Azure CLI, you can reconfigure the existing usage model from "Per Authentication" to "Per Enabled User" to enforce MFA for all new employees in Azure AD. This ensures that MFA is required for each user individually based on their account configuration, regardless of their location or authentication attempts.
upvoted 2 times
...
Madbo
1 year, 7 months ago
the solution does not meet the goal because the question states that the "Per Enabled User" setting must be set for the usage model, but the solution mentioned only reconfiguring the existing usage model via the Azure CLI. It does not specify how to change the usage model to "Per Enabled User," which requires additional steps such as setting the user-based policy in Azure AD conditional access. Therefore, the correct answer is B: No, the solution does not meet the goal.
upvoted 3 times
...
lokii9980
1 year, 8 months ago
Yes, the solution meets the goal of configuring Multi-Factor Authentication for the new employees added to Azure Active Directory (Azure AD). By reconfiguring the existing usage model via the Azure CLI and setting the Per Enabled User setting, the new employees will be required to use Multi-Factor Authentication. This ensures that the new employees' accounts are secured and protected by an extra layer of security beyond just a password.
upvoted 1 times
...
allyQ
1 year, 9 months ago
Does anyone proof-read these scenarios? ...
upvoted 1 times
...
Rufusinski
1 year, 10 months ago
Selected Answer: B
B is correct.
upvoted 1 times
...
Sunnyb
2 years ago
B is correct
upvoted 1 times
...
NaoVaz
2 years, 2 months ago
Selected Answer: B
As described in the official documentation (https://docs.microsoft.com/en-us/azure/active-directory/authentication/concept-mfa-authprovider): "You cannot change the usage model (per enabled user or per authentication) after an MFA provider is created."
upvoted 2 times
...
BigBigChannel
2 years, 2 months ago
B is correct
upvoted 1 times
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
Loading ...