300-730 · Question #96
Refer to the exhibit. A network engineer is reconfiguring clientless SSLVPN during a maintenance window, and after testing the new configuration, is unable to establish the connection. What must be…
The correct answer is B. Enable clientless protocol under the group policy. Clientless SSL VPN access requires the 'vpn-tunnel-protocol ssl-clientless' option to be explicitly enabled in the ASA group policy assigned to the user.
Question
Options
- AEnable client services on the outside interface.
- BEnable clientless protocol under the group policy.
- CEnable DTLS under the group policy.
- DEnable auto sign-on for the user's IP address.
How the community answered
(18 responses)- A6% (1)
- B83% (15)
- C11% (2)
Why each option
Clientless SSL VPN access requires the 'vpn-tunnel-protocol ssl-clientless' option to be explicitly enabled in the ASA group policy assigned to the user.
Enabling client services on the outside interface activates AnyConnect full-tunnel SSL client access, not browser-based clientless VPN sessions.
On a Cisco ASA, the group policy governs which VPN tunnel protocols are permitted for users in that group; if 'ssl-clientless' is absent from the 'vpn-tunnel-protocol' list, users are denied browser-based clientless access regardless of the interface-level SSLVPN configuration. Enabling the clientless protocol under the group policy directly resolves the connection failure.
DTLS is a UDP-based transport optimization used exclusively by AnyConnect full-tunnel clients and has no role in establishing a clientless SSL VPN session.
Auto sign-on configures single sign-on access to internal web applications after a clientless session is already active and does not affect the initial VPN connection establishment.
Concept tested: ASA clientless SSL VPN group policy protocol configuration
Source: https://www.cisco.com/c/en/us/td/docs/security/asa/asa96/configuration/vpn/asa-96-vpn-config/vpn-remote-clientless.html
Topics
Community Discussion
No community discussion yet for this question.