CYBERSECURITY-ARCHITECTURE-AND-ENGINEERING practice question 6 of 30

An IT team must allow on-premises users to log in to the Azure portal using their corporate credentials. Which strategy should be used to enable identity federation in this scenario?

Full set: 232 questions

Domain Identity and Access Management

Answer options
A: Encrypting with Transport Layer Security (TLS)
B: Deploying a hardware-based two-factor authentication (2FA) solution
C: Integrating with lightweight directory access protocol (LDAP)
D: Configuring third-party authentication with Security Assertion Markup Language (SAML) Correct answer
Correct Answer:
D. Configuring third-party authentication with Security Assertion Markup Language (SAML)
Explanation

Identity federation enables users to access resources across different security domains using a single set of credentials. In this scenario, the goal is to link the on-premises identity system with Azure's identity system. Security Assertion Markup Language (SAML) is an open standard specifically designed for exchanging authentication and authorization data between an identity provider (the on-premises corporate directory) and a service provider (Azure). By configuring SAML-based authentication, the on-premises system can authenticate the user and send a trusted security assertion to Azure, which then grants access to the portal. This establishes the federated trust required for single sign-on (SSO).

Why Incorrect

A. Encrypting with Transport Layer Security (TLS): TLS is a protocol for securing data in transit. While essential for protecting the authentication exchange, it does not provide the identity federation mechanism itself.
B. Deploying a hardware-based two-factor authentication (2FA) solution: 2FA is a method for strengthening authentication by requiring a second verification factor. It is a component of an authentication process, not a strategy for federating identities between systems.
C. Integrating with lightweight directory access protocol (LDAP): LDAP is a protocol for querying and managing directory services. While the on-premises directory likely uses LDAP, it is not the protocol used to establish federated trust with an external service like Azure.

References

1. Microsoft Azure Documentation. "What is federation with Azure AD?". Microsoft Learn. This document explicitly states, "Federation is a collection of domains that have established trust... When you set up federation with your on-premises environment, you establish a trust relationship between your on-premises identity provider and Azure AD." It further identifies SAML 2.0 as a protocol used for this purpose.

2. National Institute of Standards and Technology (NIST). Special Publication (SP) 800-63C: Digital Identity Guidelines: Federation and Assertions. June 2017. Section 5.1.1, "Security Assertion Markup Language (SAML)", describes SAML as a framework for communicating authentication and authorization information between an Identity Provider (IdP) and a Relying Party (RP), which is the exact model of identity federation.

3. Internet2. SAML: The Secret to Centralized & Streamlined Authentication. InCommon Federation. This university-backed consortium material explains, "SAML is the underlying technology that enables federated identity management, allowing a person to use the same digital identity to access a wide variety of systems at their own institution and in the cloud." (Section: "What is SAML?").

Question breakdown

Tests
Select an identity federation mechanism for cloud SSO
Difficulty
Easy

Key idea: SAML lets an on-premises identity provider vouch for a user to a cloud service provider through signed assertions, creating federated single sign-on.

How to reach the answer

  1. The goal is for corporate credentials to work in a separate security domain (Azure), which is federation.
  2. Federation requires a trust protocol between an identity provider and a service provider.
  3. SAML is built for exchanging authentication assertions across domains.
  4. TLS, 2FA and LDAP each cover transport, factor strength or directory queries, not cross-domain trust.

Each option

  • AIncorrect. TLS protects the channel the login travels over, but it does not create a trust relationship between identity systems.
  • BIncorrect. Hardware 2FA adds a verification factor, but it does not federate identities between on-premises and Azure.
  • CIncorrect. LDAP queries and manages a local directory and is not the protocol used to federate trust with an external cloud service provider.
  • DCorrect. SAML-based federation lets the corporate IdP authenticate users and pass trusted assertions to Azure for SSO.

Common trap: LDAP is tempting because the corporate directory (Active Directory) speaks LDAP, but directory access is not the same as cross-domain federation.

In practice: Organizations federate Entra ID (Azure AD) with AD FS or a third-party IdP such as Okta or Ping using SAML/WS-Fed. Users then sign in to Microsoft 365 and the Azure portal with their corporate credentials.

Remember: Cross-domain sign-in with home credentials means federation, and SAML is the classic federation protocol.

Drafted with AI assistance and checked against the answer key.

Keep practicing

Take the free CYBERSECURITY-ARCHITECTURE-AND-ENGINEERING practice test

Ten exam-style questions with answers and explanations, plus the exam facts and study guides.

Start the free practice test

More questions

Other CYBERSECURITY-ARCHITECTURE-AND-ENGINEERING practice questions

Scroll to Top