500-440 · Question #66
In a Cisco Finesse 10.0(x) deployment, primary and secondary nodes can be installed on separate domains. Which two requirements must be met for the pair to work properly? (Choose two.)
The correct answer is A. Each Cisco Finesse server should be able to perform DNS lookup of the other server using fully C. All Cisco Finesse clients should be able to perform DNS lookups of the Cisco Finesse servers. DNS Resolution is the Core Requirement When Cisco Finesse primary and secondary nodes reside on separate domains, proper DNS resolution becomes critical for both server-to-server and client-to-server communication. Option A is correct because each Finesse server must resolve…
Question
In a Cisco Finesse 10.0(x) deployment, primary and secondary nodes can be installed on separate domains. Which two requirements must be met for the pair to work properly? (Choose two.)
Options
- AEach Cisco Finesse server should be able to perform DNS lookup of the other server using fully
- BPrimary and secondary Cisco Finesse servers should only communicate with IP address.
- CAll Cisco Finesse clients should be able to perform DNS lookups of the Cisco Finesse servers
- DAll Cisco Finesse clients should connect to the server with IP address.
- EAll Cisco Finesse clients should be local to the Cisco Finesse servers.
How the community answered
(26 responses)- A88% (23)
- D8% (2)
- E4% (1)
Explanation
DNS Resolution is the Core Requirement
When Cisco Finesse primary and secondary nodes reside on separate domains, proper DNS resolution becomes critical for both server-to-server and client-to-server communication. Option A is correct because each Finesse server must resolve the other's fully qualified domain name (FQDN) to establish and maintain the HA (high availability) pair relationship - without this, the nodes cannot communicate across domain boundaries. Option C is correct because Finesse clients (agent desktops) connect to the Finesse server by hostname/FQDN, so DNS lookup failure from the client side means the agent desktop simply cannot reach the server.
Why the distractors are wrong:
- B is incorrect - Finesse servers are designed to communicate via FQDN, not raw IP addresses; hardcoding IPs breaks certificate validation and is not a supported configuration.
- D is incorrect - clients connecting by IP address bypasses DNS but breaks SSL/TLS certificate hostname matching and is not how Finesse clients are designed to operate.
- E is incorrect - Finesse supports remote/geographically distributed clients; locality is not a requirement.
Memory tip: Think "DNS both ways" - the servers need to find each other (A), and the clients need to find the servers (C). If either direction of DNS resolution breaks, the deployment fails. Any answer suggesting IP-only communication (B, D) contradicts how Finesse's certificate-based architecture works.
Topics
Community Discussion
No community discussion yet for this question.