nerdexam
CompTIA

SY0-501 · Question #391

A company offers SaaS, maintaining all customers' credentials and authenticating locally. Many large customers have requested the company offer some form of federation with their existing authenticati

The correct answer is A. Implement SAML so the company's services may accept assertions from the customers'. To enable customers to manage user authentication and authorization within their existing infrastructure for a SaaS application, implementing identity federation is necessary.

Submitted by kevin_r· Mar 4, 2026Security architecture

Question

A company offers SaaS, maintaining all customers' credentials and authenticating locally. Many large customers have requested the company offer some form of federation with their existing authentication infrastructures. Which of the following would allow customers to manage authentication and authorizations from within their existing organizations?

Options

  • AImplement SAML so the company's services may accept assertions from the customers'
  • BProvide customers with a constrained interface to manage only their users' accounts in the
  • CProvide a system for customers to replicate their users' passwords from their authentication
  • DUse SOAP calls to support authentication between the company's product and the customers'

How the community answered

(23 responses)
  • A
    70% (16)
  • B
    4% (1)
  • C
    9% (2)
  • D
    17% (4)

Why each option

To enable customers to manage user authentication and authorization within their existing infrastructure for a SaaS application, implementing identity federation is necessary.

AImplement SAML so the company's services may accept assertions from the customers'Correct

SAML (Security Assertion Markup Language) is a widely adopted standard for federated identity, allowing a Service Provider (the SaaS company) to trust authentication assertions issued by an Identity Provider (the customer's existing authentication infrastructure). This implementation delegates user authentication to the customer's identity system, enabling them to retain full control over user identities and access policies within their organization.

BProvide customers with a constrained interface to manage only their users' accounts in the

This approach provides an administrative interface for customer-specific user management within the SaaS system, rather than enabling customers to use their own existing identity infrastructure for authentication and authorization.

CProvide a system for customers to replicate their users' passwords from their authentication

Replicating passwords or hashes from customer systems to the SaaS platform is a significant security risk and does not establish true identity federation, as the SaaS provider would still be responsible for the primary authentication.

DUse SOAP calls to support authentication between the company's product and the customers'

While SOAP is a protocol for web service communication, it does not inherently provide the standardized framework for federated identity assertions and trust relationships that SAML offers, making it too generic to address the specific requirement for federation.

Concept tested: Identity Federation and SAML

Source: https://learn.microsoft.com/en-us/azure/active-directory/develop/single-sign-on-saml-protocol

Topics

#SAML#federation#SSO#identity management

Community Discussion

No community discussion yet for this question.

Full SY0-501 Practice