In SQL, commands are categorized into different language groups depending on their purpose:
Data Manipulation Language (DML):
Deals with manipulating the data stored in existing database objects.
Includes:
SELECT # query data
INSERT # add new records
UPDATE # modify existing records
DELETE # remove records
Therefore, UPDATE is a DML statement.
Data Definition Language (DDL):
Used to define and manage database schema objects (tables, indexes, schemas).
Includes: CREATE , ALTER , DROP , TRUNCATE .
Data Control Language (DCL):
Used to control access and permissions.
Includes: GRANT , REVOKE .
Now let's map the options:
A). REVOKE # DCL (not DML).
B). UPDATE # DML # (correct).
C). DROP # DDL (removes database objects).
D). CREATE # DDL (creates database objects).
Microsoft References
SQL Language Elements - DDL, DML, DCL
UPDATE (Transact-SQL)

Azure Video Indexer can ingest a video by URL as long as the URL is publicly accessible and directly downloadable (no authentication or HTML landing page). Creating a download link in OneDrive produces a direct-file URL that Video Indexer can fetch and index without you re-uploading the 20-GB file through your browser. A generic OneDrive "sharing link" often lands on a web page (not a direct file) and may require authentication, which Video Indexer cannot crawl. Uploading locally is possible but unnecessary and time- consuming for a 20-GB video.
Microsoft References
Upload/index videos in Video Indexer (supports uploading from a public URL).
https://learn.microsoft.com/azure/azure-video-indexer/upload-index-videos Video Indexer quotas and limits (file size limits; uploading by URL).

Comprehensive Detailed Explanation
The question focuses on monitoring a public-facing sales system that processes video and text, ensuring that the system provides equitable results regardless of user location or background.
Two Microsoft Responsible AI principles apply directly here:
Fairness
AI systems should treat all people fairly and avoid bias.
Monitoring ensures that outcomes do not disadvantage people based on location, background, or demographics.
This directly addresses the requirement for equitable results.
Inclusiveness
AI systems should empower everyone and engage people of all backgrounds.
Monitoring for inclusiveness ensures that the system works well across different regions, languages, and cultures, making the system accessible and beneficial for all users.
Why not the other options?
A). Transparency
Important for explaining how AI systems work, but does not directly address equitable results across demographics.
D). Reliability and safety
Focuses on consistent and safe system operation, not equity across users.
E). Privacy and security
Critical for data protection, but not related to equitable treatment of users.
The Answer:
B). fairness
C). inclusiveness
Microsoft References
Microsoft Responsible AI Principles
Fairness in AI systems
Inclusiveness in AI systems

The requirements state:
All AI solution responses must have a confidence score # 70%.
If the response confidence score is < 70%, the response must be improved by human input.
Members of the Consultant-Bookkeeper group must be able to process financial documents, which includes performing manual review when the AI confidence is below threshold.
Looking at the provided JSON:
" fields " : {
" ReceiptType " : {
" type " : " string " ,
" valueString " : " Itemized " ,
" confidence " : 0.672
},
" MerchantName " : {
" type " : " string " ,
" valueString " : " Tailwind " ,
" confidence " : 0.913
}
}
ReceiptType.confidence = 0.672 # this is below 0.7.
MerchantName.confidence = 0.913 # this is above 0.7.
Therefore, the correct condition for triggering manual review is:
documentResults.fields. < field > .confidence < 0.7
Now, evaluating the options:
A). documentResults.docType == " prebuilt:receipt "
Always true for receipts, does not check confidence. Not correct.
B). documentResults.fields.*.confidence < 0.7
This is the correct general expression: trigger manual review whenever any field confidence is below 0.7.
C). documentResults.fields.ReceiptType.confidence > 0.7
This would bypass manual review when ReceiptType has high confidence. The requirement is to trigger review when confidence < 0.7, so this is the opposite.
D). documentResults.fields.MerchantName.confidence < 0.7
This only checks one field (MerchantName). In the JSON, MerchantName has confidence 0.913 ( > 0.7), so this condition would not trigger, but ReceiptType clearly needs review. Too narrow.
The Answer: B. documentResults.fields.*.confidence < 0.7
Microsoft References
Azure AI Document Intelligence - Confidence scores
Human-in-the-loop for Document Intelligence

Explanation:

Comprehensive Detailed Explanation
You are tasked with building a solution using Custom Vision to detect faults in factory components. Custom Vision follows a defined workflow:
Create a project
Before anything else, you must create a Custom Vision project in the Azure AI portal.
This project specifies the type of model you are building: classification (classifying entire images) or object detection (locating items within images).
Since the question is about detecting faults in specific components (a business-specific scenario), it aligns with classification unless explicitly stated otherwise.
Upload and tag images
You must provide training data.
Upload a set of images showing both faulty and non-faulty components.
Tag each image correctly so that the model can learn from labeled examples.
Train the classifier model
Once images are tagged, you run training on the dataset to generate the classifier model.
The model can then be published and used for inference via API calls.
Why not the other options?
Initialize the training dataset: This is not a direct step in Custom Vision; instead, uploading and tagging images inherently prepares the training dataset.
Train the object detection model: Object detection is used if you need bounding boxes around items within an image. Since the question is about recognizing faults in a component (faulty vs non-faulty), a classifier model is appropriate.
Correct Sequence:
Create a project
Upload and tag images
Train the classifier model
Microsoft References
Quickstart: Build an image classification project with the Custom Vision portal Custom Vision overview Train and test a Custom Vision model