Why might an address object not be available on the downstream FortiGate after synchronization?

The correct answer emphasizes the importance of synchronization settings in available objects across FortiGate devices. If synchronization settings are not configured correctly, it could prevent certain objects from being shared between the primary and downstream FortiGate devices. Effective synchronization requires that both devices are set up to recognize and replicate policies and configurations, including address objects.

In a scenario where the parameters for synchronization are misconfigured—such as incorrect settings for what types of objects to synchronize or erroneous connection settings—it can lead to a failure in making specific address objects visible on the downstream device.

Other options, while they present valid reasons why an object may not appear, do not directly address the overarching mechanism of synchronization settings. For instance, conflicts with existing objects may arise post-synchronization, but if the settings were correct, resolution could perhaps still be achieved. Marking an object for export or designating it as temporary may also prevent it from being available on the downstream device, yet both these involve procedural choices rather than a configuration oversight related to synchronization itself. Thus, misconfigured synchronization settings directly account for the object's absence despite being created or modified in the primary configuration.