An administrator is promoting a secondary Vault Enterprise cluster to primary. The secondary is in a different region and has a higher latency to the primary. The promotion succeeds, but clients in the original primary's region are experiencing slow responses. What is the most likely cause?

Clients are now connecting to a cluster in a different region, increasing network latency

The replication status is incorrect, causing routing issues

The promoted cluster is sealed, causing authentication delays

The promoted cluster is not fully synced, causing data retrieval delays

A Vault Enterprise environment has a primary in DC1 and a secondary in DC2. The DC1 primary is decommissioned, and the secondary is promoted to primary. Later, the team wants to bring DC1 back as a secondary. What must be done?

Promote DC1 back to primary using the API

Demote DC1 from primary to secondary using the API

Restore DC1 from a backup and configure it as a secondary

Reinstall Vault on DC1 and configure it as a secondary to the new primary

A Vault Enterprise secondary cluster is being considered for promotion to primary. The team wants to ensure that no data is lost during the promotion. What condition must be met before promoting?

The secondary must have a valid Enterprise license and be unsealed

The primary must be sealed to prevent writes during promotion

The secondary must be fully synced with the primary (replication lag is zero)

The primary must be demoted before promoting the secondary

After promoting a secondary Vault Enterprise cluster to primary, the administrator notices that clients are unable to authenticate. The replication status shows the cluster as primary. What should the administrator check next?

Promote the cluster again to ensure the promotion completed

Restart the cluster to reset the replication state

Check the replication status on the old primary

Verify that the cluster is unsealed and the auth methods are enabled

A Vault Enterprise environment has a primary in DC1 and a secondary in DC2. The DC1 primary is experiencing intermittent network issues. The team decides to promote the secondary in DC2 to primary to ensure availability. After promotion, the DC1 cluster comes back online and attempts to rejoin as a secondary. What is the correct behavior?

The DC1 cluster will remain as a primary and cause a split-brain scenario

The DC1 cluster must be manually demoted to secondary and then rejoin the new primary

The DC1 cluster will automatically become a secondary and sync with the new primary

The DC1 cluster will be ignored by the new primary and remain isolated

HashiCorp Certified:Vault Operations Professional

Domain 4Objective 3

[ Vault Enterprise] Promote a Secondary Cluster VAULT-OPERATIONS-PROFESSIONAL Practice Questions (Page 2)

Part of the Build fault-tolerant Vault environments domain, which makes up ~10% of our current practice bank. HashiCorp does not publish an official question count, but from its 240-minute exam (~95–160 total, ~10–16 in this domain), expect 3–5 from this objective — we provide 16 practice questions to prepare you well beyond it. (estimate)

16questions here

4free pages

4concepts

Questions 6–10

6expert · hard
An administrator is promoting a secondary Vault Enterprise cluster to primary. The secondary is in a different region and has a higher latency to the primary. The promotion succeeds, but clients in the original primary's region are experiencing slow responses. What is the most likely cause?
Select an answer first
7application · medium
A Vault Enterprise environment has a primary in DC1 and a secondary in DC2. The DC1 primary is decommissioned, and the secondary is promoted to primary. Later, the team wants to bring DC1 back as a secondary. What must be done?
Select an answer first
8application · medium
A Vault Enterprise secondary cluster is being considered for promotion to primary. The team wants to ensure that no data is lost during the promotion. What condition must be met before promoting?
Select an answer first
9application · medium
After promoting a secondary Vault Enterprise cluster to primary, the administrator notices that clients are unable to authenticate. The replication status shows the cluster as primary. What should the administrator check next?
Select an answer first
10expert · hard
A Vault Enterprise environment has a primary in DC1 and a secondary in DC2. The DC1 primary is experiencing intermittent network issues. The team decides to promote the secondary in DC2 to primary to ensure availability. After promotion, the DC1 cluster comes back online and attempts to rejoin as a secondary. What is the correct behavior?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to VAULT-OPERATIONS-PROFESSIONAL

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by HashiCorp. “VAULT-OPERATIONS-PROFESSIONAL” is a trademark of its owner, used for identification only.