Ensurepass.com : Ensure you pass the IT Exams
2018 Aug Microsoft Official New Released 70-464
100% Free Download! 100% Pass Guaranteed!

Developing Microsoft SQL Server 2012 Databases

Question No: 71 – (Topic 7)

You need to optimize the index structure that is used by the tables that support the fraud detection services.

What should you do?

1. Add a hashed nonclustered index to CreateDate.

2. Add a not hash nonclustered index to CreateDate.

3. Add a not hash clustered index on POSTransactionId and CreateDate.

4. Add a hashed clustered index on POSTransactionId and CreateDate.

Answer: A

Explanation: The fraud detection service will need to meet the following requirement (among others):

Detect micropayments that are flagged with a StatusId value that is greater than 3 and that occurred within the last minute.

Question No: 72 DRAG DROP – (Topic 7)

You need to design the UserActivity table.

Which three steps should you perform in sequence? To answer, move the appropriate three actions from the list of actions to the answer area and arrange them in the correct order.

Answer:

Explanation: Box 1:

Box 2:

Box 3:

Note:

* Creating a partitioned table or index typically happens in four parts:

->Create a filegroup or filegroups and corresponding files that will hold the partitions specified by the partition scheme.

->Create a partition function that maps the rows of a table or index into partitions based on the values of a specified column.

->Create a partition scheme that maps the partitions of a partitioned table or index to the new filegroups.

->Create or modify a table or index and specify the partition scheme as the storage location.

• Reorganizing an index uses minimal system resources.

• From scenario:

/ The index maintenance strategy for the UserActivity table must provide the optimal structure for both maintainability and query performance.

/ The CoffeeAnalytics database will combine imports of the POSTransaction and MobileLocation tables to create a UserActivity table for reports on the trends in activity. Queries against the UserActivity table will include aggregated calculations on all columns that are not used in filters or groupings.

/ When the daily maintenance finishes, micropayments that are one week old must be available for queries in UserActivity table but will be queried most frequently within their first week and will require support for in-memory queries for data within first week.

The maintenance of the UserActivity table must allow frequent maintenance on the day#39;s most recent activities with minimal impact on the use of disk space and the resources available to queries. The processes that add data to the UserActivity table must be able to update data from any time period, even while maintenance is running.

* Columnstore indexes work well for mostly read-only queries that perform analysis on large data sets. Often, these are queries for data warehousing workloads. Columnstore indexes give high performance gains for queries that use full table scans, and are not well- suited for queries that seek into the data, searching for a particular value.

Question No: 73 DRAG DROP – (Topic 7)

You need to redesign the system to meet the scalability requirements of the application.

Develop the solution by selecting and arranging the required code blocks in the correct order.

You may not need all of the code blocks.

Answer:

Explanation: Box 1:

Box 2:

Box 3:

Box 4:

Box 5:

Box 6:

Box 7:

Note:

• MEMORY_OPTIMIZED_DATA

  First create a memory-optimized data filegroup and add a container to the filegroup. Then create a memory-optimized table.

• You must specify a value for the BUCKET_COUNT parameter when you create the memory-optimized table. In most cases the bucket count should be between 1 and 2 times the number of distinct values in the index key.

• Example:

  – create a durable (data will be persisted) memory-optimized table

  – two of the columns are indexed

  CREATE TABLE dbo.ShoppingCart (

  ShoppingCartId INT IDENTITY(1,1) PRIMARY KEY NONCLUSTERED, UserId INT NOT NULL INDEX ix_UserId NONCLUSTERED HASH WITH (BUCKET_COUNT=1000000),

  CreatedDate DATETIME2 NOT NULL, TotalPrice MONEY

  ) WITH (MEMORY_OPTIMIZED=ON) GO

  Question No: 74 – (Topic 7)

  You need to monitor the health of your tables and indexes in order to implement the required index maintenance strategy.

  What should you do?

  1. Query system DMVs to monitor avg_chain_length and max_chain_length. Create alerts to notify you when these values converge.

  2. Create a SQL Agent alert when the File Table: Avg time per file I/O request value is increasing.

  3. Query system DMVs to monitor total_bucket_count. Create alerts to notify you when this value increases.

  4. Query system DMVs to monitor total_bucket_count. Create alerts to notify you when this value decreases.

  Answer: A

  Explanation: From scenario:

• You need to anticipate when POSTransaction table will need index maintenance.

• The index maintenance strategy for the UserActivity table must provide the optimal structure for both maintainability and query performance.

Question No: 75 – (Topic 7)

You need to modify the stored procedure usp_LookupConcurrentUsers.

What should you do?

1. Use the summary table as an in-memory optimized table with a non-hash clustered index.

2. Use the summary table as an in-memory optimized table with a non-hash nonclustered index.

3. Use a type variable instead of the summary table.

4. Add a clustered index to the summary table.

Answer: A

Question No: 76 – (Topic 7)

You need to implement security for the restore and audit process. What should you do?

1. Grant the COFFECORP\Auditors group ALTER ANY CONNECTION and SELECT ALL USER SECURABLES permissions. Grant the COFFECORP\StoreAgent group ALTER ANY CONNECTION and IMPERSONATE ANY LOGIN permissions.

2. Grant the COFFECORP\Auditors group CONNECT ANY DATABASE and IMPERSONATE ANY LOGIN permissions. Grant the COFFECORP\StoreAgent group CONNECT ANY DATABASE and SELECT ALL USER SECURABLES permissions.

3. Grant the COFFECORP\Auditors group ALTER ANY CONNECTION and IMPERSONATE ANY LOGIN permissions. Grant the COFFECORP\StoreAgent group ALTER ANY CONNECTION and SELECT ALL USER SECURABLES permissions.

4. Grant the COFFECORP\Auditors group CONNECT ANY DATABASE and SELECT ALL USER SECURABLES permissions. Grant the COFFECORP\StoreAgent group CONNECT ANY DATABASE and IMPERSONATE ANY LOGIN permissions.

Answer: A

Topic 8, Mix Questions

Question No: 77 DRAG DROP – (Topic 8)

You need to identify which nonclustered indexes are unused by queries.

How should you complete the statement? To answer, drag the appropriate values to the correct locations. Each value may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.

Answer:

Explanation:

Box 1: sys.dm_db_index_usage_stats

sys.dm_db_index_usage_stats shows you how many times the index was used for user queries. It returns counts of different types of index operations and the time each type of operation was last performed in SQL Server.

Box 2: sys.indexes

sys.indexes contains a row per index or heap of a tabular object, such as a table, view, or table-valued function.

References: https://docs.microsoft.com/en-us/sql/relational-databases/system-dynamic- management-views/sys-dm-db-index-usage-stats-transact-sql https://docs.microsoft.com/en-us/sql/relational-databases/system-catalog-views/sys- indexes-transact-sql

Question No: 78 DRAG DROP – (Topic 8)

You have a database that contains three tables. The tables are configured as shown in the following table.

You have the following query:

The execution plan for the query is shown in the exhibit. (Click the Exhibit button.)

You need to create one index to minimize the amount of time it takes to execute the query. What should you do?

To answer, drag the appropriate columns to the correct locations in the answer area. (Answer choices may be used once, more than once, or not at all.)

Answer:

Explanation:

Box 1:

Box 2:

Box 3:

Note:

Covering index: A type of index that includes all the columns that are needed to process a particular query. For example, your query might retrieve the FirstName and LastName columns from a table, based on a value in the ContactID column. You can create a covering index that includes all three columns.

Question No: 79 – (Topic 8)

You have a table named Table1 that stores customer data.

Each customer has a credit limit that can only be discovered by querying multiple tables.

You need to ensure that the value of the credit limit is returned by executing a query on Table1.

What should you create?

1. A trigger that uses a ranking function

2. A trigger that uses a table-valued function

3. A calculated column that uses a table-valued function

4. A calculated column that uses a scalar function

Answer: C

Question No: 80 DRAG DROP – (Topic 8)

You have a table named Table1. Table1 has 1 million rows. Table1 has a columnstore index for a column named Column1.

You need to import data to Table1. The solution must minimize the amount of time it takes to import the data.

What should you do?

To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.

Answer:

Explanation:

Box 1: Create a table named Table2 by using the same schema as Table1. Note: Table2 is the staging table.

Box 2: Partition Table1

Box 3: Import the data to Table2.

Box 4: Create a columnstore index on Table2 for Column1. Box 5: Switch Table2 to Table1

Note:

• An xVelocity memory optimized columnstore index, groups and stores data for each column and then joins all the columns to complete the whole index.

  Columnstore indexes can transform the data warehousing experience for users by enabling faster performance for common data warehousing queries such as filtering, aggregating, grouping, and star-join queries.

• Tables that have a columnstore index cannot be updated. There are three ways to work around this problem.

1. To update a table with a columnstore index, drop the columnstore index, perform any required INSERT, DELETE, UPDATE, or MERGE operations, and then rebuild the columnstore index.

2. (applies in this scenario) Partition the table and switch partitions. For a bulk insert, insert data into a staging table, build a columnstore index on the staging table, and then switch the staging table into an empty partition. For other updates, switch a partition out of the main table into a staging table, disable or drop the columnstore index on the staging table, perform the update operations, rebuild or re-create the columnstore index on the staging table, and then switch the staging table back into the main table.

3. Place static data into a main table with a columnstore index, and put new data and recent data likely to change, into a separate table with the same schema that does not have a columnstore index.

100% Ensurepass Free Download!
–70-464 PDF
100% Ensurepass Free Guaranteed!
–70-464 Dumps

	EnsurePass	ExamCollection	Testking
Lowest Price Guarantee	Yes	No	No
Up-to-Dated	Yes	No	No
Real Questions	Yes	No	No
Explanation	Yes	No	No
PDF VCE	Yes	No	No
Free VCE Simulator	Yes	No	No
Instant Download	Yes	No	No