HCVA0-003 practice question 12 of 35

Elijah manages a legacy application that requires strict control over when its service account credentials change. Which type of credential should be used for this legacy application?

Full set: 285 questions
Answer options
A: static Correct answer
B: dynamic
Correct Answer:
A. static
Explanation

Static credentials are long-lived secrets whose values are defined and managed by an operator. Their lifecycle, including rotation, is controlled manually or through a deliberate, scheduled process. This model provides the "strict control" required for legacy applications that may not be designed to handle the on-demand, ephemeral nature of dynamic credentials. The administrator, Elijah, can decide precisely when to rotate the credential, ensuring the legacy application can be updated accordingly without causing service disruption.

Why Incorrect

B. dynamic: Dynamic credentials are generated on-demand by a secrets engine and have a limited Time-To-Live (TTL). They are automatically revoked, removing the administrator's direct control over the exact timing of the change.

References

1. HashiCorp Learn. (2023). Static and Dynamic Secrets. HashiCorp. In the "Static Secrets" section, it is stated: "Static secrets are secrets that are defined by an operator. They are long-lived and are often shared between multiple clients... The KV secrets engine is a generic key-value store that is used to store static secrets." This highlights the operator-controlled nature suitable for the scenario.

2. HashiCorp Vault Documentation. (2023). KV Secrets Engine. In the introduction, the KV secrets engine is described as a mechanism to "store arbitrary secrets within the configured physical storage for Vault." This implies the secrets do not have an automated lifecycle, giving the operator full control.

3. HashiCorp Vault Documentation. (2023). Database Secrets Engine. This document serves as a contrast, explaining dynamic secrets: "the database secrets engine generates database credentials dynamically based on configured roles." This automated, on-demand generation is the opposite of the "strict control" required.

Scroll to Top