Implement Farmer Authentication with Microsoft Entra ID

Implement user authentication and authorization
Answer Correct answer: C, D, E — Register the app in Microsoft Entra ID, create a user flow, and add the app to the user flow to implement farmer authentication.

Case study - This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided. To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study. At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section. To start the case study - To display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. When you are ready to answer a question, click the Question button to return to the question. Background - Munson’s Pickles and Preserves Farm is an agricultural cooperative corporation based in Washington, US, with farms located across the United States. The company supports agricultural production resources by distributing seeds fertilizers, chemicals, fuel, and farm machinery to the farms. Current Environment - The company is migrating all applications from an on-premises datacenter to Microsoft Azure. Applications support distributors, farmers, and internal company staff. Corporate website - • The company hosts a public website located at http://www.munsonspicklesandpreservesfarm.com. The site supports farmers and distributors who request agricultural production resources. Farms - • The company created a new customer tenant in the Microsoft Entra admin center to support authentication and authorization for applications. Distributors - • Distributors integrate their applications with data that is accessible by using APIs hosted at http://www.munsonspicklesandpreservesfarm.com/api to receive and update resource data. Requirements - The application components must meet the following requirements: Corporate website - • The site must be migrated to Azure App Service. • Costs must be minimized when hosting in Azure. • Applications must automatically scale independent of the compute resources. • All code changes must be validated by internal staff before release to production. • File transfer speeds must improve, and webpage-load performance must increase. • All site settings must be centrally stored, secured without using secrets, and encrypted at rest and in transit. • A queue-based load leveling pattern must be implemented by using Azure Service Bus queues to support high volumes of website agricultural production resource requests. Farms - • Farmers must authenticate to applications by using Microsoft Entra ID. Distributors - • The company must track a custom telemetry value with each API call and monitor performance of all APIs. • API telemetry values must be charted to evaluate variations and trends for resource data. Internal staff - • App and API updates must be validated before release to production. • Staff must be able to select a link to direct them back to the production app when validating an app or API update. • Staff profile photos and email must be displayed on the website once they authenticate to applications by using their Microsoft Entra ID. Security - • All web communications must be secured by using TLS/HTTPS. • Web content must be restricted by country/region to support corporate compliance standards. • The principle of least privilege must be applied when providing any user rights or process access rights. • Managed identities for Azure resources must be used to authenticate services that support Microsoft Entra ID authentication. Issues - Corporate website - • Farmers report HTTP 503 errors at the same time as internal staff report that CPU and memory usage are high. • Distributors report HTTP 502 errors at the same time as internal staff report that average response times and networking traffic are high. • Internal staff report webpage load sizes are large and take a long time to load. • Developers receive authentication errors to Service Bus when they debug locally. Distributors - • Many API telemetry values are sent in a short period of time. Telemetry traffic, data costs, and storage costs must be reduced while preserving a statistically correct analysis of the data points sent by the APIs. You need to implement farmer authentication. Which three actions should you perform? Each correct answer presents part of the solution. NOTE: Each correct selection is worth one point.

  1. Add the shared access signature (SAS) token to the app.
  2. Create a shared access signature (SAS) token.
  3. Create a user flow. Correct Answer
  4. Add the app to the user flow. Correct Answer
  5. Register the app in Microsoft Entra ID. Correct Answer

Community Votes

CDE
100%

100% of anonymous learners picked answer CDE. Votes are pick records left by other test-takers — they are not the verified answer.

Community Insight

Configuring Microsoft Entra External ID (B2C) authentication requires app registration, user flow creation, and linking the app to the user flow; SAS tokens are for service authorization, not user auth.

Implementing farmer authentication using a Microsoft Entra customer tenant requires registering the application, creating a user flow, and linking the app to that flow. This page explains why these three steps are necessary and why service-level tokens are incorrect for user identity.

Choosing SAS tokens (Options A or B) because developers receive Service Bus authentication errors locally, confusing service-level authorization with user authentication.

Community Discussion (4 comments)

FeriAZ 👍 5 Selected: CDE
Create a user flow (Option C): This step is necessary to define how farmers will authenticate and possibly manage their profiles. Add the app to the user flow (Option D): Essential for integrating the user flow with the application, ensuring the app utilizes the defined authentication process. Register the app in Microsoft Entra ID (Option E): A fundamental step to allow the application to use Microsoft Entra ID for authentication.
0cc50bf 👍 2
Either is valid: 1. Create a user flow 2. Register the app 3. Add the app to the flow OR 1. Register the app 2. Create a user flow 3. Add the app
AzDeveloper 👍 1 Selected: CDE
https://learn.microsoft.com/en-us/azure/active-directory-b2c/tutorial-create-user-flows?pivots=b2c-user-flow
Ciupaz 👍 2 Selected: CDE
Correct. By performing these 3 actions, you will effectively implement farmer authentication using Microsoft Entra ID.

Comments & Corrections

No comments yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

Expert Analysis

Why the Answer Is Correct

To implement farmer authentication using a Microsoft Entra customer tenant (Entra External ID / B2C), you must first register the application so the identity provider recognizes it (Option E). Next, you create a user flow to define the sign-up and sign-in experience for the farmers (Option C). Finally, you add the application to the user flow so the flow can issue tokens to that specific application upon successful authentication (Option D).

Why the Other Options Are Wrong

Options A and B involve Shared Access Signature (SAS) tokens, which are used for delegating access to Azure services like Service Bus or Blob Storage, not for authenticating external human users. While the case study mentions developers receiving Service Bus authentication errors locally, the question specifically asks for implementing farmer authentication, making SAS tokens completely irrelevant to this requirement.

Community Comment Notes

Commenters agree that the sequence of registering the app, creating the user flow, and adding the app to the flow is the standard procedure. As FeriAZ noted, creating a user flow defines how farmers authenticate, and adding the app to it "ensures the app utilizes the defined authentication process". AzDeveloper provided a relevant Microsoft Learn link confirming these exact steps for B2C user flows.

Official Reference

Exam Strategy

Distinguish between user authentication and service authorization; SAS tokens are for Azure resources (like Service Bus), whereas user flows and app registrations are for human users authenticating via Entra ID.

Related Analysis

← Back to AZ-204 Study Guide