The DevOps team is troubleshooting a FortiGate software-defined network(SDN) connector that is failing to integrate with a Kubernetes cluster. While using several debug commands, they find that the…

Question

Options

• AThe Kubernetes cluster is using an unsupported API version.
• BThe service principal being used has the correct role assigned.
• CThe FortiGate firewall is using HTTP to send API calls instead of HTTPS.
• DThe configured client secret credentials are incorrect.

• A
  5% (2)
• B
  8% (3)
• C
  3% (1)
• D
  84% (31)

Explanation

HTTP 401 means "Unauthorized" - an authentication failure, which occurs when the credentials presented to the API are invalid or missing. Incorrect client secret credentials (Option D) cause the Kubernetes API server to reject the FortiGate connector's requests because it cannot verify the identity of the caller.

Why the distractors are wrong:

• A - An unsupported API version would return a 400 (Bad Request) or 404 (Not Found), not 401; it's a compatibility issue, not an auth issue.
• B - This describes a correct configuration, so it's not a cause of any error; additionally, a missing or wrong role would produce 403 (Forbidden), not 401.
• C - Using HTTP instead of HTTPS may cause connection or redirect issues, but the specific 401 error code still comes from the authentication layer failing, and the root cause here is credentials, not the protocol.

Memory tip: Think of HTTP status codes in two buckets - 401 = "Who are you?" (authentication/credentials problem) vs. 403 = "I know who you are, but no." (authorization/permissions problem). Whenever you see 401 in a connector or integration context, go straight to credentials first.

No community discussion yet for this question.