Initialize CosmosClient.

Specify the database name.

Obtain the container reference.

Run the query.

The Python Azure Cosmos DB SDK follows the resource hierarchy Account → Database → Container → Items . The first step is to initialize a reusable CosmosClient with the Azure Cosmos DB account endpoint and an appropriate credential. Microsoft identifies CosmosClient as the primary client for interacting with databases in an account.

Next, specify the existing database by calling client.get_database_client(database_name). This returns a DatabaseProxy representing that database. Importantly, DatabaseProxy should not be instantiated directly ; Microsoft explicitly states that it should be obtained through CosmosClient.get_database_client().

From the database reference, obtain the target container by using database.get_container_client(container_name). Microsoft documents this as the standard way to retrieve an existing container reference.

Finally, execute the SQL query through container.query_items() , which accepts the Cosmos DB for NoSQL query and optional parameters and returns an iterable result set.

Therefore, Initialize DatabaseProxy is the distractor: the SDK creates the DatabaseProxy through get_database_client; application code should not construct it directly.

Study Guide references: Azure Cosmos DB for NoSQL → Python SDK; CosmosClient; database and container clients; ContainerProxy.query_items().

Detailed Explanation: A semantic-search schema should use the pgvector vector type for embeddings so PostgreSQL can apply vector distance operators and vector indexes. The creation timestamp should use an actual timestamp data type so comparisons, range predicates, ordering, and indexes use date semantics rather than string ordering. Storing vectors or dates as free-form character data would sacrifice type validation and make similarity or date filtering less efficient and less reliable.

Study Guide Alignment: AI data-management workloads: Cosmos DB, PostgreSQL, caching, vector storage, vector retrieval, consistency, and connection optimization.

Official Microsoft Learn References: AI-200 Study Guide | Vector similarity search with Azure PostgreSQL

The question maps directly to the AI-200 objective “Develop AI solutions by using Azure Cosmos DB for NoSQL,” which includes running queries and optimizing query performance and Request Unit (RU) consumption.

Statement 1: No — The minimum throughput is not 400 RU/s.

The PowerShell command provisions the container with:

-AutoscaleMaxThroughput 5000

Azure Cosmos DB autoscale operates between approximately 10% and 100% of the configured maximum throughput . Microsoft documentation specifically gives the example of an autoscale container provisioned with 5,000 RU/s scaling between 500 RU/s and 5,000 RU/s . Therefore, for this container, the minimum operating autoscale throughput is 500 RU/s , not 400 RU/s.

Therefore:

“The minimum throughput for the container is 400 RU/s.” → No

Statement 2: No — The first query is not an in-partition query.

The container uses:

/EmployeeId

as its partition key.

The first query is:

SELECT * FROM c WHERE c.EmployeeId > ' 12345 '

Although the query references the partition key, it uses a range predicate ( > ) , not an equality predicate. Microsoft explicitly states that a range filter on a partition key is not scoped to a single physical partition . To qualify as an in-partition query, the filter must identify the applicable partition, typically through an equality predicate such as:

WHERE c.EmployeeId = ' 12345 '

Microsoft ' s documentation provides essentially the same example: a query using DeviceId > ... against a container partitioned by DeviceId is not an in-partition query .

Therefore:

“The first query statement is an in-partition query.” → No

Statement 3: Yes — The second query is a cross-partition query.

The second query is:

SELECT * FROM c WHERE c.UserId = ' 12345 '

The container ' s partition key is /EmployeeId, not /UserId. Because the query contains no filter on the partition key , Azure Cosmos DB cannot route it to one logical partition. It must fan out the query across the applicable physical partitions and combine the results.

Microsoft describes this behavior directly: when a query does not contain a filter on the partition key, it must execute across the partitions.

Therefore:

“The second query statement is a cross-partition query.” → Yes

Verified Answer: Yes; Yes; No.

Detailed Explanation: The get_secret call supplies an explicit version value, so it retrieves that particular version of dbPassword. DefaultAzureCredential can authenticate to Key Vault by using the Azure-hosted application’s managed identity without embedding a client secret in the application. Because the code requests a fixed version, later secret rotation creates a newer version but subsequent executions of this exact code continue to request the specified old version. To follow the latest version automatically, the version parameter must be omitted.

Study Guide Alignment: Security and operations: Key Vault, App Configuration, managed identity, OpenTelemetry, Azure Monitor, and KQL-based troubleshooting.

Official Microsoft Learn References: AI-200 Study Guide | Managed identities for Azure resources | Use Key Vault references for App Service and Functions

Azure Container Registry Tasks provides Azure-hosted container build capabilities, eliminating the need to maintain external Docker build servers or dedicated CI build infrastructure. A Quick task uses commands such as az acr build to send the build context to ACR-managed compute, where Azure builds the container image and, by default, pushes the successfully built image directly into the registry. Microsoft describes quick tasks as cloud-based, on-demand build-and-push operations that do not require a local Docker Engine.

For automatic execution after source-code changes, use a Source-triggered task . ACR Tasks can associate a task with a GitHub or Azure Repos repository and automatically execute the image build whenever code is committed to the configured branch. Microsoft documents that when a commit occurs, the source-control trigger causes ACR Tasks to build and push the resulting image.

A Webhook is not the required standalone ACR build component here. ACR Tasks creates and manages the necessary source-repository webhook as part of configuring the source trigger. An Artifact Cache rule caches upstream container artifacts and does not build application images from Git commits.

Study Guide references: Azure Container Registry Tasks → Quick tasks; Automatically triggered tasks; Source-code commit triggers; cloud-based image builds.

Verified Answer: Register a global trace provider → initialize the application TraceProvider. Export traces to Azure Monitor → create/configure AzureMonitorTraceExporter. Connect exporter to provider → add a span processor. Generate spans → use tracer.start_as_current_span(...).

Detailed Explanation: OpenTelemetry tracing is a pipeline: the application obtains a tracer from a configured provider, creates spans, passes ended spans through a span processor, and exports them using the Azure Monitor exporter. Creating spans alone is insufficient; without the provider/processor/exporter chain, no telemetry reaches Azure Monitor. Log sampling and legacy Application Insights TrackEvent calls are unrelated to the required OpenTelemetry trace-export path.

Study Guide Alignment: Security and operations: Key Vault, App Configuration, managed identity, OpenTelemetry, Azure Monitor, and KQL-based troubleshooting.

Official Microsoft Learn References: AI-200 Study Guide | Enable Azure Monitor OpenTelemetry

Facilitate mathematical distance calculations between data points: Configure a vector index.

Define the document schema for high-dimensional data: Store data as a numeric array.

Azure Cosmos DB for NoSQL supports native vector search by storing embeddings directly in JSON documents and defining a vector embedding policy plus a vector index on the embedding path. Microsoft documents that vector search compares a query vector with stored vectors by calculating similarity or distance through the VectorDistance() system function. A vector index materially improves this process by reducing search latency, increasing throughput, and lowering RU consumption compared with an unindexed vector scan.

The embedding property itself must be stored as an array of numeric values . Microsoft examples show embedding properties such as " contentVector " : [2, -1, 4, ...] and define the associated vector policy with attributes including path, data type, dimensions, and distance function. This representation is required because embeddings are high-dimensional numerical vectors generated by an embedding model.

A composite index optimizes queries involving multiple scalar properties but does not provide vector-distance indexing. A Base64-encoded string cannot be used directly for native vector similarity calculations because Cosmos DB expects the vector field to contain numeric values matching the configured dimensionality.

Study Guide references: Azure Cosmos DB for NoSQL → vector embedding policies; vector indexes; VectorDistance(); numeric embedding arrays; native vector search.