nerdexam
CompTIA

SY0-501 · Question #3

Multiple organizations operating in the same vertical want to provide seamless wireless access for their employees as they visit the other organizations. Which of the following should be implemented…

The correct answer is B. RADIUS federation. To provide seamless 802.1x wireless access across multiple organizations, RADIUS federation is the appropriate solution as it allows different RADIUS infrastructures to trust and forward authentication requests to one another.

Submitted by mike_84· Mar 4, 2026Endpoint Security

Question

Multiple organizations operating in the same vertical want to provide seamless wireless access for their employees as they visit the other organizations. Which of the following should be implemented if all the organizations use the native 802.1x client on their mobile devices?

Options

  • AShibboleth
  • BRADIUS federation
  • CSAML
  • DOAuth
  • EOpenlD connect

How the community answered

(29 responses)
  • A
    3% (1)
  • B
    72% (21)
  • C
    3% (1)
  • D
    7% (2)
  • E
    14% (4)

Why each option

To provide seamless 802.1x wireless access across multiple organizations, RADIUS federation is the appropriate solution as it allows different RADIUS infrastructures to trust and forward authentication requests to one another.

AShibboleth

Shibboleth is an open-source project that uses SAML for web-based single sign-on (SSO) and identity federation, not for native 802.1x wireless authentication.

BRADIUS federationCorrect

RADIUS federation enables independent RADIUS servers, typically managed by different organizations, to securely forward authentication requests to each other's home servers. This allows an employee from one organization to authenticate against their own identity provider when connecting to another organization's 802.1x-protected wireless network, ensuring seamless access without creating duplicate accounts or complex manual configurations.

CSAML

SAML (Security Assertion Markup Language) is an XML-based standard primarily used for exchanging authentication and authorization data between an identity provider and a service provider in web-based scenarios, not for 802.1x.

DOAuth

OAuth (Open Authorization) is an authorization framework for granting access delegation, commonly used for web and API access without sharing user credentials, and is not an authentication protocol for 802.1x.

EOpenlD connect

OpenID Connect is an identity layer built on top of the OAuth 2.0 protocol, primarily used for user authentication in web and mobile applications, not for 802.1x network access.

Concept tested: Federated 802.1x wireless authentication via RADIUS

Source: https://learn.microsoft.com/en-us/windows-server/networking/technologies/nps/nps-top

Topics

#RADIUS federation#802.1x#wireless authentication#identity federation

Community Discussion

No community discussion yet for this question.

Full SY0-501 Practice