Download Provisioning SQL Databases.selftesttraining.70-765.2019-03-24.1e.112q.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. 
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/

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

You would need to use either the SQL Server Management Studio or Transact-SQL. 
References: https://docs.microsoft.com/en-us/azure/sql-database/sql-database-cloud-migrate

A contained database is a database that is isolated from other databases and from the instance of SQL Server that hosts the database. 
B: In the contained database user model, the login in the master database is not present. Instead, the authentication process occurs at the user database, and the database user in the user database does not have an associated login in the master database.
SQL Database and SQL Data Warehouse support Azure Active Directory identities as contained database users. 
D: The contained database feature is currently available only in a partially contained state. A partially contained database is a contained database that allows the use of uncontained features.
References: https://docs.microsoft.com/en-us/sql/relational-databases/databases/contained-databases