What can be done to resolve this issue?

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

View Answer

Answer: D

Explanation:

To view the paths leading up to the secrets/apps/app1 path in the user interface, the user must have at least LIST permissions to avoid permission denied error in the UI.