Microsoft AI-200 : Developing AI Cloud Solutions on Azure

You are designing an Azure Database for PostgreSQL table for semantic search. Queries frequently filter on the created_at column. The schema must support vector similarity search and reliable date filtering You need to ensure that the table meets the requirements.
Which two actions should you perform? Each correct answer presents part of the solution. Choose two NOTE: Each correct selection is worth one point.

• A. Use a typed timestamp column for created_at.
• B. Store embeddings in a varchar column.
• C. Store created_at as a free-form string.
• D. Store embeddings in a pgvector column.

Explanation: Only visible for DumpsTests members. You can sign-up / login (it's free).

You are implementing semantic retrieval in Redis.
The solution must support low-latency, approximate nearest neighbor (ANN) vector similarity search for large-scale AI retrieval workloads.
You need to select the appropriate vector schema settings.
Which configuration values should you select? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.

Explanation:

You are configuring an Azure-hosted AI application that uses Azure App Configuration to manage its runtime settings.
The application must provide the following functionality:
- Support percentage-based, targeted rollouts.
- Maximize token limits per request.
- Store a key that is retrieved securely at runtime.
- Reference a list of supported deployment regions.
You need to configure the App Configuration features for the app.
Which features should you configure? To answer, move the appropriate App Configuration features to the correct configuration items. You may use each App Configuration features once, more than once, or not at all. You may need to move the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point.

Explanation:
* Support percentage-based, targeted rollouts: Feature flag
* Maximize token limits per request: Key-value
* Store a key that is retrieved securely at runtime: Key Vault reference
* Reference a list of supported deployment regions: Key-value
Azure App Configuration provides three distinct mechanisms for these scenarios. A Feature flag is the correct choice for percentage-based and targeted rollouts. Feature Management supports conditional activation based on filters such as percentage allocation, users, groups, and other targeting criteria, making it appropriate for gradual deployment and controlled experimentation.
A Key-value is the correct mechanism for ordinary runtime configuration data such as a model token limit or a list of supported deployment regions. These values are application settings rather than secrets or feature- state controls. The application can retrieve and refresh them dynamically without redeployment. A token-limit setting such as MaxTokensPerRequest and a region list such as SupportedRegions fit naturally into App Configuration key-value entries.
For sensitive data, use a Key Vault reference . App Configuration stores only the reference to the Azure Key Vault secret rather than the secret value itself. At runtime, the application resolves the secret securely, typically by using a managed identity. This avoids embedding credentials or sensitive keys in configuration values.
Therefore, the correct mapping is Feature flag # Key-value # Key Vault reference # Key-value .
Study Guide references: Azure App Configuration # Feature Management; key-values; Key Vault references; dynamic application configuration.

You are developing several microservices to run on Azure Container Apps.
You need to monitor and diagnose the microservices.
Which features should you use? To answer, select the appropriate feature in the answer area.
NOTE: Each correct selection is worth one point.

Explanation:
View console logs from a container in near real-time: Log streaming
* Debug the microservice from inside the container: Container console
For near-real-time troubleshooting, use Log streaming . Azure Container Apps supports streaming both system logs and container console logs directly through the Azure portal or Azure CLI. Microsoft documents that container console logs originate from the application ' s stdout and stderr streams, and the log-streaming feature can display them in near real time. This is the correct feature when developers need immediate visibility into container output without waiting for log ingestion into a monitoring workspace.
To debug the application from inside the running container , use the Container console . Azure Container Apps allows operators to connect interactively to a container by using the portal console or the az containerapp exec command. From there, they can run commands through shells such as bash or sh, inspect files, test network connectivity, examine environment variables, and troubleshoot runtime behavior directly in the container context.
Azure Monitor metrics are appropriate for aggregated performance measurements rather than interactive container debugging. Azure Monitor Log Analytics is useful for historical queries and centralized analysis, but Microsoft notes that ingested logs can have a delay of several minutes, so it is not the best choice for near- real-time console output.
Study Guide references: Azure Container Apps # Log streaming; Container console; observability; Azure Monitor integration; interactive troubleshooting.

You are reviewing the message processing code in a backend worker service.
You review the following Python code that initializes and starts a Service Bus processor

Explanation:

Verified Answer: No; Yes; No.
Detailed Explanation: The default Service Bus receive behavior is PeekLock rather than receive-and-delete, so merely receiving a message does not remove it from the queue; it must be settled successfully. If processing fails and the message remains unsettled or the lock is lost, it can become available for another delivery. Invalid JSON, however, is an application-level content problem: Service Bus does not inspect the payload as JSON and automatically retry it to MaxDeliveryCount solely because deserialization fails. The application's settlement/error path determines what happens.
Study Guide Alignment: Azure service integration: Service Bus, Event Grid, Azure Functions triggers
/bindings, and event-driven processing.
Official Microsoft Learn References: AI-200 Study Guide | Service Bus message transfers, locks, and settlement | Service Bus messages, routing, and correlation