You plan to automate a deployment of SAP NetWeave on Azure virtual machines by using Azure Resource Manager templates. The database tier will consist of two instances of an Azure Marketplace…

Question

Options

• AEnable buffer pool extensions in SQL Server.
• BEnable read caching on the disks used to store the SQL Server database log
• CRun the SQL Server setup and specify the /ACTION=REBUILDDATABASE and
• DRun the SQL Server setup and specify the /ACTION-INSTALL and

• A
  5% (1)
• B
  5% (1)
• C
  14% (3)
• D
  77% (17)

Explanation

Option D is correct because deploying SQL Server for SAP NetWeaver requires running SQL Server setup with /ACTION=INSTALL and SAP-specific parameters (collation, features, service accounts) during the ARM template automation - the Marketplace image provides the binaries, but the installation must be configured to meet SAP's requirements.

Why the distractors are wrong:

• A is wrong because buffer pool extensions exist to supplement limited RAM using fast SSD storage - with 8 TB of RAM, the entire working set fits in memory, making this feature irrelevant and wasteful.
• B is wrong because enabling read caching on transaction log disks is a known anti-pattern - log writes are strictly sequential and there is nothing to read-cache; enabling it adds overhead without benefit and can risk data integrity.
• C is wrong because /ACTION=REBUILDDATABASE is a repair/maintenance command used to rebuild corrupted or miscollated system databases on an existing installation, not the correct action for a fresh deployment.

Memory tip: Associate the RAM size with the trap - "8 TB of RAM" is there to lure you toward buffer pool extensions (A), which only matter when RAM is scarce. For any new SQL Server deployment in an automated template, always think INSTALL first, REBUILD only to fix.

No community discussion yet for this question.