- A
They forgot to set the new intermediate certificate as the issuing CA by writing it to the correct path (e.g., pki/intermediate/set-signed).
After signing the CSR, the signed certificate must be written back to the intermediate mount via set-signed endpoint.
- B
They forgot to update the CRL distribution points on the new intermediate.
CRL distribution points are important but not the cause of the error; missing settings would affect CRL fetch, not immediate issuance failure.
- C
They changed the root CA's key algorithm, causing incompatibility.
Why wrong: The root CA's key algorithm is unchanged; the intermediate uses a key pair compatible with the root.
- D
They did not revoke the old intermediate CA before importing the new one.
Why wrong: Revoking the old intermediate is not required; it can coexist until its expiration.
VA-003 Compare and configure secrets engines Practice Question
This VA-003 practice question tests your understanding of compare and configure secrets engines. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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 company is using Vault's PKI secrets engine to issue certificates for internal services. They have set up a root CA and an intermediate CA. The intermediate CA's certificate expires soon, and they need to renew it. They generate a new intermediate CSR and have it signed by the root CA. After importing the new intermediate certificate, the team notices that certificates issued by the old intermediate are still valid but new certificate requests fail with 'no valid intermediate CA found'. What step did the team likely miss?
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
They forgot to set the new intermediate certificate as the issuing CA by writing it to the correct path (e.g., pki/intermediate/set-signed).
In Vault's PKI secrets engine, after the root CA signs a new intermediate certificate, the signed certificate must be explicitly set as the issuing CA for the intermediate's mount. This is done by writing the signed certificate to the `pki/intermediate/set-signed` endpoint. Without this step, the intermediate mount still references the old (expiring) certificate, causing new certificate requests to fail with 'no valid intermediate CA found' because Vault cannot locate a valid issuing certificate for signing operations.
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.
- ✓
They forgot to set the new intermediate certificate as the issuing CA by writing it to the correct path (e.g., pki/intermediate/set-signed).
Why this is correct
After signing the CSR, the signed certificate must be written back to the intermediate mount via set-signed endpoint.
Related concept
Read the scenario before looking for a memorised answer.
- ✓
They forgot to update the CRL distribution points on the new intermediate.
Why this is correct
CRL distribution points are important but not the cause of the error; missing settings would affect CRL fetch, not immediate issuance failure.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
They changed the root CA's key algorithm, causing incompatibility.
Why it's wrong here
The root CA's key algorithm is unchanged; the intermediate uses a key pair compatible with the root.
- ✗
They did not revoke the old intermediate CA before importing the new one.
Why it's wrong here
Revoking the old intermediate is not required; it can coexist until its expiration.
Common exam traps
Common exam trap: answer the scenario, not the keyword
HashiCorp often tests the specific API workflow of Vault's PKI secrets engine, where candidates confuse the CSR generation and signing process with the final step of importing the signed certificate via `set-signed`, assuming that simply having the signed certificate in the mount path is sufficient.
Detailed technical explanation
How to think about this question
The `pki/intermediate/set-signed` endpoint updates the intermediate mount's internal storage with the signed certificate and its private key reference, enabling Vault to use it for signing leaf certificates. Without this step, the mount's `ca_chain` and `issuer` remain pointing to the old intermediate, so Vault's certificate signing logic cannot find a valid issuer for new requests. In real-world scenarios, this often occurs when automation scripts generate and sign the CSR but forget to call the set-signed API, leading to a silent failure that only manifests when leaf certificate issuance is attempted.
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 small business has 20 workstations on the 192.168.1.0/24 network and one public IP from its ISP. The router uses PAT (NAT overload) so all 20 devices share one public address using different source ports. NAT questions test whether you understand the four address terms and which direction each translation applies.
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.
- →
Compare and configure secrets engines — study guide chapter
Learn the concepts, then practise the questions
- →
Compare and configure secrets engines practice questions
Targeted practice on this topic area only
- →
All VA-003 questions
514 questions across all exam domains
- →
HashiCorp Vault Associate VA-003 study guide
Full concept coverage aligned to exam objectives
- →
VA-003 practice test guide
How to use practice tests most effectively before exam day
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.
Compare authentication methods practice questions
Practise VA-003 questions linked to Compare authentication methods.
Assess Vault tokens practice questions
Practise VA-003 questions linked to Assess Vault tokens.
Create Vault policies practice questions
Practise VA-003 questions linked to Create Vault policies.
Manage Vault leases practice questions
Practise VA-003 questions linked to Manage Vault leases.
Compare and configure secrets engines practice questions
Practise VA-003 questions linked to Compare and configure secrets engines.
Utilize Vault CLI and API practice questions
Practise VA-003 questions linked to Utilize Vault CLI and API.
Explain Vault architecture practice questions
Practise VA-003 questions linked to Explain Vault architecture.
Explain encryption as a service practice questions
Practise VA-003 questions linked to Explain encryption as a service.
VA-003 fundamentals practice questions
Practise VA-003 questions linked to VA-003 fundamentals.
VA-003 scenario practice questions
Practise VA-003 questions linked to VA-003 scenario.
VA-003 troubleshooting practice questions
Practise VA-003 questions linked to VA-003 troubleshooting.
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: They forgot to set the new intermediate certificate as the issuing CA by writing it to the correct path (e.g., pki/intermediate/set-signed). — In Vault's PKI secrets engine, after the root CA signs a new intermediate certificate, the signed certificate must be explicitly set as the issuing CA for the intermediate's mount. This is done by writing the signed certificate to the `pki/intermediate/set-signed` endpoint. Without this step, the intermediate mount still references the old (expiring) certificate, causing new certificate requests to fail with 'no valid intermediate CA found' because Vault cannot locate a valid issuing certificate for signing operations.
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 →
Last reviewed: Jun 30, 2026
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.