Download Provisioning SQL Databases.PrepDumps.70-765.2020-08-04.1e.163q.vcex

Azure Resource Manager template consists of JSON, not XAML, and expressions that you can use to construct values for your deployment. 
A good JSON editor 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

Azure Resource Manager template consists of JSON, not XAML, and expressions that you can use to construct values for your deployment. 
A good JSON editor 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

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. 
A new tab dedicated to tempdb has been added to the Database Engine Configuration step of setup workflow. 
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: SQL Database automatically creates a database backups and uses Azure read-access geo-redundant storage (RA-GRS) to provide geo-redundancy. These backups are created automatically and at no additional charge. You don't need to do anything to make them happen. Database backups are an essential part of any business continuity and disaster recovery strategy because they protect your data from accidental corruption or deletion. 
References: https://docs.microsoft.com/en-us/azure/sql-database/sql-database-automated-backups

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/

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

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

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