H12-725_V4.0 · Question #6
Use iNaster NCE-Campus as the Portal server and deploy Portal authentication on the Huawei wireless controller. Which configuration is not necessary?
The correct answer is D. MAC authentication template. MAC authentication template (D) is not required because Portal authentication relies on web-based user login - the controller redirects users to a captive portal page where they enter credentials. MAC authentication is a completely separate mechanism that silently authenticates…
Question
Use iNaster NCE-Campus as the Portal server and deploy Portal authentication on the Huawei wireless controller. Which configuration is not necessary?
Options
- AURL template
- BCertification Template
- CPortal authentication template
- DMAC authentication template
How the community answered
(28 responses)- A11% (3)
- B4% (1)
- C7% (2)
- D79% (22)
Explanation
MAC authentication template (D) is not required because Portal authentication relies on web-based user login - the controller redirects users to a captive portal page where they enter credentials. MAC authentication is a completely separate mechanism that silently authenticates devices by their hardware address, with no dependency on Portal workflows.
Why the distractors are wrong:
- A (URL template) is necessary - it tells the controller which URL to redirect unauthenticated users to (the Portal login page hosted on iMaster NCE-Campus).
- B (Certification/Authentication Template) is necessary - it defines the authentication scheme (e.g., RADIUS) used to validate the credentials users submit through the portal.
- C (Portal authentication template) is necessary - it is the core binding element that associates the Portal server address, port, and authentication parameters with the WLAN or access profile.
Memory tip: Picture the Portal flow as a three-piece chain - where to send users (URL template) → how to check their identity (authentication template) → the portal ruleset itself (Portal authentication template). MAC authentication lives on a completely separate chain (silent, device-based), so it never appears in a pure Portal deployment.
Topics
Community Discussion
No community discussion yet for this question.