Which problem with the dispatcher flush agent is causing this issue?

New content is not visible on the website when accessing it via the dispatcher.

– Replication from author to publish works fine

– Dispatcher flush agent is present under /etc/replication/agents.author on the Publish instance, and enabled

– The checkbox for Dispatcher flush agent configuration is ticked for enabled, when reviewed on the author instance

– Rules in the dispatcher configuration are correct

Which problem with the dispatcher flush agent is causing this issue?
A . It does not have enough permissions to receive the activation.
B . It is not configured properly in the dispatcher configuration.
C . It is configured properly but uses the incorrect transport user.
D . It is configured properly but located in the wrong path.

View Answer

Answer: D

Explanation:

problem here lies in the description of the question: if a dispatcher flush agent is present under /etc/replication/agents.author on the publish instance, then this will never work, because it needs it in /etc/replication/agents.publish, so if the description is correct then the answer must be D, if the description is not correct and the flush agent is installed on the author, then A might be correct, but it is not according to best practices to have your flush agent installed on author. See for that even a question further down that states exactly that, where should a flush agent be configured?