You've set up multiple Vault clusters, one on-premises which is intended to be the primary cluster, and the second cluster in AWS, which was deployed to be used for performance replication. After enabling replication, developers complain that all the data they've stored in the AWS Vault cluster is missing. What happened?

• A.the data was moved to a recovery path after replication was enabled. Use the vault secrets move command to move the data back to its intended location
• B.there is a certificate mismatch after replication was enabled since Vault replication generates its own TLS certificates to ensure nodes are trusted entities
• C.the data was automatically copied to the primary cluster after replication was enabled since all writes are always forwarded to the primary cluster
• D.all of the data on the secondary cluster was deleted after replication was enabled

Comment: *

Name: *

Email: *

Verification: *

Your organization has moved to AWS and has manually deployed infrastructure using the console. Recently, a decision has been made to standardize on Terraform for all deployments moving forward.
What can you do to ensure that all existing is managed by Terraform moving forward without interruption to existing services?

• A.resources that are manually deployed in the AWS console cannot be imported by Terraform
• B.using terraform import, import the existing infrastructure into your Terraform state
• C.delete the existing resources and recreate them using new a Terraform configuration so Terraform can manage them moving forward
• D.submit a ticket to AWS and ask them to export the state of all existing resources and use terraform import to import them into the state file

Comment: *

Name: *

Email: *

Verification: *

Which Terraform command will force a marked resource to be destroyed and recreated on the next apply?

• A.terraform fmt
• B.terraform destroy
• C.terraform taint
• D.terraform refresh

Comment: *

Name: *

Email: *

Verification: *

You've deployed Vault in your production environment and are curious to understand metrics on your Vault cluster, such as the number of writes to the backend, the status of WALs, and the seal status. What feature would you configure in order to view these metrics?

• A.audit device
• B.telemetry
• C.nothing to configure, these are available in the Vault log found on the OS
• D.enable logs for each individual secrets engines

Comment: *

Name: *

Email: *

Verification: *

Which of the following best describes the storage backend?

• A.configures client interaction with a cloud storage service, such as Amazon S3
• B.configures the location for storage of Vault data
• C.selects the type of storage the Vault node runs on, such as SSD or traditional spinning hard drive
• D.Encrypts the hard drives of the server which Vault is running on

Comment: *

Name: *

Email: *

Verification: *