How would you answer an interview scenario involving Kubernetes ConfigMaps and Secrets?

For an interview scenario involving Kubernetes ConfigMaps and Secrets, I would first clarify the business goal, scale, constraints, and the failure or quality attribute the interviewer wants to explore. ConfigMaps store non-sensitive configuration while Secrets hold sensitive values for workloads. In this scenario, an application currently stores database passwords in deployment YAML. Explain how you would redesign secret storage and access. I would then explain the main alternatives and tradeoffs, identify likely failure modes, and describe how I would validate the solution through testing, observability, security controls, and recovery or rollback planning.