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.
Requirements
Contoso is deploying a new Azure SQL database that will become the authoritative data store for the following;
Sometimesthe ingestion pipeline fails due to malformed JSON and duplicate payloads.
The engineers at Contoso report that the following dashboard query runs slowly.
SELECT VehicleTd, Lastupdatedutc, EngineStatus, BatteryHealth FROM dbo.VehicleHealthSumary where fleetld- gFleetld ORDER BV LastUpdatedUtc DESC;
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
Planned Changes
Contoso wants to modernize Fleet Intelligence Platform to support Al-powered semantic search over
incident reports.
Security 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 LastModif reduce column to the time of the change.
• Avoidrecursive updates.
AI Search, Embedding’s, and Vector indexing
The development learn 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 customer-Feedback 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.
• Orderthe results by similarity score, with the highest score first
View Mode
Q: 5
You have a database named DB1. The schema is stored in a Git repository as an SDK-style SQL
database project.
You have a GitHub Actions workflow that already runs dotnet build and produces a database artifact.
You need to add a deployment step that publishes the dacpac file to an Azure SQL database by using
the secrets stored in GitHub repository secrets
What should you include in the workflow?
A)
B)
C)
D)
Options
Discussion
No comments yet. Be the first to comment.
Be respectful. No spam.
Correct Answer:
C
Explanation
This YAML snippet correctly configures a GitHub Actions workflow step to deploy a SQL database project. It uses the official Azure/sql-action@v2 action, which is designed for deploying .dacpac files to Azure SQL. The connection-string parameter is securely populated using a repository secret (${{ secrets.AZURESQLCONNECTIONSTRING }}), which is a best practice for handling sensitive credentials. The path parameter correctly points to the .dacpac file produced by the preceding build step, ensuring the correct artifact is deployed.
Why Incorrect
A. This option uses the correct action but incorrectly hardcodes a placeholder for the connection string directly in the workflow file, which is insecure and not functional.
B. This option uses Azure/webapps-deploy, an action designed for deploying applications to Azure App Service, not for deploying .dacpac files to an Azure SQL database.
D. This option uses Azure/appservice-settings, which is an action for configuring application settings on an Azure App Service instance, not for database deployment.
B)
B)
C)
D)
