Microsoft AI-200 Exam With Confidence Using Practice Dumps

Detailed Explanation: Azure Key Vault references in App Service settings satisfy the requirement to keep secrets out of container images, source control, and directly stored application configuration. App Service resolves the referenced secret at runtime by using the app identity, so the application can consume the value as a normal setting without embedding credentials in the image. GitHub secrets are build/deployment secrets rather than a runtime App Service secret-delivery mechanism. Dockerfile ENV instructions would place secret material in the image configuration and violate the case requirements.

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 | Use Key Vault references for App Service and Functions | Managed identities for Azure resources

The batch embedding workload is planned to run in Azure Kubernetes Service (AKS) , and Kubernetes workloads should be defined declaratively by using YAML manifest files . Microsoft states that a Kubernetes manifest defines the desired state of cluster resources, including Deployments, Jobs, Services, ConfigMaps, and other Kubernetes objects. These manifests can then be deployed by using kubectl apply -f < manifest > .yaml.

For this case, YAML is particularly appropriate because the technical requirements emphasize repeatable, version-controlled, automated deployments . A batch vector embedding regeneration process would typically be represented as a Kubernetes workload such as a Job or another batch-oriented resource, with its configuration committed to Git alongside the rest of the deployment definitions.

kubectl run and kubectl create are imperative commands and are less appropriate for a controlled Git-based deployment model because they do not inherently preserve the complete desired-state definition as source-controlled configuration. XML is not the standard Kubernetes manifest format. az aks commands are primarily used to provision and manage the AKS cluster itself rather than declaratively define application workloads running inside the cluster.

Therefore, the correct choice is YAML-formatted Kubernetes manifest files .

Study Guide references: Azure Kubernetes Service → Kubernetes manifests; declarative deployments; kubectl apply; Git-based workload configuration.

Initialize the connection by using the account endpoint and key: CosmosClient

Define shared throughput: Database

Perform item CRUD operations: Container

The Azure Cosmos DB for NoSQL .NET SDK uses a clear resource hierarchy. CosmosClient is the top-level client object and is responsible for connecting to the Azure Cosmos DB account. Microsoft identifies it as the primary SDK class for accessing account-level resources and databases. It can be initialized by using the account endpoint together with an account key or another supported credential.

A Database represents a database resource within the account. Shared provisioned throughput is configured at the database level , allowing multiple containers within that database to share the same RU/s allocation. Microsoft documents that setting throughput on the database creates a shared-throughput database.

A Container is the SDK object used to interact with items stored in a Cosmos DB container. Microsoft specifically describes the Container class as the object used for item operations such as creating, reading, updating, deleting, and querying documents.

The Indexing policy option is not used for any of these requirements. It controls how Cosmos DB indexes document properties for query execution, not connectivity, shared throughput, or CRUD access.

Study Guide references: Azure Cosmos DB for NoSQL .NET SDK → CosmosClient; Database; shared throughput; Container; item CRUD operations.