A root FortiGate and its downstream FortiGate are members of the same Security Fabric. The administrator needs an object created on the root, such as an address group, to be usable in policies on the downstream device without recreating it manually. Which fabric capability satisfies this requirement?
- APolicy package installation, where the downstream FortiGate pulls the root's entire firewall policy table on a schedule.
- BLog forwarding, which copies the object definitions to FortiAnalyzer so the downstream can import them from logs.
- CSD-WAN rule replication, which distributes the root's path-selection rules and any referenced objects to members.
- DFabric synchronisation of selected objects, so the root can share configuration objects like addresses with downstream members. Correct
Why A is wrong: Pulling a full policy package describes FortiManager-style management, not native fabric object sharing; the requirement is to reuse a single object, not to overwrite the downstream policy table.
Why B is wrong: Log forwarding moves event data to FortiAnalyzer for analytics; logs do not carry reusable configuration objects, so the downstream cannot build an address group from forwarded logs.
Why C is wrong: SD-WAN rules govern path selection on a single device and are not the mechanism for sharing a generic address object across the fabric, so this misapplies an unrelated feature.
Why D is correct: The Security Fabric can synchronise certain configuration objects from the root to downstream members, letting an address group defined once on the root be referenced in downstream policies without manual recreation.