Question 100
A controlled pilot has deployed: Configure supported wildcard-FQDN ZTNA Connector targets with controlled name resolution. The issue was: A branch uses private app wildcard FQDNs but the engineer specifies only one fixed IP target for all subdomains. What should the technical signoff show?
Explanation
Correct Answer
The strongest proof is that new approved subdomain endpoints resolve and connect without broad IP-subnet exposure. It confirms the intended effect of the change (Configure supported wildcard-FQDN ZTNA Connector targets with controlled name resolution) in response to a branch uses private app wildcard FQDNs but the engineer specifies only one fixed IP target for all subdomains. The validation should include both permitted and restricted flow wherever relevant.
Incorrect Answers
The option applies in “an architect wants a global colocation interconnect but assumes a private on-ramp and off-ramp are interchangeable”. A successful configuration deployment alone would not establish this test result. That evidence does not directly establish “New approved subdomain endpoints resolve and connect without broad IP-subnet exposure” for the scenario at hand.
This can be appropriate when a private app uses unsupported NAT-sensitive IP semantics and a planned ZTNA Connector SNATs traffic, but it does not isolate the distinguishing requirement here: A branch uses private app wildcard FQDNs but the engineer specifies only one fixed IP target for all subdomains. The correct acceptance decision is new approved subdomain endpoints resolve and connect without broad IP-subnet exposure.
That alternative belongs to the case: Two subsidiaries use overlapping 10.20.0.0/16 addresses for different private HR apps after a merger. It is not sufficient evidence or remediation for a branch uses private app wildcard FQDNs but the engineer specifies only one fixed IP target for all subdomains. The case-specific choice is new approved subdomain endpoints resolve and connect without broad IP-subnet exposure.