VAULT-ASSOCIATE-002 Question #50: Real Exam Question with Answer & Explanation

Question

Why might an application be mapped to an identity entity?

Options

• ATo prohibit Vault administrators from revoking tokens associated with that application
• BTo get around cloud license limitations
• CTo allow an application deployed with multiple authentication methods have a consistent set of
• DTo allow the same application in one cloud to access already provisioned Vault tokens for that

Explanation

Mapping an application to a Vault identity entity allows it to maintain a consistent identity and policy set across various authentication methods it might use.

Common mistakes.

• A. Mapping to an identity entity does not prohibit administrators from revoking tokens; administrators with sufficient privileges can revoke any token.
• B. Identity entities are a security and management feature within Vault, not a mechanism to bypass cloud licensing limitations.
• D. Identity entities provide a consistent identity within Vault, which helps with policy enforcement and token management, but it doesn't directly describe enabling an application in one cloud to access tokens provisioned for another instance of the same application.

Concept tested. Vault identity entities and consistent access

Reference. https://developer.hashicorp.com/vault/docs/concepts/identity#entities

No community discussion yet for this question.