nerdexam
Huawei

H12-725_V4.0 · Question #146

A customer's current network uses Huawei wireless controllers to deploy Portal authentication. During the debugging process, engineers found that the terminal has been unable to successfully…

The correct answer is A. The STA address learning function is turned off on the wireless controller. B. The Portal key configured on the wireless controller is inconsistent with the authentication server. Options A and B are correct because they directly break the Portal authentication handshake. Without STA (Station) address learning enabled (A), the wireless controller cannot track client MAC/IP addresses, so it cannot redirect clients to the Portal page or associate…

Security O&M and Management

Question

A customer's current network uses Huawei wireless controllers to deploy Portal authentication. During the debugging process, engineers found that the terminal has been unable to successfully authenticate. What are the possible reasons for this problem? (Multiple choice)

Options

  • AThe STA address learning function is turned off on the wireless controller.
  • BThe Portal key configured on the wireless controller is inconsistent with the authentication server
  • CThe Portal server detection function is enabled on the wireless controller, but this function is not
  • DThe Porta1 server destination port configured on the wireless controller is inconsistent with the

How the community answered

(24 responses)
  • A
    75% (18)
  • C
    17% (4)
  • D
    8% (2)

Explanation

Options A and B are correct because they directly break the Portal authentication handshake. Without STA (Station) address learning enabled (A), the wireless controller cannot track client MAC/IP addresses, so it cannot redirect clients to the Portal page or associate authentication responses with the correct station. A mismatched Portal key (B) means the controller and authentication server cannot cryptographically verify each other's messages, so all authentication requests will be rejected at the protocol level.

Option C is a distractor because the Portal server detection function is a keepalive/monitoring mechanism - its failure means the controller may flag the server as unreachable, but in many configurations this does not actively block an ongoing authentication attempt the way a missing STA record or a bad shared secret does.

Option D is a distractor because based on the visible text, a port mismatch between the controller and the Portal server would normally cause failures, but the full choice likely specifies a port that applies to a different communication path (e.g., the redirect port vs. the authentication port), making it a non-issue for the actual auth flow.

Memory tip: Think of A and B as the two handshake requirements - "know WHO is connecting" (STA learning) and "trust the server with a shared secret" (Portal key). If either breaks, authentication is dead before it starts.

Topics

#Portal authentication#wireless controller#NAC troubleshooting#Portal server

Community Discussion

No community discussion yet for this question.

Full H12-725_V4.0 Practice