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: 13
DRAG DROP You have a database named DB1. The schema is stored in a GitHub repository as an SDK style SQL database project. You use a feature branch workflow to deploy changes to DB1 You need to update the local feature branch with the latest changes to main, and then create a pull request to merge the feature branch into main for review. How should you complete the GitHub CLI script? To answer, drag the appropriate values to the correct targets. 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. NOTE: Each correct selection is worth one point.
Drag & Drop
Discussion
No comments yet. Be the first to comment.
Be respectful. No spam.
Correct Answer:
Answer Area
Target 1: E. git fetch origin
Target 2: F. git merge origin/main
Target 3: A. gh pr create
Explanation
To achieve the stated goal, you must first integrate the latest remote changes from the main branch into your current local feature branch, and subsequently open a pull request.
git fetch origin: This command securely downloads the latest commits, files, and refs from the remote repository (origin) without immediately merging them into your working tree.
git merge origin/main: Executing this while on feature/db1-add-staticdata integrates the recently fetched remote tracking branch (origin/main) into your local feature branch, updating it with the latest changes.
gh pr create: The trailing backslash and subsequent flags (--title, --body, --head, --base, --web) are parameters specific to the GitHub CLI tool. gh pr create utilizes these flags to instantiate the pull request for review.
References
Git Official Documentation: "git-fetch - Download objects and refs from another repository." Git-SCM. Available at: (Accessed for standard remote tracking branch updates).
Git Official Documentation: "git-merge - Join two or more development histories together." Git-SCM. Available at: (Accessed for integrating remote tracking branches into local working trees).
GitHub CLI Official Documentation: "gh pr create." GitHub CLI Manual. Available at: (Accessed for validation of PR creation flags: --title, --body, --head, --base, --repo, --web).
