Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

HashiCorp Exam Vault-Associate Topic 2 Question 36 Discussion

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

What are orphan tokens?

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:

Annabelle
5 days ago
Orphan tokens are tokens with no policies attached.
upvoted 0 times
...
Cornell
11 days ago
I thought orphan tokens were those that don't expire when their parent does, which might be option B. It seems like a tricky concept!
upvoted 0 times
...
Owen
16 days ago
I feel like I came across a question about tokens and their expiration in practice, but I can't recall if orphan tokens are supposed to expire or not.
upvoted 0 times
...
Theodora
22 days ago
I remember studying that orphan tokens have no policies attached, which makes them quite flexible. That sounds like option C to me.
upvoted 0 times
...
Bulah
28 days ago
I think orphan tokens are related to how they function independently from their parent tokens, but I'm not entirely sure if that means they don't expire.
upvoted 0 times
...
Colette
28 days ago
Ah, I know this one! Orphan tokens are tokens that have no policies attached to them. So option C is the correct answer. These tokens are essentially "orphaned" from any policies or expiration rules.
upvoted 0 times
...
Veronika
28 days ago
Hmm, this is an interesting question. I remember learning about orphan tokens, but I can't quite recall the exact definition. Let me think this through... Ah, I think option B is the right answer - orphan tokens are not children of their parent, so they don't expire when the parent does.
upvoted 0 times
...
Chana
28 days ago
Okay, this question is asking about the definition of orphan tokens. Based on the options, it seems like orphan tokens are tokens that are not tied to a parent token, so they don't expire when the parent does. I'm pretty sure option B is the correct answer.
upvoted 0 times
...
Brendan
1 months ago
I'm not entirely sure what orphan tokens are, but I think it has something to do with tokens that don't expire when their parent does. I'll need to review the material on tokens and policies to be more confident in my answer.
upvoted 0 times
...
Theodora
6 months ago
Forget about orphan tokens, I'm more interested in adopting some stray blockchain transactions.
upvoted 0 times
...
Thaddeus
6 months ago
Option A is clearly the winner here. Tokens with a use limit? That's the definition of an orphan token if I've ever heard one.
upvoted 0 times
Jenise
5 months ago
Exactly, it helps control how and when the tokens are used.
upvoted 0 times
...
Mose
5 months ago
That makes sense, it's like they have a set expiration date based on their usage.
upvoted 0 times
...
Harris
5 months ago
I think orphan tokens are tokens with a use limit, so you can set the number of uses when you create them.
upvoted 0 times
...
...
Teddy
6 months ago
D is my pick. Orphan tokens that don't expire when their own TTL is reached. Seems like the most logical choice.
upvoted 0 times
Renea
5 months ago
Orphan tokens are not children of their parent; therefore, they do not expire when their parent does.
upvoted 0 times
...
Rima
5 months ago
I believe orphan tokens are tokens that don't expire when their own TTL is reached.
upvoted 0 times
...
Una
6 months ago
I think orphan tokens are tokens with no policies attached.
upvoted 0 times
...
...
Kattie
6 months ago
I'm torn between B and C. Orphan tokens not expiring with their parent or having no policies sounds plausible.
upvoted 0 times
Frederick
5 months ago
Maybe orphan tokens have both characteristics, not expiring with their parent and having no policies.
upvoted 0 times
...
Lenna
6 months ago
But orphan tokens with no policies attached also sounds like a possibility.
upvoted 0 times
...
Dana
6 months ago
I think orphan tokens not expiring with their parent makes sense.
upvoted 0 times
...
...
Wynell
7 months ago
Option C sounds like the right answer. Orphan tokens without any policies attached makes sense.
upvoted 0 times
Tien
5 months ago
Exactly. Orphan tokens do not expire when their max TTL is reached.
upvoted 0 times
...
Rusty
6 months ago
So, they don't expire when their own max TTL is reached?
upvoted 0 times
...
Francesco
6 months ago
Yeah, that makes sense. They can be more flexible that way.
upvoted 0 times
...
Rosamond
6 months ago
I think orphan tokens without policies attached are the way to go.
upvoted 0 times
...
Antione
6 months ago
Yes, that's correct. Orphan tokens do not have any policies attached to them.
upvoted 0 times
...
Merilyn
6 months ago
I think orphan tokens are tokens with no policies attached.
upvoted 0 times
...
...
Yuette
7 months ago
I believe orphan tokens do not expire when their own max TTL is reached.
upvoted 0 times
...
Noble
7 months ago
I think orphan tokens are not children of their parent; therefore, orphan tokens do not expire when their parent does.
upvoted 0 times
...
Natalie
7 months ago
Orphan tokens are tokens with a use limit so you can set the number of uses when you create them.
upvoted 0 times
...

Save Cancel