A Citrix Administrator is creating a new SSL vServer and notices that ns_default_ssl_profile_frontend SSL profile is automatically bound to the SSL vServer. Which two actions can the administrator…

Question

Options

• AUnbind the ns_default_ssl_profile_frontend SSL profile from the SSL vServer without binding a
• BCreate a separate SSL profile.
• CUnbind the default SSL profile and bind the newly created SSL profile.
• DGlobally disable the ns_default_ssl_profile_frontend SSL profile.
• EGlobally unbind the ns_default_ssl_profile_frontend SSL.

• A
  81% (39)
• C
  2% (1)
• D
  4% (2)
• E
  13% (6)

Explanation

When the default SSL profile feature is enabled on a Citrix ADC, ns_default_ssl_profile_frontend is automatically bound to all SSL vServers, but administrators retain the ability to manage it at the vServer level - meaning they can unbind it from a specific vServer (A) without needing to globally alter the feature, and they can create a custom SSL profile with desired settings (B) to tailor SSL behavior per vServer.

Why the distractors are wrong:

• C describes a valid workflow but is considered a combined follow-on action from A and B, not a standalone distinct action - the exam separates the steps.
• D is incorrect because there is no option to "globally disable" only the frontend default profile; you can only enable/disable the entire default SSL profile feature, which affects all vServers.
• E is incorrect because there is no "global unbind" command for the default SSL profile - unbinding is performed at the individual vServer level.

Memory tip: Think "Create then Customize" - you first Build a new profile, then you have the freedom to Alter (unbind) the default. The global options (D, E) are distractors because the default profile feature is an all-or-nothing global switch - you work around it per-vServer, not globally.

No community discussion yet for this question.