AZ-900 Describe Azure management and governance Practice Question
What is a Service Principal in Azure Active Directory?
⚠ Common exam trap
It's easy for candidates to confuse a Service Principal with a user account or a role, failing to recognize it as a non-interactive identity for applications and automated processes that requires explicit role assignment to access resources.
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
✓
An identity for applications and automated processes to access Azure resources
A Service Principal is an identity created for use with applications, hosted services, and automated tools to access Azure resources. It functions as a security principal that can be assigned roles (via Azure RBAC) to authenticate and authorize operations, enabling secure, programmatic access without requiring a user account.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
A special high-privilege user account for Azure administrators
Why it's wrong here
A Service Principal is not a user account at all; it represents a non-human identity and lacks the interactive sign-in, password change policies, or MFA prompts associated with user accounts. Azure administrators use their own user accounts (often assigned Azure AD roles like Global Administrator or Privileged Role Administrator) for administrative tasks, while Service Principals are used by programs and automation to access resources without human intervention. This option incorrectly assumes a Service Principal is a privileged human account rather than an application identity.
- ✓
An identity for applications and automated processes to access Azure resources
Why this is correct
A Service Principal is an Azure AD identity created for a specific application or automated workload, such as a DevOps pipeline, a script, or a virtual machine extension. It provides the application with its own credentials (client secret, certificate, or assigned managed identity) and is assigned RBAC roles to access resources. Unlike a human user, it is designed for non-interactive authentication and can be tightly scoped to only the permissions its workload requires.
- ✗
A role that grants full access to all Azure resources in a subscription
Why it's wrong here
This option describes an RBAC role definition, specifically the Owner role, which grants full control over all resources in a subscription. A Service Principal is an identity (a 'who') that can be assigned roles, not the role itself (the 'what'). The distinction is fundamental in Azure RBAC: security principals (users, groups, Service Principals, managed identities) are granted permissions via role assignments. Therefore, calling a Service Principal a role misrepresents its nature as the subject of permission assignments rather than the permission set.
- ✗
A security group for organizing users with similar access needs
Why it's wrong here
A security group is a logical container in Azure AD that aggregates users, devices, or other principals for easier assignment of permissions or policies. It is not an identity itself for authentication; rather, it is used to grant access to the members within it. In contrast, a Service Principal is a standalone identity that authenticates as the application, not a group that merely holds other principals. This option incorrectly conflates a management container with an authentication principal.
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
Azure Cost Management and Billing
Key term
User
A user is any person, system, or device that interacts with an IT service, resource, or identity system, typically authenticated through credentials and authorized to perform specific actions.
Key term
Security
Security in IT is the practice of protecting systems, networks, and data from unauthorized access, damage, or theft.
About these practice questions
One of 981 original AZ-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 AZ-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 AZ-900 exam.