When using iMaster NCE-Campus as the Portal server, in order to allow iMaster NCE-Campus to match the corresponding Portal page according to the user's IP address. When configuring the URL template…

Question

Options

• Assid
• Bdevice-mac
• Cuser-mac
• Duser-ipaddress

• A
  4% (2)
• B
  10% (5)
• C
  16% (8)
• D
  69% (34)

Explanation

Option D (user-ipaddress) is correct because iMaster NCE-Campus needs the client's IP address in the URL template to look up and serve the correct Portal authentication page for that specific user - the match is IP-based by design in this architecture.

Why the distractors are wrong:

• A (ssid) identifies the wireless network name, not the individual user, so it cannot distinguish which Portal page a specific user should see.
• B (device-mac) identifies the access device (AP/switch), not the end user - it tells NCE-Campus where the request came from physically, not who is authenticating.
• C (user-mac) identifies the user's device MAC address, which can be spoofed and is not the parameter NCE-Campus uses for Portal page matching in this flow; IP address is the key correlation field.

Memory tip: Think of it this way - the Portal server needs to answer "which page does this user get?" and in an IP network, users are tracked by their IP address at Layer 3. MAC addresses are local-link only and don't survive routing, so for a centralized server like NCE-Campus, IP = identity.

No community discussion yet for this question.