The answer is application permissions with the client credentials flow. This is correct because a background service or daemon application calling Microsoft Graph without a signed-in user must authenticate as itself, not on behalf of a user, which requires application permissions (app roles) rather than delegated permissions. The client credentials OAuth 2.0 grant allows the service to obtain an access token using its own client ID and a secret or certificate, enabling server-to-server authentication with no user interaction. On the AZ-204 exam, this scenario tests your understanding of when to choose application permissions over delegated permissions—a common trap is selecting delegated permissions for a background service, which would fail because no user is present to consent. Remember the key distinction: if there is no signed-in user, you must use application permissions and the client credentials flow. A helpful memory tip is “No user? No delegated—use app-only credentials.”
AZ-204 Implement Azure security Practice Question
This AZ-204 practice question tests your understanding of implement azure security. 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. A key principle to apply: application permissions are for daemon apps acting as themselves.. 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.
A background service must call Microsoft Graph without a signed-in user. Which Microsoft identity platform permission model is required?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Application permissions with client credentials flow
Option D is correct because when a background service or daemon calls Microsoft Graph without a signed-in user, it must authenticate as itself using application permissions (app roles) rather than delegated permissions. The client credentials flow (OAuth 2.0 grant type) allows the service to obtain an access token using its own credentials (client ID and client secret or certificate), without any user interaction. This flow is designed for server-to-server scenarios where the application acts on its own behalf.
Key principle: Application permissions are for daemon apps acting as themselves.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Password hash synchronization
Why it's wrong here
Password hash synchronization is an identity sync method, not an API permission model.
✗
Delegated permissions only
Why it's wrong here
Delegated permissions require a signed-in user.
✗
Device code flow
Why it's wrong here
Device code flow is for user sign-in on input-constrained devices.
✓
Application permissions with client credentials flow
Why this is correct
Application permissions allow daemon apps to act as themselves without a user context.
Related concept
Application permissions are for daemon apps acting as themselves.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse delegated permissions (which require a user) with application permissions (which do not), and mistakenly choose the device code flow thinking it works without a user, when in fact it still requires user authentication via a browser.
Detailed technical explanation
How to think about this question
Under the hood, the client credentials flow uses the OAuth 2.0 token endpoint with grant_type=client_credentials, and the application must have pre-configured application permissions (e.g., Mail.Read.All) granted by an administrator. The access token contains the app's identity (iss and sub claims) rather than a user's identity, and Microsoft Graph validates that the token has the required app roles. A subtle behavior is that even with application permissions, some Microsoft Graph APIs (e.g., those requiring user context) may still fail, so developers must verify API support for app-only calls.
KKey Concepts to Remember
Application permissions are for daemon apps acting as themselves.
Client credentials flow uses application's own credentials (secret/certificate).
No signed-in user is involved in the client credentials flow.
Administrator consent is required for application permissions.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Application permissions are for daemon apps acting as themselves.
Real-world example
How this comes up in practice
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.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this AZ-204 question in full detail.
Review application permissions are for daemon apps acting as themselves., then practise related AZ-204 questions on the same topic to reinforce the concept.
Implement Azure security — This question tests Implement Azure security — Application permissions are for daemon apps acting as themselves..
What is the correct answer to this question?
The correct answer is: Application permissions with client credentials flow — Option D is correct because when a background service or daemon calls Microsoft Graph without a signed-in user, it must authenticate as itself using application permissions (app roles) rather than delegated permissions. The client credentials flow (OAuth 2.0 grant type) allows the service to obtain an access token using its own credentials (client ID and client secret or certificate), without any user interaction. This flow is designed for server-to-server scenarios where the application acts on its own behalf.
What should I do if I get this AZ-204 question wrong?
Review application permissions are for daemon apps acting as themselves., then practise related AZ-204 questions on the same topic to reinforce the concept.
What is the key concept behind this question?
Application permissions are for daemon apps acting as themselves.
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 →
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. A background service must call Microsoft Graph without a signed-in user. Which Microsoft identity platform permission model is required? The design must avoid adding custom operational scripts.
medium
A.Password hash synchronization
B.Delegated permissions only
C.Device code flow
✓ D.Application permissions with client credentials flow
Why D: Application permissions with the client credentials flow are required because the background service must call Microsoft Graph without a signed-in user. This flow uses OAuth 2.0 client credentials grant (RFC 6749) where the service authenticates as itself using a client secret or certificate, not on behalf of a user. Delegated permissions (Option B) always require a signed-in user context, making them unsuitable for unattended background services.
Variation 2. A background service must call Microsoft Graph without a signed-in user. Which Microsoft identity platform permission model is required? The architecture review board prefers a managed AWS-native control.
medium
A.Password hash synchronization
B.Delegated permissions only
C.Device code flow
✓ D.Application permissions with client credentials flow
Why D: For a background service calling Microsoft Graph without a signed-in user, the application must authenticate as itself, not on behalf of a user. Application permissions, combined with the client credentials flow (OAuth 2.0), allow the service to obtain an access token using its own identity (client ID and client secret or certificate), without any user interaction. This is the only model that supports non-interactive, daemon-style access to Microsoft Graph.
Variation 3. A background service must call Microsoft Graph without a signed-in user. Which Microsoft identity platform permission model is required? The team wants the control to be enforceable during normal operations.
medium
A.Password hash synchronization
B.Delegated permissions only
C.Device code flow
✓ D.Application permissions with client credentials flow
Why D: Option D is correct because the scenario requires an unattended background service to call Microsoft Graph without a signed-in user. Application permissions, combined with the client credentials flow (OAuth 2.0 grant type), allow the service to authenticate as itself using a client ID and client secret or certificate, obtaining an access token with pre-authorized application-level permissions. This model enforces control during normal operations because the permissions are granted directly to the application and cannot be delegated by a user, ensuring consistent access regardless of user presence.
Variation 4. A background data pipeline runs on a schedule and must read user profile data from Microsoft Graph. No user is present during execution. The service authenticates to Microsoft Entra ID and calls the Graph API. Which permission type and OAuth 2.0 flow are correct for this scenario?
hard
✓ A.Application permissions with the client credentials flow, authenticating with the app's client ID and secret (or certificate)
B.Delegated permissions with the authorization code flow, initiating a browser redirect to collect user consent
C.Delegated permissions with the device code flow, prompting a user to authenticate on a separate device
D.Application permissions with the on-behalf-of flow, passing the calling user's token to the Graph API
Why A: This scenario requires a background service to access Microsoft Graph without any user interaction. Application permissions are designed for such non-interactive, service-to-service calls, and the client credentials OAuth 2.0 flow (defined in RFC 6749 section 4.4) allows the app to authenticate using its own identity (client ID and secret or certificate) to obtain an access token. Delegated permissions would be incorrect because they require a signed-in user context, which is absent here.
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.
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.