Question 350
In this retired AZ-500 educational case, An Azure Function needs a private resource but its hosting plan does not support the chosen integration configuration. Which security principle BEST explains the appropriate response?
Explanation
Correct Answer
The relevant security principle is: Function network integration capabilities depend on the deployed hosting plan and feature support. That is why the action is: Select an eligible supported hosting or networking configuration and validate function outbound reachability. The directly relevant confirmation is: The function calls the private target from the authorized network without opening public access.
Incorrect Answers
The offered principle describes: DNAT exposes internal services to public reachability, independently from outbound filtering. The situation in this question instead depends on: Function network integration capabilities depend on the deployed hosting plan and feature support. These are different technical conditions.
This alternative is valid when edge WAF coverage can be bypassed when clients reach an unprotected origin directly. The facts here establish a different controlling reason: Function network integration capabilities depend on the deployed hosting plan and feature support.
“VNet peering provides private connectivity but some transit and gateway behaviors require explicit compatible flags” reflects the mechanism: VNet peering provides private connectivity but some transit and gateway behaviors require explicit compatible flags. The actual reported symptoms are better explained by: Function network integration capabilities depend on the deployed hosting plan and feature support.