Try each one before opening the answer. Every option is explained, with the HashiCorp documentation page that proves it.
Question 1 · choose 1
A bank must auto-unseal Vault with its own on-premises HSM and use seal wrapping to meet FIPS 140 requirements. The security team accepts running the cluster itself. Which deployment meets these requirements?
ASelf-managed Vault Enterprise using the bank's HSM as its seal
BHCP Vault Dedicated configured with the bank's HSM as its seal
CSelf-managed Vault Community Edition with the pkcs11 seal
DHCP Vault Dedicated with its managed KMS auto-unseal and seal wrap
Show the answer and why
ASelf-managed Vault Enterprise using the bank's HSM as its seal
Correct
HSM auto-unseal and seal wrapping are Vault Enterprise features available when you run the cluster.
BHCP Vault Dedicated configured with the bank's HSM as its seal
Incorrect
HashiCorp manages the seal on HCP Vault Dedicated, and HSM auto-unseal is not offered there.
CSelf-managed Vault Community Edition with the pkcs11 seal
Incorrect
The pkcs11 seal and seal wrapping require Vault Enterprise.
DHCP Vault Dedicated with its managed KMS auto-unseal and seal wrap
Incorrect
HCP Vault Dedicated does not offer FIPS 140-2 seal wrap.
On HCP Vault Dedicated HashiCorp manages the seal, and a few features, such as HSM auto-unseal and FIPS seal wrap, remain self-managed only.
On a self-managed cluster, an operator can seal Vault to stop access during an incident. On HCP Vault Dedicated, which control blocks most Vault API endpoints in the admin namespace while the cluster keeps running?
ANamespace API lock on the admin namespace and its children
Bvault operator seal, run with the HCP admin token
CDisabling the cluster's public endpoint in the HCP Portal
DA paths filter that excludes the admin namespace
Show the answer and why
ANamespace API lock on the admin namespace and its children
Correct
Namespace API lock blocks most API endpoints in the admin namespace and its descendants; HCP offers it where the cluster seal used to be.
Bvault operator seal, run with the HCP admin token
Incorrect
Most authenticated sys endpoints, sealing included, are not available on HCP Vault Dedicated.
CDisabling the cluster's public endpoint in the HCP Portal
Incorrect
That removes only the public address; clients on private networks could still reach the cluster.
DA paths filter that excludes the admin namespace
Incorrect
A paths filter blocks no API requests, so the admin namespace would stay reachable.
HCP Vault Dedicated replaces the cluster seal control with namespace API lock and keeps only a few authenticated sys endpoints, such as sys/leader and sys/metrics, available.