Objective 2.11 Explain How to Troubleshoot and Verify Sync Group Mesh 302 Practice Questions (Page 1)

Questions 1–5

1. 1expert · hard

   A BIG-IP DNS sync group has four devices. Device A and Device B are in sync, but Device C and Device D show 'Changes Pending' and cannot sync. The administrator notices that Device C and Device D were recently reconfigured with a different management IP address. All devices can ping each other on their management interfaces. What is the most likely cause of the sync failure?

   • AThe device trust certificates are invalid because the management IP change invalidated the certificate.
   • BThe data collection group is not configured on Device C and Device D.
   • CThe devices are in a different administrative partition, preventing sync.
   • DThe sync group configuration on Device C and Device D still references the old management IP addresses of the other devices.
   Reveal Solution Discussion Select an answer first
2. 2foundation · easy

   Which issue is a common cause of sync group mesh failures in BIG-IP DNS?

   • AToo many wide IPs configured
   • BIncorrect time zone on the devices
   • CMissing DNS records for the sync group name
   • DMismatched device certificates
   Reveal Solution Discussion Select an answer first
4. 3foundation · easy

   Which statement accurately describes the architecture of a BIG-IP DNS sync group?

   • ADevices synchronize only with their immediate neighbor in a ring topology
   • BA single device acts as the central repository for all configuration data
   • CEach device in the sync group maintains a direct synchronization connection to every other device
   • DAll devices in the sync group must be in the same data center
   Reveal Solution Discussion Select an answer first
5. 4foundation · easy

   Which GUI tool is used to monitor the sync status of a BIG-IP DNS sync group?

   • ANetwork > Interfaces
   • BDevice Management > Sync Status
   • CDNS > Zones
   • DLocal Traffic > Virtual Servers
   Reveal Solution Discussion Select an answer first
6. 5application · medium

   A company has a BIG-IP DNS sync group with three devices in a full mesh. After adding a fourth device and running tmsh show cm sync-status, the administrator sees that the new device shows 'Pending' while the original three show 'In Sync'. The new device's management IP is reachable from all other devices, and the admin can log in to it with the shared admin account. What should the administrator do first to resolve the issue?

   • ARun tmsh run cm config-sync to force a manual sync from the new device.
   • BVerify that the new device's device certificate is trusted by the other group members and that the trust domain is consistent.
   • CCheck the /var/log/ltm log on the new device for authentication failures from the other devices.
   • DReboot the new device to ensure it picks up the mesh configuration from the group.
   Reveal Solution Discussion Select an answer first