Which two components are required from the Cisco Intersight REST API Authentication? (Choose two.)

Question

Options

• ASHA256 hash of the message body and message headers.
• BSHA256 hash of the message body, including empty message bodies.
• CRSA private key with a key size of 2048.
• DRSA private key with a key size of 1024.
• ESHA384 hash of the message body, excluding empty message bodies.

• A
  88% (30)
• B
  3% (1)
• D
  6% (2)
• E
  3% (1)

Explanation

Cisco Intersight REST API uses HTTP Signature-based authentication, which requires a SHA256 hash covering both the message body and the request headers (A) - not just the body alone - because headers like Date, Host, and (request-target) are included in the signing string to prevent replay attacks and ensure request integrity. It also mandates an RSA private key of 2048 bits (C), which is the minimum key size Intersight accepts for cryptographic security.

Why the distractors are wrong:

• B is incorrect because it only hashes the body (even if empty), omitting headers - Intersight's signing process requires headers to be included.
• D is wrong because 1024-bit RSA is cryptographically weak and explicitly rejected by Intersight; 2048 is the enforced minimum.
• E is wrong on two counts: Intersight uses SHA256, not SHA384, and empty bodies are not excluded - they still require a digest value.

Memory tip: Think "2048 and Headers" - Intersight needs a strong key (2048-bit RSA, not weak 1024) and a complete hash (body + headers, not body alone). If an option drops either the key size or the headers, it's wrong.

No community discussion yet for this question.