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 HCVA0-003 Topic 7 Question 2 Discussion

Actual exam question for HashiCorp's HCVA0-003 exam
Question #: 2
Topic #: 7
[All HCVA0-003 Questions]

As a best practice, the root token should be stored in which of the following ways?

Show Suggested Answer Hide Answer
Suggested Answer: A

The root token is the initial token created when initializing Vault. It has unlimited privileges and can perform any operation in Vault. As a best practice, the root token should be revoked and never stored after initial setup. This is because the root token is a single point of failure and a potential security risk if it is compromised or leaked. Instead of using the root token, Vault operators should create other tokens with appropriate policies and roles that allow them to perform their tasks. If a new root token is needed in an emergency, the vault operator generate-root command can be used to create one on-the-fly with the consent of a quorum of unseal key holders. Reference: Tokens | Vault | HashiCorp Developer, Generate root tokens using unseal keys | Vault | HashiCorp Developer


Contribute your Thoughts:

Annamaria
28 days ago
D all the way! Vault is practically a requirement these days. If you're not using it, you're doing it wrong.
upvoted 0 times
...
Dorethea
30 days ago
I dunno, man. Shouldn't we just delete the root token and start fresh? A seems like the safest bet to me.
upvoted 0 times
Terina
9 days ago
C) Should be stored in another password safe
upvoted 0 times
...
Lashawnda
12 days ago
Yeah, that's the best practice. We should delete it and not store it.
upvoted 0 times
...
Daren
13 days ago
A) Should be revoked and never stored after initial setup
upvoted 0 times
...
...
Tamesha
1 months ago
I'd go with D. Vault is the industry standard for this kind of thing. Anything else is just asking for trouble.
upvoted 0 times
Michel
3 days ago
I think storing it in another password safe could also work.
upvoted 0 times
...
Jamie
5 days ago
I agree, storing it in Vault is the safest option.
upvoted 0 times
...
...
Billye
2 months ago
B seems like a reasonable option too. As long as the config tooling is properly secured, it could work.
upvoted 0 times
Orville
1 months ago
D) Should be stored in Vault
upvoted 0 times
...
Melvin
1 months ago
C) Should be stored in another password safe
upvoted 0 times
...
Armanda
1 months ago
B) Should be stored in configuration automation tooling
upvoted 0 times
...
...
Dwight
2 months ago
I believe it should be stored in another password safe for added security.
upvoted 0 times
...
Carrol
2 months ago
I agree with Sang, storing it in Vault provides secure access control.
upvoted 0 times
...
Sang
2 months ago
I think the root token should be stored in Vault.
upvoted 0 times
...
Anthony
2 months ago
Definitely D. Vault is the way to go for secure storage of sensitive tokens.
upvoted 0 times
Blair
17 days ago
Vault provides a secure way to manage and store sensitive tokens like the root token.
upvoted 0 times
...
Lawana
18 days ago
I always make sure to follow best practices when it comes to storing sensitive information.
upvoted 0 times
...
Lashawnda
24 days ago
It's important to keep sensitive tokens like the root token in a secure location.
upvoted 0 times
...
Joesph
27 days ago
I agree, storing the root token in Vault is the most secure option.
upvoted 0 times
...
Nadine
1 months ago
Vault provides a secure way to manage and store sensitive tokens like the root token.
upvoted 0 times
...
Luz
1 months ago
I always make sure to follow best practices when it comes to storing sensitive information.
upvoted 0 times
...
Dorinda
2 months ago
It's important to keep sensitive tokens like the root token in a secure location.
upvoted 0 times
...
Brittni
2 months ago
I agree, storing the root token in Vault is the most secure option.
upvoted 0 times
...
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77