New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

HashiCorp Vault-Associate Exam - Topic 1 Question 3 Discussion

Actual exam question for HashiCorp's Vault-Associate exam
Question #: 3
Topic #: 1
[All Vault-Associate Questions]

An organization would like to use a scheduler to track & revoke access granted to a job (by Vault) at completion. What auth-associated Vault object should be tracked to enable this behavior?

Show Suggested Answer Hide Answer
Suggested Answer: C

A lease ID is a unique identifier that is assigned by Vault to every dynamic secret and service type authentication token. A lease ID contains information such as the secret path, the secret version, the secret type, etc. A lease ID can be used to track and revoke access granted to a job by Vault at completion, as it allows the scheduler to perform the following operations:

Lookup the lease information by using the vault lease lookup command or the sys/leases/lookup API endpoint. This will return the metadata of the lease, such as the expire time, the issue time, the renewable status, and the TTL.

Renew the lease if needed by using the vault lease renew command or the sys/leases/renew API endpoint. This will extend the validity of the secret or the token for a specified increment, or reset the TTL to the original value if no increment is given.

Revoke the lease when the job is completed by using the vault lease revoke command or the sys/leases/revoke API endpoint. This will invalidate the secret or the token immediately and prevent any further renewals. For example, with the AWS secrets engine, the access keys will be deleted from AWS the moment a lease is revoked.

A lease ID is different from a token ID or a token accessor. A token ID is the actual value of the token that is used to authenticate to Vault and perform requests. A token ID should be treated as a secret and protected from unauthorized access. A token accessor is a secondary identifier of the token that is used for token management without revealing the token ID. A token accessor can be used to lookup, renew, or revoke a token, but not to authenticate to Vault or access secrets. A token ID or a token accessor can be used to revoke the token itself, but not the leases associated with the token. To revoke the leases, a lease ID is required.

An authentication method is a way to verify the identity of a user or a machine and issue a token with appropriate policies and metadata. An authentication method is not an object that can be tracked or revoked, but a configuration that can be enabled, disabled, tuned, or customized by using the vault auth commands or the sys/auth API endpoints.


Contribute your Thoughts:

0/2000 characters
Elbert
3 months ago
Authentication method doesn't fit this scenario at all.
upvoted 0 times
...
Micaela
3 months ago
Wait, are we sure Lease ID is the correct answer? Seems a bit off.
upvoted 0 times
...
Vannessa
4 months ago
I thought it was Token ID at first, but Lease ID is definitely right.
upvoted 0 times
...
Tamekia
4 months ago
Totally agree, Lease ID makes the most sense here.
upvoted 0 times
...
Maybelle
4 months ago
Lease ID is the one to track for revocation.
upvoted 0 times
...
Franchesca
4 months ago
I’m leaning towards Lease ID as well, since it’s tied to the lifecycle of the access granted. It just makes sense for revocation.
upvoted 0 times
...
Leah
4 months ago
I feel like the Token ID could be important here, but it seems more related to identifying the token rather than tracking access.
upvoted 0 times
...
Juliann
4 months ago
I remember practicing a question about token accessors, but I can't recall if they are relevant for revoking access after a job completes.
upvoted 0 times
...
Na
5 months ago
I think the Lease ID might be the right answer since it relates to the duration of access, but I'm not entirely sure.
upvoted 0 times
...
Leota
5 months ago
I'm pretty sure the authentication method wouldn't be the right thing to track here. That's more about how the access was granted, not the specific token or lease.
upvoted 0 times
...
Chandra
5 months ago
The lease ID seems like it could work, since that's associated with the auth process. But I'm not totally confident that's the right answer.
upvoted 0 times
...
Vallie
5 months ago
I think the token accessor would be the best option to track, since it's a unique identifier for the token that can be used to revoke access.
upvoted 0 times
...
Ailene
5 months ago
Hmm, I'm not sure about this one. I'm trying to remember the difference between token ID and token accessor. I'll have to think this through a bit more.
upvoted 0 times
...
Shaun
5 months ago
Hmm, the question mentions filtering out a specific prefix, but it's still appearing in the routing tables. I'm wondering if the issue is with the access list configuration.
upvoted 0 times
...
Kendra
5 months ago
I feel like the answer might be "Group," since it relates to managing similar items, but I'm not entirely sure.
upvoted 0 times
...
Dianne
5 months ago
Hmm, security clearances don't seem very relevant for host-based intrusion detection. I'm leaning towards audit trails or access control lists as the best options here.
upvoted 0 times
...
Lennie
5 months ago
Hmm, I'm not sure about the QoS requirement. Does that mean I can ignore it or do I need to consider it somehow?
upvoted 0 times
...
Mari
2 years ago
I can see both sides of the argument here. The Lease ID might be the more straightforward option, but the Token-based approach could provide more flexibility and control. It's a tough call.
upvoted 0 times
Denny
2 years ago
C) Lease ID
upvoted 0 times
...
Anastacia
2 years ago
True, but considering the organization's needs, the Token accessor might be the better choice.
upvoted 0 times
...
Malcolm
2 years ago
A) Token accessor
upvoted 0 times
...
Ling
2 years ago
But tracking the Lease ID might be the more straightforward approach in this situation.
upvoted 0 times
...
Nohemi
2 years ago
C) Lease ID
upvoted 0 times
...
Yong
2 years ago
I agree, tracking the Token accessor would provide more flexibility in managing access.
upvoted 0 times
...
Maxima
2 years ago
A) Token accessor
upvoted 0 times
...
...
Jamie
2 years ago
I agree with Refugia. Tracking the Token accessor or Token ID seems like a more robust approach. Relying on the Lease ID feels a bit too indirect to me.
upvoted 0 times
...
Refugia
2 years ago
I'm not so sure about that. Wouldn't tracking the Token accessor or Token ID be a better way to manage the access? That way, you can revoke the token itself instead of just the lease.
upvoted 0 times
...
Nohemi
2 years ago
Hmm, this is an interesting question. I think the answer is C) Lease ID. Vault uses leases to track access granted to a job, and revoking the lease would effectively revoke the access when the job is completed.
upvoted 0 times
...

Save Cancel