The answer is Microsoft Entra ID Enterprise Application with SAML-based SSO. This feature is correct because it allows you to register partner applications that support SAML 2.0 or OpenID Connect, enabling federated single sign-on using existing Microsoft Entra ID credentials, while also providing per-application branding customization for the sign-in pages, such as logos and text. On the AZ-305 exam, this tests your understanding of how to bridge identity federation with custom user experience requirements—a common scenario where candidates mistakenly choose Azure AD B2C for external partners, but the key is that these are partner applications, not customer-facing consumer apps. The trap is confusing “custom branding” with tenant-wide company branding; for enterprise application SAML SSO custom branding, you configure it at the application level, not the tenant level. Memory tip: think “Enterprise App = Partner SSO + Per-App Branding,” and remember that SAML-based SSO is the bridge for federated identity with a branded front door.
AZ-305 Practice Question: Design identity, governance, and monitoring solutions
This AZ-305 practice question tests your understanding of design identity, governance, and monitoring solutions. 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.
A company uses Microsoft Entra ID. They want to allow users to sign in to partner applications using their Microsoft Entra ID credentials. The partner applications support SAML 2.0 and OpenID Connect. They also need to customize the appearance of the sign-in pages. Which Microsoft Entra ID feature should they configure?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Microsoft Entra ID Enterprise Application with SAML-based SSO
Microsoft Entra ID Enterprise Application with SAML-based SSO is the correct feature because it allows you to register partner applications that support SAML 2.0 or OpenID Connect, enabling federated single sign-on using existing Microsoft Entra ID credentials. Additionally, you can customize the branding (logo, sign-in page text, etc.) for each enterprise application, meeting the requirement to customize the appearance of sign-in pages.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Microsoft Entra ID B2C
Why it's wrong here
Microsoft Entra ID B2C is designed for customer-facing apps, not for partner access using existing Microsoft Entra ID credentials.
✗
Microsoft Entra ID Application Proxy
Why it's wrong here
Application Proxy provides secure remote access to on-premises web applications, not for partner application SSO.
✓
Microsoft Entra ID Enterprise Application with SAML-based SSO
Why this is correct
Enterprise Applications in Microsoft Entra ID support SAML/OpenID Connect SSO for partner apps and allow customization of sign-in pages.
Related concept
Read the scenario before looking for a memorised answer.
✗
Microsoft Entra ID Conditional Access
Why it's wrong here
Conditional Access enforces policies like MFA but does not configure SSO itself.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse Microsoft Entra ID B2C (designed for external customers) with the Enterprise Application gallery (designed for partner/SaaS apps), but the requirement to use existing corporate credentials and customize sign-in pages points directly to Enterprise Application SSO, not B2C.
Detailed technical explanation
How to think about this question
When you configure a SAML-based Enterprise Application in Microsoft Entra ID, you define a service principal that represents the partner app, and you upload a SAML metadata file or manually configure endpoints and claims. The customization of sign-in pages is achieved through the 'Branding' settings at the tenant level or per application via the 'Properties' blade, which overrides the default Microsoft sign-in page with your company logo and text. This setup uses the SAML 2.0 HTTP-POST binding for assertion delivery and supports SP-initiated SSO, which is the most common pattern for partner integrations.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
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
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
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-305 question in full detail.
Design identity, governance, and monitoring solutions — This question tests Design identity, governance, and monitoring solutions — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Microsoft Entra ID Enterprise Application with SAML-based SSO — Microsoft Entra ID Enterprise Application with SAML-based SSO is the correct feature because it allows you to register partner applications that support SAML 2.0 or OpenID Connect, enabling federated single sign-on using existing Microsoft Entra ID credentials. Additionally, you can customize the branding (logo, sign-in page text, etc.) for each enterprise application, meeting the requirement to customize the appearance of sign-in pages.
What should I do if I get this AZ-305 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
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 →
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-305 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-305 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.