In the Portal authentication scenario, if there is no condition to deploy an external independent Portal server, the built-in Portal server of WAC can be used for authentication. Which of the…

Question

Options

• ADue to compatibility issues with some mobile browsers, Portal authentication users using these
• BThe built-in Portal server does not support MAC-first Portal authentication
• CThe built-in Portal server does not support custom authentication page content and style
• DCompared with the external Portal server, the built-in Portal server has simple functions and

• A
  5% (2)
• B
  2% (1)
• C
  78% (32)
• D
  15% (6)

Explanation

Option C is the incorrect statement because the WAC built-in Portal server does support basic customization of the authentication page content and style - users can modify elements like logos, background images, and text to fit their organization's branding needs. Claiming it offers zero customization is factually wrong.

Why the distractors are correct (and thus not the answer):

• Option A accurately notes that the built-in Portal has compatibility problems with certain mobile browsers, which is a known limitation of the simplified server implementation.
• Option B is correct - the built-in Portal server genuinely does not support MAC-first (MAC address priority) Portal authentication, which requires a more capable external Portal server.
• Option D is correct - the built-in Portal server is by design a stripped-down solution; it lacks advanced features (like MAC-first auth, complex policy logic, and third-party integration) that external Portal servers provide.

Memory tip: Think of it this way - "built-in = basic but not bare." The built-in Portal gives you just enough customization to make the login page look like yours, but strips out complex authentication flows (like MAC-first). Any answer claiming it has zero customization ability is the trap, because even a basic server lets you brand the page.

No community discussion yet for this question.