Why are short-lived, dynamic secrets in Vault more secure than long-lived, static credentials?
Correct Answer: B
Comprehensive and Detailed In-Depth Explanation: Short-lived, dynamic secrets in Vault enhance security by being generated on-demand and expiring after a short, configurable time-to-live (TTL). This reduces the window of opportunity for credential leakage or misuse. Unlike long-lived, static credentials, which persist indefinitely and increase exposure risk if compromised, dynamic secrets are ephemeral-once they expire, they're automatically revoked by Vault, rendering them useless to attackers. For example, a database credential might last 5 minutes, limiting its attack surface compared to a static password stored indefinitely. Option A (performance via caching) is unrelated to security and inaccurate, as dynamic secrets aren't cached longer. Option C (eliminating authentication) is false; authentication is still required to obtain dynamic secrets. Option D (automatic rotation) applies to some dynamic secrets (e.g., database roles), but the core security benefit is their short lifespan, not just rotation. Vault's documentation on dynamic secrets emphasizes their ephemerality as the key security advantage. References: Dynamic Secrets Tutorial Dynamic Secrets Concepts
Question 102
A Vault cluster's listener configuration is shown in the exhibit. Given the configuration displayed, what VAULT_ADDR environment variable value would target this cluster? Exhibit: listener " tcp " { address = " 10.0.0.50:8200 " tls_disable = true }
Correct Answer: D
The listener is bound to IP address 10.0.0.50 on port 8200, so the client must target that address, not localhost. The configuration also sets tls_disable = true, which means the listener is using plain HTTP rather than HTTPS. Therefore, the correct VAULT_ADDR value is http://10.0.0.50:8200. Option A uses the correct IP and port but the wrong protocol because TLS is disabled. Options B and C target 127.0.0.1, which would only work for a Vault listener bound locally on the client machine. Vault assumes TLS by default unless explicitly disabled, so when TLS is disabled, the scheme must be http://.
