What is a key consideration when recovering a failed Cisco Spaces Connector cluster member to minimize service disruption?

All cluster members must be restarted simultaneously to ensure consistency.

The cluster must be recreated with a new cluster name to avoid conflicts.

The failed member should be brought back online and allowed to rejoin the cluster without disrupting other members.

The failed member must be reinstalled from scratch before rejoining the cluster.

A healthcare provider runs a two-node Cisco Spaces Connector cluster. The cluster status shows Node A as 'Active' and Node B as 'Standby', but Node B's status is 'Error' and the service is not running. The admin needs to restore Node B to service without affecting Node A. Which recovery action should be taken?

Restart the connector service on Node B and verify it rejoins the cluster

Renew the certificates on both nodes

Reboot Node A to force a failover to Node B

Remove Node B from the cluster and re-add it

A hospital runs a CMX HA pair. The HA status dashboard shows both nodes as 'Active' (split-brain). The admin needs to determine which node has the most recent data before deciding which to keep as active. Which source of information should be used to make this determination?

The node with the most free disk space

The timestamps of the last location data received on each node

The node that was originally configured as primary

The node with the higher IP address

What is a typical symptom of a service state inconsistency in a Cisco Spaces Connector cluster?

One cluster member reports a different software version than the others.

All cluster members show the same status in the dashboard.

One cluster member is marked as active while another is also marked as active.

One cluster member shows as 'down' while the others show as 'up' in the cluster status.

Which command or interface is used to verify the high availability status of a CMX pair?

The 'show redundancy' command on the wireless controller

The 'show cmx ha status' CLI command

The CMX Admin UI's High Availability page

The 'show cluster status' command in the CMX CLI

CiscoCertified Network Professional Enterprise Wireless (ENWLSI)

Domain 5Objective 4

5.4 Troubleshoot CMX and Cisco Spaces Connector High Availability 300-430 Practice Questions (Page 3)

Part of the Advanced Location Services domain, which accounts for 10% of the 300-430 exam. Cisco does not publish an official question count, but from its 90-minute exam (~35–60 total, ~4–6 in this domain), expect 1–1 from this objective — we provide 33 practice questions to prepare you well beyond it. (estimate)

33questions here

7free pages

6concepts

10%of the exam

Questions 11–15

11foundation · easy
What is a key consideration when recovering a failed Cisco Spaces Connector cluster member to minimize service disruption?
Select an answer first
12application · medium
A healthcare provider runs a two-node Cisco Spaces Connector cluster. The cluster status shows Node A as 'Active' and Node B as 'Standby', but Node B's status is 'Error' and the service is not running. The admin needs to restore Node B to service without affecting Node A. Which recovery action should be taken?
Select an answer first
13expert · hard
A hospital runs a CMX HA pair. The HA status dashboard shows both nodes as 'Active' (split-brain). The admin needs to determine which node has the most recent data before deciding which to keep as active. Which source of information should be used to make this determination?
Select an answer first
14foundation · easy
What is a typical symptom of a service state inconsistency in a Cisco Spaces Connector cluster?
Select an answer first
15foundation · easy
Which command or interface is used to verify the high availability status of a CMX pair?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to 300-430

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by Cisco. “300-430” is a trademark of its owner, used for identification only.