You administer all the deployments of Microsoft SQL Server 2016 in your company.
A database contains a large product catalog that is updated periodically.
You need to be able to send the entire product catalog to all branch offices on a monthly basis.
Which configuration should you use?
A . Two servers configured in the same data center A primary server configured to perform log-shipping every 10 minutes A backup server configured as a warm standby
B . SQL Server that includes an application database configured to perform transactional replication
C . Two servers configured in the same data center SQL Server Availability Group configured in AsynchronousCommit Availability Mode One server configured as an Active Secondary
D . Two servers configured in a Windows Failover Cluster in the same data center SQL Server configured as a clustered instance
E . SQL Server that includes an application database configured to perform snapshot replication
F . Two servers configured in different data centers SQL Server Availability Group configured in Synchronous-Commit Availability Mode One server configured as an Active Secondary
G . Two servers configured on the same subnet SQL Server Availability Group configured in Synchronous-Commit Availability Mode
H . Two servers configured in different data centers SQL Server Availability Group configured in AsynchronousCommit Availability Mode
Answer: E
Explanation:
Snapshot replication distributes data exactly as it appears at a specific moment in time and does not monitor for updates to the data. When synchronization occurs, the entire snapshot is generated and sent to Subscribers.
Using snapshot replication by itself is most appropriate when one or more of the following is true:
– Data changes infrequently.
– It is acceptable to have copies of data that are out of date with respect to the Publisher for a period of time.
– Replicating small volumes of data.
A large volume of changes occurs over a short period of time.
References: https://docs.microsoft.com/en-us/sql/relational-databases/replication/snapshot-replication