Question 508 of 514
Compare and configure secrets enginesmediumMultiple ChoiceObjective-mapped

Quick Answer

The answer is that the database secrets engine uses a separate encryption key that was not re-wrapped after changing the Vault seal configuration. This is correct because when you change the seal—for instance, from the default Shamir seal to AWS KMS—Vault’s underlying encryption mechanism shifts, but the database engine’s internal key material, which protects dynamic credential generation, remains encrypted under the old seal. The KV v2 engine works fine because its static data is decrypted on-the-fly with the new seal, but the database engine fails because its stored key was never re-wrapped. On the HashiCorp Vault Associate VA-003 exam, this tests your understanding of seal migration and the difference between static and dynamic secret engines—a common trap is assuming all engines behave identically after a seal change. Remember: static secrets read, dynamic secrets break; always re-wrap engine keys after a seal swap.

VA-003 Compare and configure secrets engines Practice Question

This VA-003 practice question tests your understanding of compare and configure secrets engines. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.

A SaaS startup uses Vault to manage secrets for their microservices architecture. They have enabled the KV v2 secrets engine at 'secret/' and the database secrets engine at 'database/'. Developers often need to read application configuration from 'secret/app/config' and database credentials from 'database/creds/app-role'. Recently, the security team mandated that all secrets must be encrypted at rest using Vault's seal mechanism. They configured Vault to use AWS KMS as the seal. After enabling the seal, they noticed that reading from 'secret/app/config' still works, but reading from 'database/creds/app-role' returns an error: 'Error making API request: Code: 500. Errors: * 1 error occurred: * failed to decrypt data'. What is the most likely cause?

Clue words in this question

Noticing these words before you look at the options changes how you read each choice.

  • Clue: "most likely"

    Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.

Question 1mediummultiple choice
Full question →

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

The database engine uses a separate encryption key that was not re-wrapped after changing the seal configuration.

Option D is correct because when the seal configuration is changed (e.g., from the default Shamir seal to AWS KMS), the database secrets engine's encrypted storage (which includes its own encryption key used to protect dynamic credentials) must be re-wrapped with the new seal. Vault's KV v2 engine stores data encrypted with the same seal, but reading existing static secrets works because they are decrypted on-the-fly using the new seal. However, the database engine's internal key material was encrypted under the old seal and was not re-wrapped, causing decryption failures when Vault attempts to use it to generate credentials.

Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • The database engine requires a separate seal configuration.

    Why it's wrong here

    Seal is cluster-wide; no separate seal for engines.

  • The database engine configuration is stored in a different location that is not sealed.

    Why it's wrong here

    All data is encrypted by the master key, which is sealed.

  • The AWS KMS key has been rotated and Vault cannot access the old key.

    Why it's wrong here

    If the key was rotated, Vault would have issues with all data, not just database.

  • The database engine uses a separate encryption key that was not re-wrapped after changing the seal configuration.

    Why this is correct

    The database engine may have its own key for encrypting credentials, which needs re-wrapping.

    Clue confirmation

    The clue word "most likely" in the question point toward this answer.

    Related concept

    Read the scenario before looking for a memorised answer.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates assume all secrets engines use the same encryption path and will automatically work after a seal change, but Vault requires explicit re-wrapping of engine-specific key material that was encrypted under the previous seal.

Detailed technical explanation

How to think about this question

Under the hood, Vault uses a master key (encrypted by the seal) to protect the encryption keys used by each secrets engine. When the seal changes (e.g., from Shamir to AWS KMS), the master key is re-encrypted with the new seal, but existing encrypted key material for engines like the database secrets engine must be explicitly re-wrapped via `vault operator rekey` or `vault seal migrate`. In real-world scenarios, failing to re-wrap after a seal migration can cause partial outages where static secrets (KV) work but dynamic secrets (database, PKI) fail, leading to confusing troubleshooting.

KKey Concepts to Remember

  • Read the scenario before looking for a memorised answer.
  • Find the constraint that changes the correct option.
  • Eliminate answers that are true in general but not in this case.

TExam Day Tips

  • Watch for words such as best, first, most likely and least administrative effort.
  • Review why wrong options are wrong, not only why the correct option is correct.

Key takeaway

Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.

Real-world example

How this comes up in practice

A practitioner preparing for the VA-003 exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.

What to study next

Got this wrong? Here's your next step.

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Related practice questions

Related VA-003 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free VA-003 practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this VA-003 question test?

Compare and configure secrets engines — This question tests Compare and configure secrets engines — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: The database engine uses a separate encryption key that was not re-wrapped after changing the seal configuration. — Option D is correct because when the seal configuration is changed (e.g., from the default Shamir seal to AWS KMS), the database secrets engine's encrypted storage (which includes its own encryption key used to protect dynamic credentials) must be re-wrapped with the new seal. Vault's KV v2 engine stores data encrypted with the same seal, but reading existing static secrets works because they are decrypted on-the-fly using the new seal. However, the database engine's internal key material was encrypted under the old seal and was not re-wrapped, causing decryption failures when Vault attempts to use it to generate credentials.

What should I do if I get this VA-003 question wrong?

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Are there clue words in this question I should notice?

Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.

What is the key concept behind this question?

Read the scenario before looking for a memorised answer.

About these practice questions

Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Last reviewed: Jun 11, 2026

Question Discussion

Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.

Loading comments…

Sign in to join the discussion.

This VA-003 practice question is part of Courseiva's free HashiCorp certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the VA-003 exam.