nerdexam
Microsoft

70-465 · Question #61

What should you recommend for the updates to Sales.TransactionHistory?

The correct answer is A. Datum has limited storage. Whenever possible, all storage space should be minimized for all. When storage is limited and minimization is the priority, batch updates using minimal logging or choosing storage-efficient data types and transaction approaches is the correct strategy. The question context points to minimizing storage overhead for transaction operations.

Submitted by katya_ua· Mar 5, 2026Design and implement database solutions for SQL Server

Question

What should you recommend for the updates to Sales.TransactionHistory?

Exhibit

70-465 question #61 exhibit

Options

  • ADatum has limited storage. Whenever possible, all storage space should be minimized for all
  • Bimplicit transactions
  • Cquery hints
  • Da SNAPSHOT isolation level

How the community answered

(15 responses)
  • A
    93% (14)
  • B
    7% (1)

Why each option

When storage is limited and minimization is the priority, batch updates using minimal logging or choosing storage-efficient data types and transaction approaches is the correct strategy. The question context points to minimizing storage overhead for transaction operations.

ADatum has limited storage. Whenever possible, all storage space should be minimized for allCorrect

When storage is constrained, minimizing storage space for all operations - including transaction log usage - is the recommended approach for updates to a high-volume table like Sales.TransactionHistory. This involves strategies such as using minimal logging, appropriate data types, and batch processing to reduce log file growth and overall storage consumption. Prioritizing storage efficiency aligns with the stated constraint that Datum has limited storage.

Bimplicit transactions

Implicit transactions automatically wrap each DML statement in its own transaction, which can actually increase transaction log usage and overhead rather than minimizing storage space.

Cquery hints

Query hints influence query execution plans for performance optimization purposes and do not directly address storage minimization for transactional data.

Da SNAPSHOT isolation level

SNAPSHOT isolation level stores row versions in tempdb to provide read consistency without locking, which increases storage consumption rather than minimizing it, making it counterproductive in a storage-constrained environment.

Concept tested: Storage optimization strategies for SQL Server transactions

Source: https://learn.microsoft.com/en-us/sql/relational-databases/sql-server-transaction-log-architecture-and-management-guide

Topics

#Storage optimization#Data archiving#Data types

Community Discussion

No community discussion yet for this question.

Full 70-465 Practice