You have an on-premises SAP NetWeaver deployment. The deployment has a DB2 data store that contains a 5-TB SAP database. You plan to migrate the deployment to SQL Server on an Azure virtual machine…

Question

Options

• APlace the transaction logs on the temporary disk.
• BPlace the transaction logs on a striped volume of Premium SSD disks.
• CPlace the transaction logs on an Ultra disk.
• DEnable the write cache for the disk that hosts the transaction logs.

• A
  18% (9)
• B
  66% (33)
• C
  10% (5)
• D
  6% (3)

Explanation

Placing transaction logs on a striped volume of Premium SSD disks (B) is correct because striping aggregates IOPS and throughput across multiple disks, maximizing sequential write performance for transaction logs-and since no host caching is used (caching is disabled for transaction logs per best practice), it does not consume the VM's cached I/O bandwidth quota.

Why the distractors fail:

• (A) Temporary disk - The temp disk is ephemeral; data is lost on VM resize, restart, or redeployment, making it completely unsuitable for transaction logs regardless of performance.
• (C) Ultra disk - While Ultra disks offer excellent IOPS, they do consume the VM's I/O quota and require specific VM size support, directly violating the constraint.
• (D) Write cache - SQL Server's write-ahead logging requires durability guarantees; enabling write cache on transaction log disks risks data corruption on failure, and it routes I/O through the Azure host cache, consuming the VM's cached I/O quota.

Memory tip: "Stripe the logs, never cache them" - Striped Premium SSDs give you throughput without touching the host cache quota, while write caching on transaction logs is both dangerous and quota-consuming. Think of it as more disks, no cache, no risk.

No community discussion yet for this question.