When constructing a Python script for data extraction using GMM APIs on a Cisco Kinetic Cloud platform, how should the API authentication be implemented?

Question

Options

• AGenerate the API keys once and edit the permissions as needed.
• BGenerate and use the API keys for the required access level from the Kinetic Cloud application.
• CUse a complex username and password with 128-bit encryption.
• DUse a complex username with an auto-generated password from the Kinetic Cloud application.

• A
  6% (2)
• B
  76% (26)
• C
  15% (5)
• D
  3% (1)

Explanation

Option B is correct because Cisco Kinetic Cloud's GMM (Gateway Management Module) APIs use API key-based authentication, and the platform requires you to generate keys scoped to the specific access level your script needs - this follows the principle of least privilege and is the documented authentication method for programmatic access.

Why the distractors are wrong:

• A is wrong because generating keys once and editing permissions later is not how Kinetic Cloud works - you generate keys with the appropriate access level from the start, and permission changes typically require generating new keys.
• C is wrong because Kinetic Cloud GMM APIs do not use username/password authentication with encryption for API access; that describes a different authentication model entirely.
• D is wrong for the same reason as C - auto-generated passwords with usernames are a credential-based auth pattern, not the API key model that Kinetic Cloud uses for programmatic/script access.

Memory tip: Think "Generate and Go" - you Generate API keys at the right access level, then Go use them directly in your script. The word "generate" appears in both A and B, but only B includes the critical qualifier "for the required access level," which reflects the least-privilege principle that governs all proper API authentication design.

No community discussion yet for this question.