Question 528 of 997
Implement Azure securityhardMultiple ChoiceObjective-mapped

Quick Answer

The answer is to use the [Authorize] attribute with a policy that requires a specific claim. This is correct because ASP.NET Core’s policy-based authorization allows you to define granular access rules in the Startup class, where you can configure a policy to demand a particular claim type and value. When the [Authorize] attribute is applied to a controller or action with that policy name, the middleware checks the incoming token’s claims against the policy before granting access. On the AZ-204 exam, this tests your understanding of how to implement fine-grained access control in Azure AD-protected APIs, often appearing in scenario-based questions where you must choose between role-based and claim-based authorization. A common trap is confusing the [Authorize] attribute’s Roles property with policies—remember, roles are just one type of claim, but policies let you check any custom claim. Memory tip: think “Policy picks the claim” to recall that policies are the mechanism for checking specific claims beyond built-in roles.

AZ-204 Implement Azure security Practice Question

This AZ-204 practice question tests your understanding of implement azure security. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. 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 are developing a .NET Core API that uses Azure AD for authentication. You want to restrict access to specific claims. Which middleware component should you use to check claims?

Question 1hardmultiple choice
Full question →

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

Use the [Authorize] attribute with a policy that requires a specific claim

The [Authorize] attribute with policy-based authorization allows checking claims via policies configured in Startup.

Key principle: Authentication proves identity; authorization controls what that identity can do after login. Both must work for full privileged access.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Use the UseAuthorization middleware in the pipeline

    Why it's wrong here

    UseAuthorization enables authorization but does not by itself check claims; you need policies.

  • Use the UseAuthentication middleware to validate tokens

    Why it's wrong here

    UseAuthentication validates the token but does not check specific claims.

  • Use the [Authorize] attribute with a policy that requires a specific claim

    Why this is correct

    Policy-based authorization with claims is the standard approach in ASP.NET Core.

    Related concept

    Authentication checks who the user is.

  • Manually parse the JWT in a custom middleware

    Why it's wrong here

    This is possible but not recommended; the built-in authorization is simpler and more maintainable.

Common exam traps

Common exam trap: authentication is not authorization

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

How to think about this question

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.

KKey Concepts to Remember

  • Authentication checks who the user is.
  • Authorization controls what the user is allowed to do after login.
  • Privilege levels affect access to EXEC and configuration commands.
  • AAA, TACACS+ and RADIUS can separate login success from command access.

TExam Day Tips

  • Do not assume successful login means full administrative access.
  • Look for words such as cannot enter configuration mode, privilege level, authorization or command access.
  • Separate login problems from permission problems before choosing the answer.

Key takeaway

Authentication proves identity; authorization controls what that identity can do after login. Both must work for full privileged access.

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.

What to study next

Got this wrong? Here's your next step.

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.

Related practice questions

Related AZ-204 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free AZ-204 practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this AZ-204 question test?

Implement Azure security — This question tests Implement Azure security — Authentication checks who the user is..

What is the correct answer to this question?

The correct answer is: Use the [Authorize] attribute with a policy that requires a specific claim — The [Authorize] attribute with policy-based authorization allows checking claims via policies configured in Startup.

What should I do if I get this AZ-204 question wrong?

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.

What is the key concept behind this question?

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 →

How Courseiva writes practice questions · Editorial policy

Last reviewed: Jun 20, 2026

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.

Loading comments…

Sign in to join the discussion.

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.