An open-data portal needs an opaque Secret from literal values in a demo Namespace so the app is not baked with passwords in the image. What is the admin's responsibility?
Select an answer to reveal the explanation.
Short Explanation
Images should stay password-free—like shipping a safe without writing the combination on the cardboard. Admins create Secrets (often opaque from literals) and point the app at them.
Full Explanation
Cluster administrators create Secret objects that Pods reference for credentials, avoiding baking secrets into images. Disabling the API server, printing passwords on consoles, or stuffing credentials into RBAC rule fields are not valid Secret provisioning practices.