SC-900 Practice Question: Describe the concepts of security, compliance, and identity
A security architect is explaining identity management concepts to the IT team. Which statement correctly describes the difference between authentication and authorization?
⚠ Common exam trap
A common mix-up: candidates confuse the order or swap the definitions of authentication and authorization, leading them to pick Option A or B, but the key is remembering that authentication always precedes authorization and that they are distinct processes.
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
✓
Authentication verifies the identity of a user, while authorization determines the resources they can access.
Authentication is the process of verifying a user's identity (e.g., via password, biometric, or certificate), while authorization determines what resources or actions that authenticated identity is permitted to access. In Microsoft Entra ID, authentication occurs first via protocols like OAuth 2.0 or OpenID Connect, and authorization is then enforced through role-based access control (RBAC) or conditional access policies.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Authentication verifies what a user can do, while authorization verifies who the user is.
Why it's wrong here
This statement incorrectly reverses the fundamental definitions of authentication and authorization. Authentication is the process of verifying a user's claimed identity, confirming 'who you are,' typically through credentials like a username and password. Conversely, authorization determines 'what you can do' or which resources you are permitted to access, based on your verified identity and assigned permissions.
- ✗
Authorization must always occur before authentication.
Why it's wrong here
This statement is incorrect because authorization logically cannot precede authentication. Before a system can determine what actions a user is permitted to perform or which resources they can access, it must first establish and verify the user's identity. Authentication is a foundational prerequisite, ensuring the system knows who is requesting access before evaluating their entitlements.
- ✓
Authentication verifies the identity of a user, while authorization determines the resources they can access.
Why this is correct
This statement accurately distinguishes between authentication and authorization, which are sequential and complementary processes in identity management. Authentication is the crucial initial step where a system confirms the legitimacy of a user's claimed identity, often through credentials. Following successful authentication, authorization then evaluates the user's verified identity against predefined policies to determine their specific access rights to resources.
- ✗
Authentication and authorization are synonymous terms in identity management.
Why it's wrong here
Treating authentication and authorization as synonymous terms is a common misconception, as they represent distinct phases of access control. Authentication is solely focused on proving identity, establishing trust that a user is who they claim to be. Authorization, however, is concerned with the permissions granted to that *verified* identity, dictating access to specific data, applications, or functionalities.
Quick reference
Access Control Model Comparison
| Model | Acronym | Who Controls Access? | Best For |
|---|---|---|---|
| Discretionary Access Control | DAC | Resource owner | Small teams, file shares |
| Mandatory Access Control | MAC | System / security labels | Classified govt / military |
| Role-Based Access Control | RBAC | Administrator (via roles) | Enterprise environments |
| Attribute-Based Access Control | ABAC | Policy engine (user + resource attributes) | Fine-grained, dynamic policies |
| Rule-Based Access Control | RuBAC | System rules / ACLs | Firewall rules, network ACLs |
Go deeper
Related to this question
Learn chapter
Authentication and MFA in Entra
Key term
RBAC
RBAC is a method of restricting network access based on the roles of individual users within an organization, where permissions are assigned to roles rather than to individuals directly.
Key term
OpenID Connect
OpenID Connect is an identity layer on top of OAuth 2.0 that allows applications to verify a user's identity and obtain basic profile information in a standardized way.
About these practice questions
One of 1,279 original SC-900 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This SC-900 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 SC-900 exam.