Correct Answer:

Explanation:
* pull_request
* build Database.sqlproj -c Release
The correct configuration is pull_request with dotnet build Database.sqlproj -c Release.
Fabrikam requires every pull request targeting production to be validated before merging, and all deployments must use the Release configuration.
Technical breakdown:
1. pull_request trigger: Executes the GitHub Actions workflow when a pull request targets the main branch.
This allows SQL project validation before changes are merged.
2. dotnet build: Compiles the SDK-style SQL database project, validates its database schema model, and produces a .dacpac deployment artifact.
3. -c Release: Explicitly selects the Release build configuration, satisfying Fabrikam ' s deployment configuration requirement.
4. Branch protection: Configure GitHub branch protection rules to make successful validation a required status check before merging. The workflow alone does not enforce this restriction.
5. Incorrect alternatives: push runs after changes are pushed, while merge is not a valid GitHub Actions event.
dotnet pack packages projects, and dotnet publish is not the appropriate SQL project validation command.
Microsoft identifies dotnet build as the supported compilation method for SDK-style SQL projects.
Completed GitHub Actions workflow
name: Validate SQL Project
on:
pull_request:
branches: [ " main " ]
jobs:
validate:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Step 1
run: dotnet build Database.sqlproj -c Release
DP-800 Official Study Guide Reference:
Main topic: Secure, optimize, and deploy database solutions.
Subtopic: Implement CI/CD by using SQL Database Projects.
Specific examination objectives:
* Create, build, and validate database models by using SQL Database Projects, including SDK-style models.
* Manage branching, pull requests, and conflict resolution.
* Design and implement controls for deployment pipelines.

Correct Answer:

Explanation:
Function return type # RETURNS INT
Calculation # DATEDIFF(day, @OrderDate, GETDATE())
Comprehensive and Detailed Explanation with all Developing AI-Enabled Database Solutions documents: = The first correct selection is RETURNS INT because the requirement is to create a scalar UDF that returns a single integer representing the number of days since the order date. Microsoft documents that scalar user- defined functions return a single scalar value, and DATEDIFF returns an int value.
The second correct selection is:
DATEDIFF(day, @OrderDate, GETDATE())
Microsoft defines DATEDIFF(datepart, startdate, enddate) as returning the number of specified datepart boundaries crossed between two dates. Therefore, placing @OrderDate as the start date and GETDATE() as the end date returns the number of elapsed day boundaries from the order date to the current date and time.
GETDATE() is valid inside a Transact-SQL UDF. Microsoft explicitly lists GETDATE among the nondeterministic built-in functions that can be used in T-SQL user-defined functions. Its nondeterministic nature means the result changes over time, but it does not prevent creation of this scalar UDF.
The completed code is:
CREATE FUNCTION dbo.ufn_DaysSinceOrder
(
@OrderDate datetime2(0)
)
RETURNS INT
BEGIN
DECLARE @Days int;
SELECT @Days =
DATEDIFF(day, @OrderDate, GETDATE());
RETURN @Days;
END;
GO
So the drag-and-drop answers are:
First target: RETURNS INT
Second target: DATEDIFF(day, @OrderDate, GETDATE())

Correct Answer:

Explanation:
Verified answer:
Support agents must see only the rows of their own TenantId # Create a row-level security (RLS) predicate that uses the user context.
Support agents must see only the domain name portion of CustomerEmail # Configure dynamic data masking on selected columns.
Comprehensive and Detailed Explanation with all Developing AI-Enabled Database Solutions documents: = For the TenantId requirement, use Row-Level Security (RLS). RLS is designed to restrict which rows a database principal can access. A security predicate can compare the row ' s TenantId with tenant information derived from the current user ' s session or security context, so support agents querying the same Tickets table see only rows belonging to their own tenant. This is the correct multitenant isolation mechanism because it is enforced by the database rather than relying on individual reporting tools or application-side filtering.
For CustomerEmail, use Dynamic Data Masking (DDM). DDM controls how sensitive column values are displayed to users who do not have UNMASK permission. A partial masking rule can conceal the local/user- specific portion of an email address while exposing only the required portion, such as its domain, according to the masking configuration.
The remaining choices do not satisfy these specific requirements. Transparent Data Encryption (TDE) protects database files at rest but does not filter rows or selectively obscure query results. Always Encrypted protects sensitive values cryptographically and is appropriate when the database engine itself should not see plaintext, but it is not the right mechanism when support agents must deliberately see a controlled portion of an email address.
Final drag-and-drop selections:
Own TenantId rows # Create a row-level security (RLS) predicate that uses the user context Only domain portion of CustomerEmail # Configure dynamic data masking on selected columns

Correct Answer:

Explanation:
A REST GET request to the order entity that includes the access token and x-MS-API-ROLE: operations will return data. # No When DAB runs the stored procedure, the database policy defined on the FinalizeOrder entity will be enforced. # Yes If the client omits the x-MS-API-ROLE header but still sends the same access token, the order entity read request will run in the authenticated role context. # Yes The first statement is No. In Data API builder, when a valid token is sent with X-MS-API-ROLE, the request runs in that requested role if that role is present in the token. Here, that means the effective role becomes operations, not authenticated. But the order entity grants read only to the authenticated role, not to operations, so the GET request would not be authorized to return data.
The second statement is Yes. DAB evaluates the request against the permissions and policies configured for the effective role on the requested entity. The FinalizeOrder entity grants execute to role operations and includes a database policy of TenantId = @claims.tenantid, so that policy is part of the enforced authorization
/filtering behavior when the stored procedure entity is executed.
The third statement is Yes. If the client sends a valid access token without X-MS-API-ROLE, DAB uses the built-in Authenticated system role by default. Since the order entity allows read for the authenticated role, that read request runs in the authenticated role context.
Top of Form
Bottom of Form

Correct Answer: C  🗳️

Explanation: Only visible for ExamDumpsVCE members. You can sign-up / login (it's free).