Vault has failed to start. You inspect the log and find the error below. What needs to be changed in order to successfully start Vault?
"Error parsing config.hcl: At 1:12: illegal char"

• A.the " character cannot be used in the config file
• B.fix the syntax error in the Vault configuration file
• C.you must use single quotes vs double quotes in the config file
• D.line 1 on the config file is blank

Comment: *

Name: *

Email: *

Verification: *

A Vault client who has read access to the path secrets/apps/app1 is having trouble viewing the secret in the user interface (UI) but can access via the API. What can be done to resolve this issue?

• A.add read permissions to the path secrets/apps
• B.modify the policy to allow the create permission
• C.remove the deny policy blocking access to the secrets/apps/app1 path
• D.add LIST to the policy so the user can browse the paths leading up to the key/value's path

Comment: *

Name: *

Email: *

Verification: *

When creating a dynamic secret in Vault, Vault returns what value that can be used to renew or revoke the lease?

• A.lease_id
• B.vault_accessor
• C.revocation_access
• D.token_revocation_id

Comment: *

Name: *

Email: *

Verification: *

After running into issues with Terraform, you need to enable verbose logging to assist with troubleshooting the error. Which of the following values provides the MOST verbose logging?

• A.ERROR
• B.INFO
• C.DEBUG
• D.WARN
• E.TRACE

Comment: *

Name: *

Email: *

Verification: *

Which is not a benefit of running HashiCorp Vault in your environment?

• A.Integrate with your code repository to pull secrets when deploying your applications
• B.Consolidate static, long-lived passwords used throughout your organization
• C.Act as root or intermediate certificate authority to automate the generation of PKI certificates
• D.The ability to generate dynamic secrets for applications and resource access

Comment: *

Name: *

Email: *

Verification: *