Question 510
In this retired AZ-500 educational case, An AKS operator assumes selecting a private cluster automatically restricts every pod-to-pod communication path. Which security principle BEST explains the appropriate response?
Explanation
Correct Answer
The relevant security principle is: AKS private control-plane access and pod data-plane policy are separate security boundaries. That is why the action is: Implement a supported network policy for required namespace and workload segmentation. The directly relevant confirmation is: A permitted application tier communicates but a prohibited lateral pod connection fails.
Incorrect Answers
This alternative is valid when client-side cryptography depends on coordinated keys, metadata and compatible application drivers. The facts here establish a different controlling reason: AKS private control-plane access and pod data-plane policy are separate security boundaries.
“Presentation masking alone does not prevent exposure through logging and diagnostics” reflects the mechanism: Presentation masking alone does not prevent exposure through logging and diagnostics. The actual reported symptoms are better explained by: AKS private control-plane access and pod data-plane policy are separate security boundaries.
The offered principle describes: Management-plane storage roles and blob data access permissions are distinct authorization surfaces. The situation in this question instead depends on: AKS private control-plane access and pod data-plane policy are separate security boundaries. These are different technical conditions.