Q: 8
What will cause a connector to fail to establish a connection with the cloud gateway during the
deployment of a new ZTNA Connector in a data center?
Options
Discussion
B . Double NAT is the real blocker here since it can prevent establishing any session at all. A is tempting but DNS misconfig typically throws a different error, not just failure to connect. Seen similar on other exam reports, always B.
Option B. Don't think it's A, DNS misconfig just blocks name resolution not the connection setup.
B tbh. Double NAT will block session setup for ZTNA connectors, while DNS issues usually just cause lookup delays or errors but don't always stop initial connection cold. Seen similar Qs on practice, B's the trapbreaker. Disagree?
B or A, but B is the definite blocker. Double NAT breaks session setup, DNS issues usually just delay connection.
I don’t think it’s B. A.
Misconfigured DNS (A) seems like the main culprit in my experience. Without proper DNS, the connector can't even resolve where to connect, so no chance for the session to start. Not 100 percent, but A looks like a real blocker here. Agree?
A , because if the connector can't resolve the cloud gateway due to DNS issues, it won't even try to connect. Double NAT is nasty for ongoing sessions, but DNS misconfig seems like a total blocker right at startup. Not sure, but feels like A also makes sense.
Hard to say, B. Double NAT breaks the session with the cloud gateway, so the connector can't ever establish the connection at all.
Wouldn't a DNS misconfiguration (A) also block the connector from ever reaching the cloud gateway in the first place? If it can't resolve the destination, connection setup should fail outright, not just be unreliable. Double NAT is definitely tricky, but is DNS really just a red herring here?
Double NAT is a classic issue here, not just DNS or dynamic IP. Saw something like this in other exam dumps, pretty sure B is what they're going for but some could get tricked by A.
Be respectful. No spam.
