Quick Answer
The answer is the authorization code flow with PKCE. This flow is correct because it allows an Azure Function app to securely authenticate a signed-in user and obtain an access token for Microsoft Graph API, while PKCE (Proof Key for Code Exchange) adds a cryptographic challenge that prevents interception attacks, making it ideal for public clients like mobile or single-page apps that cannot securely store a client secret. On the Microsoft Azure Developer Associate AZ-204 exam, this scenario tests your understanding of selecting the right OAuth 2.0 flow based on the client type and user presence—a common trap is choosing client credentials for a user-interactive app, but that flow is only for daemon or server-to-server scenarios without a user. Remember, if a user is signing in and the app is a public client, always reach for PKCE. Memory tip: "PKCE protects public clients from code interception—think 'PKCE for People' when a user is involved."
This AZ-204 practice question tests your understanding of connect to and consume azure services and third-party services. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
You need to authenticate an Azure Function app to call Microsoft Graph API on behalf of the signed-in user. Which authentication flow should you use?
Device code flow
Why wrong: For devices without browser.
Client credentials flow
Why wrong: For server-to-server, no user context.
Implicit flow
Why wrong: Deprecated and less secure.
Authorization code flow with PKCE
For user authentication, returns tokens.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Authorization code flow with PKCE
Option C is correct because the authorization code flow is for apps that need to authenticate a user and get an access token for APIs like Graph. Option A is wrong because client credentials flow is for daemon apps without a user. Option B is wrong because device code flow is for devices without a browser. Option D is wrong because implicit flow is deprecated.
Key principle: Authentication proves identity; authorization controls what that identity can do after login. Both must work for full privileged access.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
Device code flow
Why it's wrong here
For devices without browser.
Client credentials flow
Why it's wrong here
For server-to-server, no user context.
Implicit flow
Why it's wrong here
Deprecated and less secure.
Authorization code flow with PKCE
Why this is correct
For user authentication, returns tokens.
Related concept
Authentication checks who the user is.
Common exam traps
Logging in proves the user can authenticate. It does not automatically mean the user is allowed to enter privileged or configuration mode. Watch for AAA authorization, privilege level and command authorization details.
Detailed technical explanation
This kind of question is testing the difference between identity and permission. A user may successfully log in to a router because authentication is working, but still fail to enter configuration mode because authorization is missing, misconfigured or mapped to a lower privilege level.
Key takeaway
Authentication proves identity; authorization controls what that identity can do after login. Both must work for full privileged access.
Real-world example
A company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.
What to study next
Review Cisco AAA concepts — authentication, authorization, and accounting. Study privilege levels (0–15), command authorization under TACACS+, and how RADIUS differs. Then practise related AZ-204 questions on access control and AAA configuration.
Connect to and consume Azure services and third-party services — study guide chapter
Learn the concepts, then practise the questions
Connect to and consume Azure services and third-party services practice questions
Targeted practice on this topic area only
All AZ-204 questions
997 questions across all exam domains
Microsoft Azure Developer Associate AZ-204 study guide
Full concept coverage aligned to exam objectives
AZ-204 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise AZ-204 questions linked to Develop Azure compute solutions.
Practise AZ-204 questions linked to Develop for Azure storage.
Practise AZ-204 questions linked to Implement Azure security.
Practise AZ-204 questions linked to Connect to and consume Azure services and third-party services.
Practise AZ-204 questions linked to Monitor, troubleshoot, and optimize Azure solutions.
Practise AZ-204 questions linked to AZ-204 fundamentals.
Practise AZ-204 questions linked to AZ-204 scenario.
Practise AZ-204 questions linked to AZ-204 troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Connect to and consume Azure services and third-party services — This question tests Connect to and consume Azure services and third-party services — Authentication checks who the user is..
The correct answer is: Authorization code flow with PKCE — Option C is correct because the authorization code flow is for apps that need to authenticate a user and get an access token for APIs like Graph. Option A is wrong because client credentials flow is for daemon apps without a user. Option B is wrong because device code flow is for devices without a browser. Option D is wrong because implicit flow is deprecated.
Review Cisco AAA concepts — authentication, authorization, and accounting. Study privilege levels (0–15), command authorization under TACACS+, and how RADIUS differs. Then practise related AZ-204 questions on access control and AAA configuration.
Authentication checks who the user is.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Same concept, more angles
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. Your web app needs to authenticate users with Microsoft Entra ID (formerly Azure AD). Which OAuth 2.0 flow should you use for a single-page application (SPA) that uses MSAL.js?
easyWhy B: The authorization code flow with PKCE is the recommended OAuth 2.0 flow for SPAs. Option B is wrong because implicit flow is deprecated. Option C is wrong because client credentials flow is for daemon apps. Option D is wrong because resource owner password credentials flow is not recommended.
Last reviewed: Jun 20, 2026
This AZ-204 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-204 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.