The correct answer is to configure the role with a ttl of 1h. This works because the database secrets engine supports role-level TTL configuration, which overrides the default lease duration for credentials generated from that specific role, allowing you to enforce a 1-hour expiration without altering the system-wide default lease TTL. On the HashiCorp Vault Associate VA-003 exam, this tests your understanding of how Vault’s lease hierarchy works—role TTLs take precedence over mount-level defaults, a common trap where candidates mistakenly adjust the backend configuration instead. The search intent “vault database role ttl enforce expiration” directly maps to this scenario, emphasizing that role-specific settings provide granular control for dynamic secrets. A useful memory tip: think of role TTL as a “local override”—it only applies to credentials created under that role, leaving other roles and the default lease untouched.
VA-003 Manage Vault leases Practice Question
This VA-003 practice question tests your understanding of manage vault leases. 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 DevOps team is using Vault's database secrets engine to generate dynamic credentials for a PostgreSQL database. They notice that the lease duration is set to 24 hours, but security policy requires that credentials expire after 1 hour. What should the team do to enforce the 1-hour expiration without changing the default lease TTL for all secrets?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Configure the role with a ttl of 1h.
Option C is correct because the database secrets engine allows role-level TTL configuration that overrides the default lease duration for credentials generated from that role. By setting the role's `ttl` to 1h, the team enforces a 1-hour expiration for credentials created under that specific role without affecting the default lease TTL for all secrets or other roles. This directly meets the security policy requirement while maintaining flexibility for other secrets.
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.
✗
Set the mount's max_lease_ttl to 1h.
Why it's wrong here
This would affect all secrets from this mount, not just database credentials.
✗
Ask each developer to set the TTL when requesting credentials.
Why it's wrong here
Users can request a TTL, but it is capped by the role's max_ttl.
✓
Configure the role with a ttl of 1h.
Why this is correct
The role-level ttl overrides the default lease TTL.
Related concept
Read the scenario before looking for a memorised answer.
✗
Use a periodic token with a period of 1h.
Why it's wrong here
Periodic tokens are not appropriate for database credentials.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse mount-level TTL settings with role-level TTL settings, assuming that changing the mount's `max_lease_ttl` is the only way to enforce expiration, when in fact role-level configuration provides granular control without affecting other secrets.
Detailed technical explanation
How to think about this question
Under the hood, Vault's database secrets engine uses roles to define credential generation parameters, including `ttl` and `max_ttl`. When a role has a `ttl` set, Vault uses that value as the lease duration for credentials generated from that role, overriding the mount's default lease TTL. This is implemented via the `database/config` and `database/roles` endpoints, where the role's TTL is stored and applied during credential creation. In real-world scenarios, this allows teams to enforce different expiration policies for different databases or applications (e.g., 1 hour for production, 24 hours for development) without altering global settings.
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.
Manage Vault leases — This question tests Manage Vault leases — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Configure the role with a ttl of 1h. — Option C is correct because the database secrets engine allows role-level TTL configuration that overrides the default lease duration for credentials generated from that role. By setting the role's `ttl` to 1h, the team enforces a 1-hour expiration for credentials created under that specific role without affecting the default lease TTL for all secrets or other roles. This directly meets the security policy requirement while maintaining flexibility for other secrets.
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.
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 →
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.
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.
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.
Sign in to join the discussion.