You administer several Microsoft SQL Server 2016 database servers. Merge replication has been configured for an application that is distributed across offices
throughout a wide area network (WAN). Many of the tables involved in replication use the XML and varchar (max) data types. Occasionally, merge replication fails due to timeout errors. You need to reduce the occurrence of these timeout errors.
What should you do?
A . Set the Merge agent on the problem subscribers to use the slow link agent profile.
B . Create a snapshot publication, and reconfigure the problem subscribers to use the snapshot publication.
C . Change the Merge agent on the problem subscribers to run continuously.
D . Set the Remote Connection Timeout on the Publisher to 0.
Answer: A
Explanation:
You might have different profiles for different instances of an agent. For example, a Merge Agent that connects to the Publisher and Distributor over a dialup connection could use a set of parameters that are better suited to the slower communications link by using the slow link profile.
Note: When replication is configured, a set of agent profiles is installed on the Distributor. An agent profile contains a set of parameters that are used each time an agent runs: each agent logs in to the Distributor during its startup process and queries for the parameters in its profile.
References: https://docs.microsoft.com/en-us/sql/relationaldatabases/replication/agents/replication-agent-profiles