Question 770
In this retired AZ-500 educational case, A security owner wants to hide credit card data in a database but stores the original values in query logs despite masking the display. Which security principle BEST explains the appropriate response?
Explanation
Correct Answer
The relevant security principle is: Presentation masking alone does not prevent exposure through logging and diagnostics. That is why the action is: Remove sensitive values from logs and apply appropriate column protection and application data handling. The directly relevant confirmation is: A controlled transaction produces redacted logs and the authorized app still processes the protected field.
Incorrect Answers
“Kubernetes workload egress can create risk even when the API server is not publicly exposed” reflects the mechanism: Kubernetes workload egress can create risk even when the API server is not publicly exposed. The actual reported symptoms are better explained by: Presentation masking alone does not prevent exposure through logging and diagnostics.
This alternative is valid when ephemeral containers still create runtime and image exposure independent of short deployment lifetime. The facts here establish a different controlling reason: Presentation masking alone does not prevent exposure through logging and diagnostics.
“Data access should reflect precise blob type, resource path, and allowed operations” reflects the mechanism: Data access should reflect precise blob type, resource path, and allowed operations. The actual reported symptoms are better explained by: Presentation masking alone does not prevent exposure through logging and diagnostics.