Explanation:
The percentage of false positives is [0].
* The value for the number of true positives divided by the total number of true positives and false negatives is [100].
The screenshot shows the Performance tab of a Custom Vision object detection model after training.
Two key performance metrics are in focus:
* False Positives (FP):
* False positives occur when the model incorrectly predicts an object that isn't present.
* In the provided exhibit, the model shows 0% false positives.
* This means it did not incorrectly classify any non-object as an object.
* Recall (True Positives ÷ (True Positives + False Negatives)):
* This measures how many of the actual objects were correctly detected.
* Formula: Recall = TP / (TP + FN).
* In the performance report, recall is 100%, meaning the model correctly detected all the actual objects (no false negatives).
* False positives: 0%
* Recall (TP ÷ (TP + FN)): 100%
Correct Answers:
* False positives # 0
* Recall # 100
* Custom Vision performance metrics
* Precision, recall, and accuracy in machine learning

You are building a Text-to-Speech (TTS) solution in Azure Cognitive Services Speech that must:
* Convert up to 400 characters (short-form TTS, not long audio synthesis).
* Provide multiple voice options to users.
* Minimize costs (short-form TTS is cheaper than long-form neural synthesis).
To provide a list of available voices, Azure Speech exposes a REST API endpoint:
* Correct endpoint:
* https://<region>.tts.speech.microsoft.com/cognitiveservices/voices/list This endpoint returns a list of all available voices (standard + neural) supported in the region, including locale, gender, and style.
* Option A: /longaudiosynthesis/voices
* Wrong. This is for long audio synthesis (narration/long documents).
* More expensive and not needed for short social media messages.
* Option B: /cognitiveservices/voices/list #
* Correct. This endpoint lists available voices for short-form text-to-speech, which matches the requirements.
* Option C: /cognitiveservices/v1?deploymentId={deployment}
* Wrong. This is for using a custom voice deployment.
* Not required here since the solution should minimize cost and use standard available voices.
* Option D: /speechtotext/v3.0/models/base
* Wrong. This is for speech-to-text (STT), not text-to-speech.
The answer:
B). https://uksouth.tts.speech.microsoft.com/cognitiveservices/voices/list
* Azure Speech Service REST API reference
* List voices in Azure Text-to-Speech

Explanation:

The given code is using the Azure AI Vision client library with the method:
image_analysis = client.analyze_image_in_stream(
image=image_stream,
visual_features=[
VisualFeatureTypes.tags,
VisualFeatureTypes.description
]
)
Breakdown of the functionality:
* VisualFeatureTypes.tags # Extracts tags (labels) describing the image (e.g., "dog", "tree", "outdoor"), including confidence scores.
* VisualFeatureTypes.description # Generates captions (natural-language sentences) that describe the image.
* The code explicitly iterates through tags and captions, printing both with their confidence values.
* The image is read from the local file system using:
* with open(local_image, "rb") as image_stream:
* Face recognition is not included because the code does not request VisualFeatureTypes.faces.
Correct Answer Matrix:
* Face recognition # No
* Tags with confidence # Yes
* Read image from local file system # Yes
* Azure AI Vision features (tags, description, faces, etc.)
* analyze_image_in_stream method

Your documents must include a field specifying which groups have access. This information becomes the filter criteria against which documents are selected or rejected from the result set returned to the issuer.
D: A query request targets the documents collection of a single index on a search service.
CF: In order to trim documents based on group_ids access, you should issue a search query with a group_ids
/any(g:search.in(g, 'group_id1, group_id2,...')) filter, where 'group_id1, group_id2,...' are the groups to which the search request issuer belongs.
Reference:
https://docs.microsoft.com/en-us/azure/search/search-security-trimming-for-azure-search

Explanation:

When using the Speech SDK's speech translation, a TranslationRecognitionResult includes a Reason property (type ResultReason) indicating the outcome. For successful translation results, the reason is ResultReason.TranslatedSpeech. In that case, you can read the recognized source text from translationRecognitionResult.Text and iterate the translated outputs from translationRecognitionResult.
Translations (a dictionary keyed by target language code).
RecognizingSpeech corresponds to interim hypotheses raised on the Recognizing event and is not the final result reason used here; NoMatch is the branch already handled for unrecognized audio.
Microsoft Azure AI References
* Azure AI Speech SDK - Speech translation overview and TranslationRecognizer usage (C#): result handling with ResultReason.TranslatedSpeech, reading Text and Translations.
* Speech SDK API reference - TranslationRecognitionResult (Reason, Text, Translations) and ResultReason enum (values include TranslatedSpeech, NoMatch, Canceled).