Download Microsoft.70-765.RealExams.2019-12-04.121q.tqb
| Vendor: | Microsoft |
| Exam Code: | 70-765 |
| Exam Name: | Provisioning SQL Databases |
| Date: | Dec 04, 2019 |
| File Size: | 3 MB |
Demo Questions
Question 1
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
Question 2
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/
Question 3
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/
