* The requirement is to identify the created Azure AI services account within a DevOps pipeline.
* The az cognitiveservices account show command returns the details (name, id, location, etc.) of an existing Azure AI service account.
* az resource link creates or manages links between resources, not what we need.
* az account list lists Azure subscriptions, not resources.
* az cognitiveservices account network-rule manages network access rules but does not return account identity.
Microsoft References:
* az cognitiveservices account show

* The requirement is to optimize the reading experience for users with dyslexia and learning differences.
* Azure AI Immersive Reader is specifically designed to make text more accessible, improving comprehension by enabling features like text-to-speech, line focus, and translation.
* Translator (A) is for translating text, not accessibility.
* Document Intelligence (B) is for extracting information from documents.
* Azure AI Language (D) is for NLP tasks, not improving reading accessibility.
Microsoft References:
* Azure AI Immersive Reader overview

Explanation:
Use " definition " for the first field and " sampleBlobUrl " for the second field When creating a custom text category in Azure AI Content Safety, you call the PUT /contentsafety/text
/categories/{categoryName} endpoint and provide a JSON body that includes:
categoryName : the identifier of your category.
definition : a natural-language description of what the category covers (e.g., "text prompts about learning advice while preparing for an exam").
sampleBlobUrl : a pointer to labeled sample data (typically a JSONL file in Azure Storage) used to help the service understand the category.
Keys like prompt or text are used when analyzing content (for example, text:detect ), not when defining a category. Likewise, blocklistName applies to blocklist operations, and outputType is not part of the category- creation schema. Therefore, the correct payload fields to complete the cURL are definition and sampleBlobUrl .
Microsoft Azure AI References (titles only)
Azure AI Content Safety - Create or update custom text categories (REST) Azure AI Content Safety - Custom categories concepts and training data (JSONL in blob storage) Azure AI Content Safety - Text analysis vs. category management endpoints

Explanation:

In SQL, DML (Data Manipulation Language) statements include SELECT , INSERT , UPDATE , and DELETE . Often, you need to filter which rows are affected or returned. That filtering is done with the WHERE clause.
Let's review the options:
ALTER
Used in Data Definition Language (DDL), not DML.
Alters the structure of a database object (e.g., add/remove columns, modify constraints).
Not used to filter rows.
ON
Used in JOIN operations to specify the relationship between tables.
Does not specify row-level filtering criteria in general DML.
SET
Used in the UPDATE statement to assign new values to columns.
Does not specify which rows to update.
WHERE
Used in DML statements to specify criteria for rows that must match.
Examples:
SELECT * FROM Customers WHERE Country = ' USA ' ;
DELETE FROM Orders WHERE OrderDate < ' 2020-01-01 ' ;
UPDATE Products SET Price = Price * 1.1 WHERE CategoryID = 5;
Thus, the correct clause is WHERE.
The Answer: WHERE
Microsoft References
SQL WHERE clause
SQL UPDATE with WHERE
SQL DELETE with WHERE

Explanation:

You are deploying a Language Understanding (LUIS) container. When running LUIS in Docker, the model must first be exported from the Language Understanding portal, and then provided to the container at runtime.
Step-by-step reasoning:
From the Language Understanding portal, export the solution as a package file.
The trained LUIS model must be exported from the portal into a .json package file.
This is required because the container cannot access the hosted service directly.
From the host computer, move the package file to the Docker input directory.
Containers expect the model to be available locally.
The package file is placed into the input directory that the container maps for models.
From the host computer, run the container and specify the input directory.
When starting the container, you specify --volume < local_input > :/input so the container has access to the package file.
This makes the exported model available inside the container for processing.
Why not the other options?
Retain the model in the portal is not sufficient; the container cannot pull directly from the cloud.
Build the container and specify the output directory is not required; the container image is already available from MCR and is not custom-built for this step.
Correct Answer Order:
Export the solution as a package file.
Move the package file to the Docker input directory.
Run the container and specify the input directory.
Microsoft References
Run LUIS containers
Use containers with Azure AI services