nerdexam
CompTIA

CAS-002 · Question #895

A network engineer wants to deploy user-based authentication across the company's wired and wireless infrastructure at layer 2 of the OSI model. Company policies require that users be centrally…

The correct answer is C. LDAP D. RADIUS. Layer 2 user-based network authentication with centralized management and role-based access control requires RADIUS for AAA enforcement at the network edge and LDAP for centralized directory services with hierarchical trust.

Technical Integration of Enterprise Components

Question

A network engineer wants to deploy user-based authentication across the company's wired and wireless infrastructure at layer 2 of the OSI model. Company policies require that users be centrally managed and authenticated and that each user's network access be controlled based on the user's role within the company. Additionally, the central authentication system must support hierarchical trust and the ability to natively authenticate mobile devices and workstations. Which of the following are needed to implement these requirements? (Select TWO).

Options

  • ASAML
  • BWAYF
  • CLDAP
  • DRADIUS
  • EShibboleth
  • FPKI

How the community answered

(42 responses)
  • A
    2% (1)
  • B
    7% (3)
  • C
    76% (32)
  • E
    2% (1)
  • F
    12% (5)

Why each option

Layer 2 user-based network authentication with centralized management and role-based access control requires RADIUS for AAA enforcement at the network edge and LDAP for centralized directory services with hierarchical trust.

ASAML

SAML operates at the application layer (Layer 7) for web-based SSO and is not applicable to Layer 2 wired or wireless network access authentication.

BWAYF

WAYF (Where Are You From) is a discovery service used in federated web identity systems to route users to their home IdP and has no role in Layer 2 network authentication.

CLDAPCorrect

LDAP provides a hierarchical directory structure (supporting 'hierarchical trust' as stated in the requirement) and serves as the central user store from which authentication credentials and group/role memberships are retrieved. It natively supports workstations and mobile devices through directory-integrated authentication and is the backend typically queried by the RADIUS server to validate credentials.

DRADIUSCorrect

RADIUS implements 802.1X authentication at Layer 2 of the OSI model for both wired (IEEE 802.1X port-based NAC) and wireless infrastructure, enforcing per-user network access policies. It integrates directly with LDAP to authenticate users centrally and can return vendor-specific attributes (VSAs) to enforce role-based VLAN or ACL assignments on switches and access points.

EShibboleth

Shibboleth is a web-based SAML federation solution for application-layer SSO and does not participate in Layer 2 network access control.

FPKI

PKI provides certificate infrastructure and can complement 802.1X (EAP-TLS), but on its own it is not a user management or Layer 2 authentication system with centralized role-based access control.

Concept tested: 802.1X Layer 2 authentication with RADIUS and LDAP

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

Topics

#RADIUS#LDAP#802.1X#network access control

Community Discussion

No community discussion yet for this question.

Full CAS-002 Practice