101 · Question #707
A BIG-IP Administrator has a cluster of devices. What should the administrator do after creating a new Virtual Server on device 1?
The correct answer is A. synchronize the settings of device 1 to the group. In a BIG-IP Device Service Clustering (DSC) group, after changing configuration on one device the administrator must sync that device's config outward to the group so all peers receive the update.
Question
A BIG-IP Administrator has a cluster of devices. What should the administrator do after creating a new Virtual Server on device 1?
Options
- Asynchronize the settings of device 1 to the group
- Bcreate a new cluster on device 1
- Ccreate the new virtual server on device 2
- Dsynchronize the settings of the group to device 1
How the community answered
(31 responses)- A90% (28)
- B3% (1)
- C6% (2)
Why each option
In a BIG-IP Device Service Clustering (DSC) group, after changing configuration on one device the administrator must sync that device's config outward to the group so all peers receive the update.
BIG-IP DSC synchronization pushes the local configuration from the modified device (device 1) to all other members of the sync group, replicating the new Virtual Server across the cluster consistently and without manual recreation on each peer.
Creating a new cluster is unnecessary because a sync group already exists; DSC replicates changes through synchronization, not by forming additional clusters.
Manually creating the Virtual Server on device 2 is redundant and error-prone; DSC synchronization is the correct and authoritative mechanism for propagating configuration changes.
Syncing from the group to device 1 would overwrite device 1's current configuration with the group's older state, deleting the newly created Virtual Server.
Concept tested: BIG-IP DSC device group configuration synchronization
Source: https://techdocs.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/bigip-device-service-clustering-administration-13-1-0.html
Topics
Community Discussion
7
Carlos M.May 10, 2026A is correct. When you add a Virtual Server on one device in a BIG-IP cluster, you sync device 1 to the group so all other members pick up the change, not the other way around.
Lena V.Apr 28, 2026A is right. After making a config change on the active device, you sync device-to-group so the updated virtual server definition pushes out to all peers in the sync-failover device group, keeping the cluster consistent.
Toby R.Apr 28, 2026Just to add, the sync step also updates the config-sync status so you can confirm all devices in the group show "In Sync" before you trust the change is fully propagated.
Mei-Ling H.Apr 22, 2026Option D is the trap here because "group to device 1" sounds like you are pushing the latest config out, but that direction overwrites what you just built on device 1, which is the opposite of what you want. After you create the virtual server on device 1, you push device 1 outward to the group, so A is correct.
Toby R.Apr 25, 2026Exactly right, and the "sync direction" wording on that question tripped up a lot of people in my testing group too, so if you see "propagate" in the answer choices that is usually the giveaway that the config is flowing from the source device outward.
Toby R.May 3, 2026D all day, you push the group config down to overwrite device 1.
Mei-Ling H.May 6, 2026Toby, actually A is correct here because the device-level config takes precedence over the group config in that hierarchy, so pushing the group config down does not overwrite device 1 without first clearing the device-level override. D would work only if there were no device-specific settings already in place, which the question does not say.