Refer to the exhibit. An administrator wants to temporarily disable Kerberos Auth on the Workspace ONE Access Connector from the access console; however, this setting is greyed out. What does the…

Question

Exhibit

Options

• ALogin as super admin role on the Access admin console and disable Kerberos Auth.
• BDelete Kerberos Auth option.
• CLogin the connector host machine and disable Kerberos Auth.
• DAdd a second connector without Kerberos Auth.

• A
  4% (1)
• B
  4% (1)
• C
  78% (18)
• D
  13% (3)

Explanation

When the Kerberos Auth toggle is greyed out in the Workspace ONE Access admin console, it means the setting is being managed at the connector host level, not the cloud console level - so the administrator must log directly into the connector host machine and disable Kerberos Auth there (Option C).

Why the distractors are wrong:

• A is incorrect because the super admin role still cannot override a greyed-out setting in the console; the permission boundary is architectural, not role-based.
• B is incorrect because deleting the Kerberos Auth option is not a supported action and would be destructive rather than a temporary disable.
• D is incorrect because adding a second connector is a workaround that doesn't address the existing connector and introduces unnecessary infrastructure complexity.

Memory tip: Think of it this way - grey = go to the machine. When a cloud console setting is greyed out in Workspace ONE Access, it signals that control has been handed off to the local connector host, so you must manage it locally on that machine rather than remotely through the web UI.

No community discussion yet for this question.