Question 1110
After implementing the design, the architecture team must validate: Two private application environments use the same DNS name in different internal domains. What observed evidence best establishes the intended state?
Explanation
Correct Answer
Authorized users resolve each intended backend without cross-tenant collisions. It validates the recommended action: Design distinct resolution scopes, connector definitions or approved namespace separation for each private environment. The design principle is: A name alone may be ambiguous when split-horizon DNS domains overlap across enterprises.
Incorrect Answers
A valid service hostname passes while neighbor hosts on the same subnet are denied. That observation supports a DIFFERENT situation: An organization defines a broad ZTNA connector subnet to avoid managing application hostnames, creating lateral exposure. Here the selected design is: Design distinct resolution scopes, connector definitions or approved namespace separation for each private environment.
Authorized access continues when the service resolves to its new permitted IP. That observation supports a DIFFERENT situation: A private application uses a unique DNS hostname but the service's IP changes behind its load balancer. Here the selected design is: Design distinct resolution scopes, connector definitions or approved namespace separation for each private environment.
A private app resolves to intended internal service connectivity without a public ingress rule. That observation supports a DIFFERENT situation: Users can authenticate to a managed enterprise browser but a private application still routes through a public Internet address. Here the selected design is: Design distinct resolution scopes, connector definitions or approved namespace separation for each private environment.