Which statement best describes the CLI syntax to configure case sensitivity on a vserver?

• A. It uses 'set cs vserver <name> -caseSensitiveON'.
• B. It uses 'config cs vserver <name> -caseSensitiveON'.
• C. It uses 'set vserver <name> -caseSensitiveON'.
• D. It uses 'enable cs vserver <name> on'.

Answer: (A)

The statement tests how to modify a vserver’s attribute using the correct CLI structure. To enable case sensitivity for a specific vserver, you update its setting with a dedicated command that targets the case-sensitivity feature and applies it to that vserver. The proper syntax is to use the set command, specify the case-sensitivity context, address the vserver by name, and pass the boolean value as a flag. This pattern—set cs vserver -caseSensitive ON—follows the CLI grammar where the attribute is controlled by a flag-style option (with ON/OFF as the value) and the cs scope indicates you’re adjusting the case-sensitivity behavior for that vserver.

Other forms don’t fit the CLI rules: using config isn’t appropriate for this targeted attribute change; using a plain set vserver command omits the specific cs context and the exact -caseSensitive flag, and enable cs vserver on doesn’t align with the per-attribute syntax and is not how you toggle a vserver property in this context.