nerdexam
Microsoft

AI-102 · Question #46

Drag and Drop Question You plan to use containerized versions of the Azure AI Anomaly Detector API on local devices for testing and in on-premises datacenters. You need to ensure that the…

The correct answer is Pull the Anomaly Detector container image.; Create a custom Dockerfile.; Build the image.; Push the image to an Azure container registry. The correct sequence addresses both requirements systematically: first pull the official Microsoft Anomaly Detector container image, then create a custom Dockerfile to embed the billing/API credentials directly into the image (preventing them from appearing in command-line…

Submitted by yuriko_h· Mar 30, 2026Deploy and manage AI solutions using Azure AI services, specifically deploying containerized AI services securely with access control and credential management best practices

Question

Drag and Drop Question You plan to use containerized versions of the Azure AI Anomaly Detector API on local devices for testing and in on-premises datacenters. You need to ensure that the containerized deployments meet the following requirements: - Prevent billing and API information from being stored in the command-line histories of the devices that run the container. - Control access to the container images by using Azure role-based access control (Azure RBAC). Which four actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order. (Choose four.) NOTE: More than one order of answer choices is correct. You will receive credit for any of the correct orders you select. Answer:

Exhibit

AI-102 question #46 exhibit

Answer Area

Drag items

Create a custom Dockerfile.Pull the Anomaly Detector container image.Distribute a docker run script.Push the image to an Azure container registry.Build the image.Push the image to Docker Hub.

Correct arrangement

  • Pull the Anomaly Detector container image.
  • Create a custom Dockerfile.
  • Build the image.
  • Push the image to an Azure container registry.

Explanation

The correct sequence addresses both requirements systematically: first pull the official Microsoft Anomaly Detector container image, then create a custom Dockerfile to embed the billing/API credentials directly into the image (preventing them from appearing in command-line histories), build the custom image from that Dockerfile, and finally push it to an Azure Container Registry (ACR) which natively supports Azure RBAC for access control. This approach ensures sensitive billing keys are baked into the image rather than passed as runtime command-line arguments, and ACR's integration with Azure AD/RBAC satisfies the access control requirement.

Topics

#Azure AI Containers#Azure Container Registry#Azure RBAC#Anomaly Detector

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full AI-102 Practice