70-764最も有効な質問と解答で勉強

You store Microsoft SQL Server backups at an off-site location that has no protection from unauthorized access. Your organization has not implemented hardware security modules (HSM).
You need to implement a solution for encrypting the SQL backups.
Which three actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.

Explanation

Step 1: Create a database master key of the master database.
Step 2: Create a certificate for the backups.
Create a Backup Certificate: Create a backup certificate in the master database.
Step 3:
Backup the database: Specify the encryption algorithm and certificate to use.
References:
https://docs.microsoft.com/en-us/sql/relational-databases/backup-restore/create-an-encrypted-backup?view=sql-s

Note: This question is part of a series of questions that use the same scenario. For your convenience, the scenario is repeated in each question. Each question presents a different goal and answer choices, but the next of the scenario is exactly the same in each question in this series.
Start of repeated scenario
Contoso, Ltd. has Microsoft SQL Server databases that support a custom application. The current SQL Server environment consists of two servers: ContosoSQL1 and ContosoSQL2. These two servers participate in an Always On Availability Group named ContosoAG1 that is configured to use synchronous-commit with automatic failover. The secondary replica is not configured for read-only access.
The application performs both transactional processing and historical data retrieval in a database named ContosoDB. The application includes an inventory management module. The inventory management module and database have experienced performance issues.
Users report that a query named InventoryQuery1 takes a long time to complete. The query is shown as follows:
SELECT ProductNumber, Name, ProductLine
FROM Production.Product
WHERE ProductNumber = N'<specific product>'
The query plan used by SQL Server for this query is shown in the exhibit. (Click the Exhibit tab.) Various performance issues, including frequent long-term blocking episodes, prevent business users from completing their daily tasks. You suspect the tempdb database resources could be responsible. You must create Blocking reports for the ContosoDB database to identify issues.
Exhibit.

You plan to use Extended Events to review all Transact-SQL statements that are run against the ContosoSQL1 instance. The output from the Extended Events session must contain both start and stop events and must be written to a file. You must configure the Extended Events session to minimize possible data loss and reduce the effect on server performance.
You plan to deploy an additional secondary replica named ContosoSQL3 to ContosoAG1. Read-only traffic must be load-balanced between the two secondary replicas, regardless of which instance is the primary replica.
Contoso plans to add an additional dedicated reporting system that will rely on real-time data from the transactional databases.
End of repeated scenario
You need to create the blocking reports.
Which three actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.

Explanation

Scenario:
Various performance issues, including frequent long-term blocking episodes, prevent business users from completing their daily tasks. You suspect the tempdb database resources could be responsible. You must create Blocking reports for the ContosoDB database to identify issues.
Step 1: Enable the Show advanced options server configuration option
First, you need to decide how many seconds a process should be blocked for in order for it to be included in the report, i.e. the blocked process threshold. If you set this value too low you may generate too much noise in the report. If you set it too high you might not get any processes waiting long enough to appear in the report.
For Microsoft Dynamics NAV environments, the value should be less than any "Lock Timeout" setting which may be enabled (as set in the NAV Development Environment, see File -> Database -> "Alter Database" ->
"Advanced" tab).
Step 2: Set the Blocked process threshold server configuration option to 60 By default, the "blocked process threshold" is zero, meaning that SQL Server won't generate the blocked process reports. We need to configure by the "blocked process threshold" to a specific value (in seconds) using the sp_configure option. For example, if we set it to 15 seconds, then the event will fire three times if a session is blocked for 45 seconds.
Step 3: Use Extended Events to capture blocking reports for review
If blocking is causing issues, we can run an Extended Events event session, to log occurrences of blocking that exceed a specific time threshold, and capture the blocked_process_report event.
References:
https://cloudblogs.microsoft.com/dynamics365/no-audience/2015/01/16/using-sql-server-extended-events-to-pro

You need to recommend a backup process for an Online Transaction Processing (OLTP) database. The process must meet the following requirements:
* Ensure that if a hardware failure occurs, you can bring the database online with a minimum amount of data loss.
* Minimize the amount of administrative effort required to restore any lost data.
What should you include in the recommendation? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.

Explanation

A table named Table1 has a clustered columnstore index. The table contains over 10 billion records. This represents 12 years of sales data. The table is stored in a single filegroup.
You drop the existing columnstore index. You allocate 13 new filegroups with files large enough to store the entire table.
You need to implement a new columnstore index that supports maximum data compression for data older than
2 years.
Which four actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.

Explanation

Step 1: Create a nonclustered index by year
Step 2: Define a partitioning function
A partition function must first be created in a CREATE PARTITION FUNCTION statement before creating a partition scheme.
Step 3: Define a partitioning scheme
The CREATE PARTITION SCHEME command creates a scheme in the current database that maps the partitions of a partitioned table or index to filegroups. The number and domain of the partitions of a partitioned table or index are determined in a partition function.
Step 4: Create a partitioned clustered columnstore index. Use columnstore_archive data...
For partitioned tables and indexes, you can configure the compression option for each partition, and the various partitions of an object do not have to have the same compression setting.
For partitioned columnstore tables and columnstore indexes, you can configure the archival compression option for each partition, and the various partitions do not have to have the same archival compression setting.
The partition scheme must already exist in the database when you create a columnstore index.
References:
https://docs.microsoft.com/en-us/sql/relational-databases/data-compression/data-compression?view=sql-server-2
https://docs.microsoft.com/en-us/sql/t-sql/statements/create-partition-scheme-transact-sql?view=sql-server-2017

Note: This question is part of a series of questions that use the same scenario. For your convenience, the scenario is repeated in each question. Each question presents a different goal and answer choices, but the next of the scenario is exactly the same in each question in this series.
Start of repeated scenario
Contoso, Ltd. has Microsoft SQL Server databases that support a custom application. The current SQL Server environment consists of two servers: ContosoSQL1 and ContosoSQL2. These two servers participate in an Always On Availability Group named ContosoAG1 that is configured to use synchronous-commit with automatic failover. The secondary replica is not configured for read-only access.
The application performs both transactional processing and historical data retrieval in a database named ContosoDB. The application includes an inventory management module. The inventory management module and database have experienced performance issues.
Users report that a query named InventoryQuery1 takes a long time to complete. The query is shown as follows:
SELECT ProductNumber, Name, ProductLine
FROM Production.Product
WHERE ProductNumber = N'<specific product>'
The query plan used by SQL Server for this query is shown in the exhibit. (Click the Exhibit tab.) Various performance issues, including frequent long-term blocking episodes, prevent business users from completing their daily tasks. You suspect the database resources could be responsible. You must create Blocking reports for the ContosoDB database to identify issues.
Exhibit.

You plan to use Extended Events to review all Transact-SQL statements that are run against the ContosoSQL1 instance. The output from the Extended Events session must contain both start and stop events and must be written to a file. You must configure the Extended Events session to minimize possible data loss and reduce the effect on server performance.
You plan to deploy an additional secondary replica named ContosoSQL3 to ContosoAG1. Read-only traffic must be load-balanced between the two secondary replicas, regardless of which instance is the primary replica.
Contoso plans to add an additional dedicated reporting system that will rely on real-time data from the transactional databases.
End of repeated scenario
You need to troubleshoot and resolve the issue with InventoryQuery1.
Use the drop-down menus to select the answer choice that answers each question based on the information presented in the graphic.

Explanation

Box 1: Key Lookup (clustered)
They Key Lookup (clustered) should be less than 50%.
Box 2: Change the table's primary key to the Product.ProductNumber column.
Incorrect: Non-Clustered Index Seek
Non-Clustered Index Seek occurs when Columns part of non-clustered index accessed in query and rows located in the B+ tree.
It is good and ideal to have a Non-Clustered Index Seek.
Action: Evaluate other operators
References:
https://www.sqlshack.com/sql-server-query-execution-plans-beginners-non-clustered-index-operators/