Pass the HashiCorp Security Automation Certification HCVA0-003 Questions and answers with Dumpstech

The missing capability is update. In Vault ACL policies, read allows a client to retrieve data from a path, but it does not allow changing the data at that path. To modify an existing value, the policy must grant update capability. The list capability only allows listing keys or path entries; it does not read or modify secret values. The delete capability removes data, but it is not needed to change an existing value. The sudo capability is reserved for root-protected paths and administrative operations, not normal secret modification. Since the role can already read the secret, option E is already present and cannot be the missing permission. HashiCorp’s policy documentation states that update allows changing data at a path, while read only allows reading data.

================

To create a new user named “sally” with password “h0wN0wB4r0wnC0w” and the power-users policy, you would use the Vault userpass auth method mounted at auth/userpass. You would use the following command: “vault write auth/userpass/users/sally password=h0wN0wB4r0wnC0w policies=power-users”. This command would create a new user named “sally” with the specified password and policy.  References :

[Userpass Auth Method | Vault | HashiCorp Developer]

[Create Vault policies | Vault | HashiCorp Developer]

The statement is false. The Vault encryption key is not stored in Vault’s backend storage, but rather in Vault’s memory. The Vault encryption key is the key that is used to encrypt and decrypt the data that is stored in Vault’s backend storage, such as secrets, tokens, policies, etc. The Vault encryption key is derived from the master key, which is generated when Vault is initialized. The master key is split into unseal keys using Shamir’s secret sharing algorithm, and the unseal keys are distributed to trusted operators. To start Vault, a quorum of unseal keys is required to reconstruct the master key and derive the encryption key. The encryption key is then kept in memory and used to protect the data in Vault’s backend storage. The encryption key is never written to disk or exposed via the API. References:  Seal/Unseal | Vault | HashiCorp Developer ,  Key Rotation | Vault | HashiCorp Developer

Orphan tokens are tokens that are root of their own token tree. This means that they do not have any parent token associated with them, and they do not expire when their parent token expires. Orphan tokens are useful for scenarios where you need a short-lived and independent token, such as for testing or debugging purposes. Orphan tokens can also be used to create temporary access tokens for applications or services that need to communicate with Vault without using a long-lived root token. References:  Tokens | Vault | HashiCorp Developer ,  Vault cli: how to create orphan token with role - HashiCorp Discuss

The statement is true. When an auth method is disabled, all users authenticated via that method lose access. This is because the tokens issued by the auth method are automatically revoked when the auth method is disabled. This prevents the users from performing any operation in Vault using the revoked tokens. To regain access, the users have to authenticate again using a different auth method that is enabled and has the appropriate policies attached. References:  Auth Methods | Vault | HashiCorp Developer ,  auth disable - Command | Vault | HashiCorp Developer

Not all storage backends support high availability mode for Vault. Only the storage backends that support locking can enable Vault to run in a multi-server mode where one server is active and the others are standby. Some examples of storage backends that support high availability mode are Consul, Integrated Storage, and ZooKeeper.  Some examples of storage backends that do not support high availability mode are Filesystem, MySQL, and PostgreSQL.  References: https://developer.hashicorp.com/vault/docs/concepts/ha 1 , https://developer.hashicorp.com/vault/docs/configuration/storage 2

The Vault UI hides or denies access to sections that the current token cannot use. ACL policy management is controlled by Vault policies, usually through access to policy-related system paths. If the authenticated token does not have the required permissions to list, read, create, or update policies, the UI will not expose the ACL Policies menu as expected. There is no separate “policy engine” that must be enabled; policies are a core Vault authorization mechanism. Option C is also incorrect because the issue is not solved by moving to a “policy namespace” unless the token has the required permissions in that namespace. The exhibit behavior is a permissions problem. HashiCorp documents that Vault access is controlled by policies and that unauthorized paths evaluate to deny.

================

This screenshot is shown when you are enabling authentication methods in the GUI. Authentication methods are the ways users and applications authenticate with Vault. Vault supports many different authentication methods, including username and password, GitHub, and more. You can enable one or more authentication methods from the grid of options, which are divided into three categories: Generic, Cloud, and Infra. Each option has a name, a description, and a logo. You can also enable authentication methods using the Vault CLI or API.

Enabling policies, authentication engines, and secret engines are different tasks that are not related to this screenshot. Policies are rules that govern the access to Vault resources, such as secrets, authentication methods, and audit devices. Authentication engines are components of Vault that perform authentication and assign policies to authenticated entities. Secret engines are components of Vault that store, generate, or encrypt data. These tasks have different GUI pages and options than the screenshot.

For a very large object, the correct pattern is envelope encryption using a data key. Vault Transit can generate a high-entropy data key, return it to the client, and protect that data key with the named Transit key. The application then encrypts the 2GB blob locally using the plaintext data key and stores the encrypted blob outside Vault. Later, the protected data key can be decrypted or used according to the workflow so the application can decrypt the blob locally. Vault should not permanently store the blob, and it should not temporarily place a 2GB payload into its storage backend. Transit does not store submitted data, and Vault’s HTTP API has a request-size limit, so large-object encryption should be handled through data keys.

================

This is a templated ACL policy using {{identity.entity.id}}. The template dynamically resolves to the authenticated entity’s unique Vault identity ID. Because the paths are under secret/data/ and secret/metadata/, this is written for a KV version 2 secrets engine, where data and metadata are addressed separately. The policy grants each entity create, update, read, and delete permissions under its own data path, plus list permission under its own metadata path. That means every user or client mapped to a Vault entity receives access to a folder matching its entity ID, without requiring a manually written policy for each person. This is not a special system entity folder; it is identity-based path templating. HashiCorp documents ACL templating for user-specific KV paths.

================