Question 370
In a controlled acceptance test for a telecom operator, the original issue is: A team proposes a wildcard allow for all applications from a vendor instead of the one approved API. Which result proves the desired architecture?
Explanation
Correct Answer
Only intended API requests pass while unrelated vendor applications remain blocked. It validates the recommended action: Define precise application and destination controls for the approved vendor service, not vendor-wide trust. The design principle is: A common service provider does not imply equal security authorization for all hosted apps.
Incorrect Answers
Calls and screen sharing succeed with app-specific rule hits while other applications on the same ports remain denied. That observation supports a DIFFERENT situation: A video collaboration tool loses access when a policy migrates from port-based rules to App-ID controls. Here the selected design is: Define precise application and destination controls for the approved vendor service, not vendor-wide trust.
Test transactions match the custom application rule without granting unrelated unknown-TCP sessions. That observation supports a DIFFERENT situation: An internal custom protocol lacks a usable predefined App-ID and matches a broad unknown-TCP rule. Here the selected design is: Define precise application and destination controls for the approved vendor service, not vendor-wide trust.
Primary and failover routes both generate expected allow-or-deny observations at the inspection point. That observation supports a DIFFERENT situation: A service-mesh microsegment policy exists but an alternate transit path bypasses its firewall. Here the selected design is: Define precise application and destination controls for the approved vendor service, not vendor-wide trust.