How does BIG-IP APM handle Access Policy Sync to ensure consistency across HA devices?

Question

Options

• AIt synchronizes access policies globally for all virtual servers.
• BIt requires manual configuration for local objects on each device.
• CIt synchronizes access policies locally within each traffic group.
• DIt uses DNS-based synchronization for global policy settings.

• B
  2% (1)
• C
  93% (42)
• D
  4% (2)

Explanation

BIG-IP APM synchronizes access policies within the scope of a traffic group, not globally across all virtual servers or devices. In an HA pair, each traffic group maintains its own policy state, so only devices sharing that traffic group receive synchronized access policies - this ensures consistent session handling for traffic managed by that group without bleeding into unrelated traffic groups.

Why the distractors are wrong:

• A is wrong because synchronization is scoped to a traffic group, not applied globally to all virtual servers across the entire BIG-IP fleet.
• B is wrong because APM does synchronize automatically within a traffic group - manual per-device configuration is not required for that shared scope (though local objects like certificates may need individual attention).
• D is wrong because APM uses device trust and config sync mechanisms, not DNS, to propagate policy settings.

Memory tip: Think "traffic group = policy group." APM policy sync follows the same boundary as traffic group membership - if two devices share a traffic group, they share the policy. DNS has nothing to do with it; it's all internal sync infrastructure.

No community discussion yet for this question.