DP-800

更新时间:   试题数量:   购买人数:   提供作者:

有效期: 个月

章节介绍: 共有个章节

收藏
搜索
题库预览
Testlet 1

Case Study

This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.

To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study.

At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section.

To start the case study

To display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment and problem statements. If the case study has an All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs. When you are ready to answer a question, click the Question button to return to the question.

Existing Environment

Azure Environment

Contoso has an Azure subscription in North Europe that contains the corporate infrastructure. The current infrastructure contains a Microsoft SQL Server 2017 database. The database contains the following tables.

(含图)

The FeedbackJson column has a full-text index and stores JSON documents in the following format.

(含图)

The support staff at Contoso never has the UNMASK permission.

Problem Statements

Contoso is deploying a new Azure SQL database that will become the authoritative data store for the following:

AI workloads

Vector search

Modernized API access

Retrieval Augmented Generation (RAG) pipelines

Sometimes the ingestion pipeline fails due to malformed JSON and duplicate payloads. The engineers at Contoso report that the following dashboard query runs slowly.

(含图)

You review the execution plan and discover that the plan shows a clustered index scan. VehicleIncidentReports often contains details about the weather, traffic conditions, and location. Analysts report that it is difficult to find similar incidents based on these details.

Requirements

Planned Changes

Contoso wants to modernize Fleet Intelligence Platform to support AI-powered semantic search over incident reports.

Security Requirements

Contoso identifies the following security requirements:

Restrict the support staff from viewing Personally Identifiable Information (PII) data, which is full email addresses and phone numbers.

Enforce row-level filtering so that analysts see only incidents for the fleets to which they are assigned. The analysts can be assigned to multiple fleets.

Database Performance and Requirements

Contoso identifies the following telemetry requirements:

Telemetry data must be stored in a partitioned table.

Telemetry data must provide predictable performance for ingestion and retention operations. latitude, longitude, and accuracy JSON properties must be filtered by using an index seek.

Contoso identifies the following maintenance data requirements:

Ensure that any changes to a row in the MaintenanceEvents table updates the corresponding value in the LastModifiedUtc column to the time of the change.

Avoid recursive updates.

AI Search, Embeddings, and Vector Indexing

Contoso plans to implement semantic search over incident data to meet the following requirements:

Embeddings must be stored in dedicated Azure SQL Database tables.

Embeddings must be generated from rich natural language fields.

Chunking must preserve semantic coherence.

Hybrid search must combine the following:

- Vector similarity

- Keyword filtering or boosting

Development Requirements

The development team at Contoso will use Microsoft Visual Studio Code and GitHub Copilot and will retrieve live metadata from the databases.

Contoso identifies the following requirements for querying data in the FeedbackJson column of the CustomerFeedback table:

Extract the customer feedback text from the JSON document.

Filter rows where the JSON text contains a keyword.

Calculate a fuzzy similarity score between the feedback text and a known issue description. Order the results by similarity score, with the highest score first.

QUESTION 1

HOTSPOT

You need to meet the development requirements for the FeedbackJson column.

How should you complete the Transact-SQL query? To answer, select the appropriate options in the answer area.

SELECT

f. FeedbackId,

f. Vehicleld,

()

EDIT_DISTANCE_SIMILARITY

JSON_VALUE(f.FeedbackJson, "S.text"),

@KnownIssueDescription

) AS Similarityscore

FROM

dbo. CustomerFeedback f

WHERE

()

ORDER BY

()

DESC;

Testlet 2

Case Study

This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.

To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study.

At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section.

To start the case study

To display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment and problem statements. If the case study has an All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs. When you are ready to answer a question, click the Question button to return to the question.

Existing Environment

Azure Environment

Fabrikam has a single Azure subscription in the East US 2 Azure region. The subscription contains an Azure SQL database named DB1. DB1 contains the following tables:

Patients

Employees

Procedures

Transactions

UsefulPrompts

ProcedureDocuments

You store a column master key as a secret in Azure Key Vault.

You have an on-premises application named TransactionProcessing that uses a hard-coded username

and password in a connection string to access DB1.

Problem Statements

Users report that after executing a long-running stored procedure named sp_UpdateProcedureForPatient, updates to the underlying data are sometimes inconsistent.

Requirements

Planned Changes

Fabrikam plans to manage all changes to Azure SQL Database objects by using source control in GitHub. Every pull request submitted to production will be validated before it can be merged. Deployments must use the Release configuration.

Security Requirements

Fabrikam identifies the following security requirements:

The TransactionProcessing application must use a passwordless connection to DB1.

The Employees table contains two columns named TaxID and Salary that must be encrypted at

rest.

Auditors must have a tamper-evident history of transactions with cryptographic proof of changes to the employee data.

Database Performance Requirements

Records accessed by using sp_UpdateProcedureForPatient must NOT be changed by other transactions while the stored procedure runs.

AI Search, Embeddings, and Vector Indexing

Fabrikam identifies the following AI-related requirements:

Queries to the ProcedureDocuments table must use Reciprocal Rank Fusion (RRF).

Users must be able to query the data in DB1 by using prompts in Copilot in Microsoft Fabric.

The UsefulPrompts table will store prompts that doctors can use to help diagnose patient illness by

connecting to an Azure OpenAI endpoint.

Development Requirements

Fabrikam identifies the following development requirements:

Provide the functionality to retrieve all the transactions of a given patient between two dates, showing a running total.

Expose a Data API builder (DAB) configuration file to enable Azure services to perform the following operations over a REST API:

- Read data from the procedures table without authentication.

- Read and insert data into the Transactions table once authenticated.

- Execute the sp_UpdateProcedurePatient stored procedure.

Provide the functionality to retrieve a list of the names of patients who underwent medical procedures during the last 30 days.

Information for each medical procedure will be stored in a table. The table will be used with a large language model (LLM) for user querying and will have the following structure.

(含图)

DAB

You create a DAB configuration file that meets the development requirements for DB1 and includes the following entities.

(含图)

QUESTION 1

HOTSPOT

You need to create a solution that meets the development requirements for retrieving the patient lists. How should you complete the Transact-SQL code? To answer, select the appropriate options

in the answer area.

NOTE: Each correct selection is worth one point.

CREATE PROCEDURE dbo.GetActivePatients

AS

BEGIN

SET NOCOUNT ON;

SELECT p. Name

FROM dbo. Patients AS p

()

SELECT PatientId

FROM dbo.Procedures AS pr

()

AND pr.TransactionDate >= DATEADD(DAY, -30, SYSUTDATETIME ())

) ;

END

1 2