70-765: Provisioning SQL Databases - Free download from ExamHUB

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.

After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.

Your company plans to use Microsoft Azure Resource Manager templates for all future deployments of SQL Server on Azure virtual machines.

You need to create the templates.

Solution: You create the desired SQL Server configuration in an Azure Resource Group, then export the Resource Group template and save it to the Templates Library.

Does the solution meet the goal?

Yes
No

Correct answer: B

Explanation:

Azure Resource Manager template consists of JSON, and expressions that you can use to construct values for your deployment. A good JSON editor, not a Resource Group template, can simplify the task of creating templates. Note: In its simplest structure, an Azure Resource Manager template contains the following elements:{ "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#","contentVersion": "","parameters": { },"variables": { },"resources": [ ],"outputs": { }} References: https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-authoring-templates

Azure Resource Manager template consists of JSON, and expressions that you can use to construct values for your deployment.

A good JSON editor, not a Resource Group template, can simplify the task of creating templates.

Note: In its simplest structure, an Azure Resource Manager template contains the following elements:

{

"$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#",

"contentVersion": "",

"parameters": { },

"variables": { },

"resources": [ ],

"outputs": { }

}

References: https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-authoring-templates

You have a Microsoft SQL Server 2014 named SRV2014 that has a single tempdb database file. The tempdb database file is eight gigabytes (GB) in size.

You install a SQL Server 2016 instance named SQL Server 2016 by using default settings. The new instance has eight logical processor cores.

You plan to migrate the databases from SRV2014 to SRV2016.

You need to configure the tempdb database on SRV2016. The solution must minimize the number of future tempdb autogrowth events.

What should you do?

Increase the size of the tempdb data file to 1 GB. Add seven additional tempdb data files and set the size for each data file to 1 GB.
Increase the size of the tempdb data files to 1 GB.
Add seven additional tempdb data files and set the size for each data file to 1 GB.
Set the value for the autogrowth setting for the tempdb data file to128 megabytes (MB). Add seven additional tempdb data files and set the autogrowth value to 128 MB.

Correct answer: B

Explanation:

In an effort to simplify the tempdb configuration experience, SQL Server 2016 setup has been extended to configure various properties for tempdb for multi-processor environments. 1.A new tab dedicated to tempdb has been added to the Database Engine Configuration step of setup workflow. 2.Configuration options:Data Files Number of files – this will default to the lower value of 8 or number of logical cores as detected by setup. Initial size – is specified in MB and applies to each tempdb data file. This makes it easier to configure all files of same size. Total initial size is the cumulative tempdb data file size (Number of files * Initial Size) that will be created. Autogrowth – is specified in MB (fixed growth is preferred as opposed to a non-linear percentage based growth) and applies to each file. The default value of 64MB was chosen to cover one PFS interval. Figure: References: https://blogs.msdn.microsoft.com/psssql/2016/03/17/sql-2016-it-just-runs-faster-automatic-tempdb-configuration/

In an effort to simplify the tempdb configuration experience, SQL Server 2016 setup has been extended to configure various properties for tempdb for multi-processor environments.

1.A new tab dedicated to tempdb has been added to the Database Engine Configuration step of setup workflow.

2.Configuration options:

Data Files

Number of files – this will default to the lower value of 8 or number of logical cores as detected by setup.
Initial size – is specified in MB and applies to each tempdb data file. This makes it easier to configure all files of same size. Total initial size is the cumulative tempdb data file size (Number of files * Initial Size) that will be created.
Autogrowth – is specified in MB (fixed growth is preferred as opposed to a non-linear percentage based growth) and applies to each file. The default value of 64MB was chosen to cover one PFS interval.

Figure:

References: https://blogs.msdn.microsoft.com/psssql/2016/03/17/sql-2016-it-just-runs-faster-automatic-tempdb-configuration/

Note: This question is part of a series of questions that use the same or similar answer choices. An answer choice may be correct for more than one question in the series. Each question is independent of the other questions in this series. Information and details provided in a question apply only to that question.

You have a virtual machine (VM) in Microsoft Azure, which has a 2 terabyte (TB) database. Microsoft SQL Server backups are performed by using Backup to URL.

You need to provision the storage account for the backups while minimizing costs.

Which storage option should you use?

Premium P10 disk storage
Premium P20 disk storage
Premium P30 disk storage
Standard locally redundant disk storage
Standard geo-redundant disk storage
Standard zone redundant blob storage
Standard locally redundant blob storage
Standard geo-redundant blob storage

Correct answer: G

Explanation:

A URL specifies a Uniform Resource Identifier (URI) to a unique backup file. The URL is used to provide the location and name of the SQL Server backup file. The URL must point to an actual blob, not just a container. If the blob does not exist, it is created. If an existing blob is specified, BACKUP fails, unless the “WITH FORMAT” option is specified to overwrite the existing backup file in the blob. LOCALLY REDUNDANT STORAGE (LRS) makes multiple synchronous copies of your data within a single datacenter. Incorrect Answers:F: Zone redundant blob storage would be me more expensive as it stores three copies of data across multiple datacenters within or across regions.References:https://msdn.microsoft.com/en-us/library/dn435916.aspxhttps://azure.microsoft.com/en-us/pricing/details/storage/blobs/

A URL specifies a Uniform Resource Identifier (URI) to a unique backup file. The URL is used to provide the location and name of the SQL Server backup file. The URL must point to an actual blob, not just a container. If the blob does not exist, it is created. If an existing blob is specified, BACKUP fails, unless the “WITH FORMAT” option is specified to overwrite the existing backup file in the blob.

LOCALLY REDUNDANT STORAGE (LRS) makes multiple synchronous copies of your data within a single datacenter.

Incorrect Answers:

F: Zone redundant blob storage would be me more expensive as it stores three copies of data across multiple datacenters within or across regions.

References:

https://msdn.microsoft.com/en-us/library/dn435916.aspx

https://azure.microsoft.com/en-us/pricing/details/storage/blobs/

Note: This question is part of a series of questions that use the same or similar answer choices. An answer choice may be correct for more than one question in the series. Each question is independent of the other questions in this series. Information and details provided in a question apply only to that question.

You have deployed a GS-series virtual machine (VM) in Microsoft Azure. You plan to deploy Microsoft SQL Server.

You need to deploy a 30 megabyte (MB) database that requires 100 IOPS to be guaranteed while minimizing costs.

Which storage option should you use?

Premium P10 disk storage
Premium P20 disk storage
Premium P30 disk storage
Standard locally redundant disk storage
Standard geo-redundant disk storage
Standard zone redundant blob storage
Standard locally redundant blob storage
Standard geo-redundant blob storage

Correct answer: A

Explanation:

Premium Storage Disks Limits When you provision a disk against a Premium Storage account, how much input/output operations per second (IOPS) and throughput (bandwidth) it can get depends on the size of the disk. Currently, there are three types of Premium Storage disks: P10, P20, and P30. Each one has specific limits for IOPS and throughput as specified in the following table: References: https://docs.microsoft.com/en-us/azure/storage/storage-premium-storage

Premium Storage Disks Limits

When you provision a disk against a Premium Storage account, how much input/output operations per second (IOPS) and throughput (bandwidth) it can get depends on the size of the disk. Currently, there are three types of Premium Storage disks: P10, P20, and P30. Each one has specific limits for IOPS and throughput as specified in the following table:

References: https://docs.microsoft.com/en-us/azure/storage/storage-premium-storage

Note: This question is part of a series of questions that use the same or similar answer choices. An answer choice may be correct for more than one question in the series. Each question is independent of the other questions in this series. Information and details provided in a question apply only to that question.

You have deployed several GS-series virtual machines (VMs) in Microsoft Azure. You plan to deploy Microsoft SQL Server in a development environment.

You need to provide storage to the environment that minimizes costs.

Which storage option should you use?

Premium P10 disk storage
Premium P20 disk storage
Premium P30 disk storage
Standard locally redundant disk storage
Standard geo-redundant disk storage
Standard zone redundant blob storage
Standard locally redundant blob storage
Standard geo-redundant blob storage

Correct answer: D

You plan to migrate a database to Microsoft Azure SQL Database. The database requires 500 gigabytes (GB) of storage.

The database must support 50 concurrent logins. You must minimize the cost associated with hosting the database.

You need to create the database.

Which pricing tier should you use?

Standard S3 pricing tier
Premium P2 tier
Standard S2 pricing tier
Premium P1 tier

Correct answer: D

Explanation:

For a database size of 500 GB the Premium tier is required. Both P1 and P2 are adequate. P1 is preferred as it is cheaper. Note: Incorrect Answers:A, C: Maximum database size is 250 GB for the Standard pricing tier.References: https://docs.microsoft.com/en-us/azure/sql-database/sql-database-service-tiers

For a database size of 500 GB the Premium tier is required.

Both P1 and P2 are adequate. P1 is preferred as it is cheaper.

Note:

Incorrect Answers:

A, C: Maximum database size is 250 GB for the Standard pricing tier.

References: https://docs.microsoft.com/en-us/azure/sql-database/sql-database-service-tiers

You plan to deploy 20 Microsoft Azure SQL Database instances to an elastic pool in Azure to support a batch processing application.

Two of the databases in the pool reach their peak workload threshold at the same time every day. This leads to inconsistent performance for batch completion.

You need to ensure that all batches perform consistently.

What should you do?

Create an In-Memory table.
Increase the storage limit in the pool.
Implement a readable secondary database.
Increase the total number of elastic Database Transaction Units (eDTUs) in the pool.

Correct answer: D

Explanation:

In SQL Database, the relative measure of a database's ability to handle resource demands is expressed in Database Transaction Units (DTUs) for single databases and elastic DTUs (eDTUs) for databases in an elastic pool. A pool is given a set number of eDTUs, for a set price. Within the pool, individual databases are given the flexibility to auto-scale within set parameters. Under heavy load, a database can consume more eDTUs to meet demand. Additional eDTUs can be added to an existing pool with no database downtime. References: https://docs.microsoft.com/en-us/azure/sql-database/sql-database-elastic-pool

In SQL Database, the relative measure of a database's ability to handle resource demands is expressed in Database Transaction Units (DTUs) for single databases and elastic DTUs (eDTUs) for databases in an elastic pool.

A pool is given a set number of eDTUs, for a set price. Within the pool, individual databases are given the flexibility to auto-scale within set parameters. Under heavy load, a database can consume more eDTUs to meet demand.

Additional eDTUs can be added to an existing pool with no database downtime.

References: https://docs.microsoft.com/en-us/azure/sql-database/sql-database-elastic-pool

A company has an on-premises Microsoft SQL Server 2014 environment. The company has a main office in Seattle, and remote offices in Amsterdam and Tokyo. You plan to deploy a Microsoft Azure SQL Database instance to support a new application. You expect to have 100 users from each office.

In the past, users at remote sites reported issues when they used applications hosted at the Seattle office.

You need to optimize performance for users running reports while minimizing costs.

What should you do?

Implement an elastic pool.
Implement a standard database with readable secondaries in Asia and Europe, and then migrate the application.
Implement replication from an on-premises SQL Server database to the Azure SQL Database instance.
Deploy a database from the Premium service tier.

Correct answer: B

Explanation:

References: https://docs.microsoft.com/en-us/azure/sql-database/sql-database-geo-replication-transact-sql#add-secondary-database

You administer all the deployments of Microsoft SQL Server 2012 in your company. You have two servers in the same data center that hosts your production database.

You need to ensure that the database remains available if a catastrophic server failure or a disk failure occurs.

You also need to maintain transactional consistency of the data across both servers.

You need to achieve these goals without manual intervention.

Which configuration should you use?

Two servers configured in a Windows Failover Cluster in the same data center SQL Server configured as a clustered instance
SQL Server that includes an application database configured to perform transactional replication
Two servers configured in the same data centerA primary server configured to perform log-shipping every 10 minutes A backup server configured as a warm standby
Two servers configured in different data centersSQL Server Availability Group configured in Synchronous-Commit Availability Mode One server configured as an Active Secondary
Two servers configured in the same data centerSQL Server Availability Group configured in Asynchronous-Commit Availability Mode One server configured as an Active Secondary
Two servers configured in different data centersSQL Server Availability Group configured in Asynchronous-Commit Availability Mode
SQL Server that includes an application database configured to perform snapshot replication
Two servers configured on the same subnetSQL Server Availability Group configured in Synchronous-Commit Availability Mode

Correct answer: H

Explanation:

Always On availability groups supports two availability modes—asynchronous-commit mode and synchronous-commit mode Synchronous-commit mode emphasizes high availability over performance, at the cost of increased transaction latency. References: https://docs.microsoft.com/en-us/sql/database-engine/availability-groups/windows/availability-modes-always-on-availability-groups#SyncCommitAvMode

Always On availability groups supports two availability modes—asynchronous-commit mode and synchronous-commit mode

Synchronous-commit mode emphasizes high availability over performance, at the cost of increased transaction latency.

References: https://docs.microsoft.com/en-us/sql/database-engine/availability-groups/windows/availability-modes-always-on-availability-groups#SyncCommitAvMode

You create an availability group that has replicas named HA/Server01 and HA/Server02.

Currently, HA/Server01 is the primary replica.

You have multiple queries that read data and produce reports from the database.

You need to offload the reporting workload to the secondary replica when HA/Server01 is the primary replica.

What should you do?

Set the Availability Mode property of HA/Server02 to Asynchronous commit.
Set the Readable Secondary property of HA/Server02 to Read-intent only.
Set the Connections in Primary Role property of HA/Server01 to Allow read/write connections.
Set the Availability Mode property of HA/Server01 to Asynchronous commit.

Correct answer: B

Explanation:

To set up a readable secondary replica, you first create an availability group. Then you add replicas. You can choose either Yes or Read-intent only options. References: http://msdn.microsoft.com/en-us/library/jj542414.aspx

To set up a readable secondary replica, you first create an availability group. Then you add replicas.

You can choose either Yes or Read-intent only options.