nerdexam
Microsoft

70-465 · Question #114

You have a SQL Server 2012 database named DB1. You have a backup device named Device1. You discover that the log file for the database is full. You need to ensure that DB1 can complete transactions…

The correct answer is B. BACKUP LOG DB1 TO Device1. To resolve a full transaction log and allow new transactions without breaking the log sequence number (LSN) chain, a standard transaction log backup is required.

Submitted by ashley.k· Mar 5, 2026Design and implement database solutions for SQL Server

Question

You have a SQL Server 2012 database named DB1. You have a backup device named Device1. You discover that the log file for the database is full. You need to ensure that DB1 can complete transactions. The solution must not affect the chain of log sequence numbers (LSNs). Which code segment should you execute?

Options

  • ABACKUP LCG DB1 TO Device1 WITH COPY_ONLY
  • BBACKUP LOG DB1 TO Device1
  • CBACKUP LOG DB1 TO Device1 WITH NCRECCVERY
  • DBACKUP LOG D31 TO Device1 WITH TRUNCATE ONLY

How the community answered

(35 responses)
  • A
    3% (1)
  • B
    77% (27)
  • C
    14% (5)
  • D
    6% (2)

Why each option

To resolve a full transaction log and allow new transactions without breaking the log sequence number (LSN) chain, a standard transaction log backup is required.

ABACKUP LCG DB1 TO Device1 WITH COPY_ONLY

The `LCG` keyword is not a valid backup type in SQL Server; the correct keyword for backing up the transaction log is `LOG`.

BBACKUP LOG DB1 TO Device1Correct

Executing `BACKUP LOG DB1 TO Device1` performs a regular transaction log backup. This action automatically truncates the inactive portion of the transaction log, freeing up space for new transactions, while critically maintaining the log sequence number (LSN) chain essential for recovery.

CBACKUP LOG DB1 TO Device1 WITH NCRECCVERY

The `NCRECCVERY` option is not a valid parameter for the `BACKUP LOG` command in SQL Server.

DBACKUP LOG D31 TO Device1 WITH TRUNCATE ONLY

The `TRUNCATE_ONLY` option for `BACKUP LOG` was deprecated in SQL Server 2008 and removed in SQL Server 2012, making this command invalid for the specified version, and it would break the log chain.

Concept tested: SQL Server transaction log backup and management

Source: https://learn.microsoft.com/en-us/sql/t-sql/statements/backup-transact-sql

Topics

#Transaction log backup#Log Sequence Number (LSN)#Log full

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full 70-465 Practice