Question 480
A legacy internal TCP service uses a non-HTTP protocol and cannot be published through a browser-focused application proxy; employees need it without a full VPN. What is the most appropriate implementation step?
Explanation
Correct Answer
Private Access supports scoped private TCP connectivity beyond browser HTTP publishing. Client flow and segment logs verify TCP-specific routing. A specific check is: An authorized client connects to the named private port while unrelated internal ports remain inaccessible.
Incorrect Answers
This addresses a different requirement: An organization wants two private apps with different access policies, not one broad Quick Access route. Per-app segmentation avoids granting network-wide access from one broad policy.
This addresses a different requirement: A branch has Microsoft traffic routed but private application traffic still follows the legacy VPN. Microsoft service forwarding and private access forwarding are independent profile configurations.
This addresses a different requirement: Remote Windows users need identity-aware access to an internal TCP application without full network VPN exposure. Private Access enables per-app Zero Trust connectivity to eligible private network resources.