You work as a Database Administrator (DBA) for a company named ABC.com. The company uses a Microsoft SQL Server 2012 infrastructure. You have a database named CorpDB. CorpDB contains 2TB of data…

The Full recovery model logs every transaction in detail, including every row inserted during a bulk import, which would maximize, not minimize, the transaction log size.

The Bulk-Logged recovery model minimizes transaction log usage for large-scale operations like data imports by only logging the metadata of the bulk operations and extent allocations, rather than every individual row insertion. This significantly reduces the amount of data written to the transaction log compared to the Full recovery model, thereby keeping the log size smaller during the import process.

Starting a new transaction log file does not alter the logging behavior of bulk operations and will not reduce the overall amount of data written to the log, thus failing to minimize its size.

Transaction log files are not assigned to filegroups; filegroups are used for organizing data files, making this option irrelevant to managing transaction log size.