This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(313.6, 84%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAH%3C/text%3E%3C/svg%3E)
The module assessment for AZ-204: Implement user authentication and authorization / Implement authentication by using the Microsoft Authentication Library contains an incorrect answer to the quiz question
This question is related to the following Learning Module
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(12.8, 76%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EV%3C/text%3E%3C/svg%3E)
Hi Abdel Hajou,
We are looking into the issue, and we will get back to you soon.
Hi Abdel Hajou,
Thank you for reaching out to Microsoft Q&A forum.
The PublicClientApplicationBuilder class is very important in the Microsoft Authentication Library (MSAL) for .NET when it comes to applications that need to perform interactive authentication. Its main focus is to enable the construction of authorization contexts, essentially aimed at console applications. It is very important in ensuring that users are able to authenticate securely and comfortably, allowing easy integration with Azure services.
As opposed to some misbeliefs, the PublicClientApplicationBuilder does not exist to create new Azure accounts or include API permissions in registered applications. Rather, it is geared towards facilitating automated processes for creating and managing authentication environments, thus improving the security and stability of application hosting platforms. This is a clear distinction in functionality that makes it easy for developers to use the class in their projects.
If you have found the answer provided to be helpful, please click on the "Accept answer/Upvote" button so that it is useful for other members in the Microsoft Q&A community.
Hi Abdel Hajou,
Just checking in to see if you had a chance to see my previous answer. Please let me know if it was helpful and don't hesitate to reach out to us if you face any issue.
Thank you.
Hi Abdel Hajou,
Just checking in to see if you had a chance to see my previous answer. Please let me know if it was helpful and don't hesitate to reach out to us if you face any issue.
Thank you.
I think the explanation does not match the answer.
The answer option is "Enables the automation and validation of the creation and teardown of environments" but the explanation "is used to build out the authorization context" does not match that answer option. Either the answer option should be reformulated or the explanation for the answer.
Hi Abdel Hajou,
Apologies for the inconsistency in my previous response.
You are correct—the answer option "Enables the automation and validation of the creation and teardown of environments" does not describe the purpose of PublicClientApplicationBuilder. This is a misinterpretation, and I appreciate you flagging it.
Correction (Per Microsoft Docs):
The PublicClientApplicationBuilder class exclusively handles: Authentication configuration for public client apps (desktop, mobile, or console). Interactive token acquisition (e.g., user sign-in via Azure AD). Initializing client applications with parameters like ClientId and Authority.
It has no role in environment automation, which is managed by tools like Azure DevOps or ARM templates.
Next Steps:
Thank you for catching this inconsistency—this helps improve the learning experience for everyone.
The PublicClientApplicationBuilder class is very important in the Microsoft Authentication Library (MSAL) for .NET when it comes to applications that need to perform interactive authentication. Its main focus is to enable the construction of authorization contexts, essentially aimed at console applications. It is very important in ensuring that users are able to authenticate securely and comfortably, allowing easy integration with Azure services.
As opposed to some misbeliefs, the PublicClientApplicationBuilder does not exist to create new Azure accounts or include API permissions in registered applications. Rather, it is geared towards facilitating automated processes for creating and managing authentication environments, thus improving the security and stability of application hosting platforms. This is a clear distinction in functionality that makes it easy for developers to use the class in their projects.