Question 540
Following the issue — A Container Apps environment permits privileged application secrets in plain configuration variables visible to routine operators. — the team takes this action: Move secrets into approved secret references or managed identity-controlled services with scoped access. Which continuing safeguard BEST prevents the same control weakness from returning?
Explanation
Correct Answer
The recurring safeguard is: Scan container deployment manifests for embedded credentials and unsafe role grants. This mitigates the control weakness because: Container configuration and operator privileges affect exposure of sensitive runtime secrets. Keep the intervention, Move secrets into approved secret references or managed identity-controlled services with scoped access., in the approved deployment, monitoring and change governance process.
Incorrect Answers
This safeguard is for the dependency described by: Client-side column encryption depends on driver capabilities in addition to server schema. The continuing risk here is determined by: Container configuration and operator privileges affect exposure of sensitive runtime secrets. The targeted safeguard is “Scan container deployment manifests for embedded credentials and unsafe role grants”.
That review protects the control associated with: Versioning preserves prior object versions according to configured service capabilities and retention. It does not directly prevent the stated recurrence, which concerns: Container configuration and operator privileges affect exposure of sensitive runtime secrets. The appropriate guardrail is “Scan container deployment manifests for embedded credentials and unsafe role grants”.
This safeguard is for the dependency described by: Dynamic masking is not a comprehensive confidentiality boundary against arbitrary query inference. The continuing risk here is determined by: Container configuration and operator privileges affect exposure of sensitive runtime secrets. The targeted safeguard is “Scan container deployment manifests for embedded credentials and unsafe role grants”.