Refer to the exhibit. The code and the error message that are received when the code is run is presented. What causes issues authenticating with Cisco GMM API using the web-generated API key?

Question

Exhibit

Options

• Afirewall that blocks authentication ports
• Bincorrect username and password
• Cincorrect GMM Cluster selection
• Dincorrect key size and data encryption

• A
  3% (1)
• B
  77% (27)
• C
  9% (3)
• D
  11% (4)

Explanation

Option B is correct because Cisco GMM API authentication via a web-generated API key relies on valid user credentials - the key is bound to a specific username and password combination, so if either is wrong or the account credentials have changed, the API call fails with an authentication error even though the key format itself is valid.

Option A is wrong because if a firewall were blocking authentication ports, you would receive a connection timeout or refusal - not an authentication error message from the API itself, which implies the connection succeeded. Option C is wrong because an incorrect GMM Cluster selection would cause a connectivity or routing error (wrong endpoint), not a credential authentication failure. Option D is wrong because web-generated keys use a fixed, predetermined format and size dictated by the platform - the issue is not with the cryptographic properties of the key but with the credentials it is tied to.

Memory tip: Think of a web-generated API key as a "keycard printed with your name on it" - if your name (credentials) doesn't match the system's records, the door won't open regardless of the card's physical properties.

No community discussion yet for this question.