{"id":22833,"date":"2026-09-26T08:05:10","date_gmt":"2026-09-26T08:05:10","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=22833"},"modified":"2026-09-26T08:05:10","modified_gmt":"2026-09-26T08:05:10","slug":"microsoft-ai-200-practice-test-questions-and-exam-dumps-part19-q361-380","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/microsoft-ai-200-practice-test-questions-and-exam-dumps-part19-q361-380\/","title":{"rendered":"Microsoft AI-200 Practice Test Questions and Exam Dumps Part19 Q361-380"},"content":{"rendered":"<h2><b>View Full <\/b><a href=\"https:\/\/www.examlabs.com\/ai-200-exam-dumps\"><b>Microsoft AI-200 Exam Dumps<\/b><\/a><b> and Practice Test Dumps<\/b><\/h2>\n<p>&nbsp;<\/p>\n<h3><b>Question 361<\/b><\/h3>\n<p><b>Which Azure AI Search capability returns only selected document fields?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Search mode<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Select clause<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Query type<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Scoring function<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The $select parameter in Azure AI Search allows an application to specify which fields should be included in returned search documents. This can reduce unnecessary response data and ensure clients receive only the properties needed by the application. Search mode influences how search terms are interpreted, query type controls the query syntax or behavior, and scoring functions influence relevance calculations. Selecting only required fields can be useful in AI applications where search results are passed into downstream processing and unnecessary document content would increase response size.<\/span><\/p>\n<h3><b>Question 362<\/b><\/h3>\n<p><b>Which Cosmos DB feature provides automatic conflict resolution for multi-region writes?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Conflict resolution policy<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Request throttling<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Query metrics<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Index transformation<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Azure Cosmos DB conflict resolution policies determine how conflicting writes are handled in multi-region write configurations. Depending on the selected approach, conflicts can be resolved using supported automatic strategies or application-defined logic. Request throttling controls behavior when provisioned capacity is exceeded, query metrics provide information about query execution, and index transformation concerns indexing changes. Conflict resolution is important for globally distributed AI applications where several regional instances may update related data concurrently.<\/span><\/p>\n<h3><b>Question 363<\/b><\/h3>\n<p><b>Which Cosmos DB capability reports detailed request-unit consumption for queries?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Diagnostic logs<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Query metrics<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Change notifications<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Partition statistics<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Cosmos DB query metrics provide detailed information about query execution, including resource consumption characteristics that can help developers understand request-unit usage and query behavior. This information can assist with performance tuning and identifying expensive query patterns. Diagnostic logs provide broader operational information, change notifications expose modifications through supported mechanisms, and partition statistics provide partition-related information. Query metrics are particularly useful when optimizing AI applications that perform complex document retrieval and need to balance query performance against RU consumption.<\/span><\/p>\n<h3><b>Question 364<\/b><\/h3>\n<p><b>Which Blob Storage feature moves objects between access tiers automatically?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Lifecycle management<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Version retention<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Container recovery<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Inventory policy<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Azure Blob Storage lifecycle management can automatically move blobs between supported access tiers or delete them according to rule conditions such as age. This allows storage behavior to align with changing access patterns over an object&#8217;s lifetime. Version retention preserves earlier blob versions, container recovery protects against deletion, and inventory policies produce object reports. Lifecycle rules can be valuable for AI data platforms where recently generated datasets require frequent access but older training artifacts or historical files can transition to more economical storage.<\/span><\/p>\n<h3><b>Question 365<\/b><\/h3>\n<p><b>Which Azure Storage feature enables customer-controlled encryption keys?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Customer-managed key<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Platform secret<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Storage token<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Service credential<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Azure Storage supports customer-managed keys for scenarios where organizations require greater control over encryption-key management. Keys can be maintained through supported Azure key-management services, allowing customers to control key lifecycle operations such as rotation and access permissions. Platform-managed encryption remains available as the standard service-managed approach, while storage tokens and service credentials are authentication or authorization concepts rather than encryption-key controls. Customer-managed encryption can be important for AI workloads handling regulated or sensitive datasets with specific organizational security requirements.<\/span><\/p>\n<h3><b>Question 366<\/b><\/h3>\n<p><b>Which Service Bus feature moves repeatedly unsuccessful messages for separate inspection?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Dead-letter queue<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Transfer queue<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Session receiver<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Message browser<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The Service Bus dead-letter queue provides a separate location for messages that cannot be successfully processed or meet configured dead-letter conditions. Applications can inspect these messages later and determine whether they should be corrected, retried, or discarded. A transfer queue is associated with supported forwarding scenarios, a session receiver processes session-aware messages, and a message browser is not the standard Service Bus mechanism for isolating failed messages. Dead-lettering is important for resilient AI processing pipelines because problematic inputs can be separated from the normal processing stream.<\/span><\/p>\n<h3><b>Question 367<\/b><\/h3>\n<p><b>Which Service Bus capability keeps related messages associated with one processing context?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Session identifier<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Broker sequence<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Entity path<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Correlation token<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A Service Bus session identifier associates messages with a logical session so session-aware consumers can process related messages together. This can support ordered processing and stateful workflows where messages belong to the same business operation or conversation. Broker sequence numbers identify individual messages, entity paths identify Service Bus entities, and correlation tokens can be used for application-level relationship tracking. Session identifiers are useful for AI workflows involving ordered conversation events, job stages, or customer-specific processing sequences.<\/span><\/p>\n<h3><b>Question 368<\/b><\/h3>\n<p><b>Which Event Hubs setting identifies the logical destination within a namespace?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Event hub name<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Namespace quota<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Capture interval<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Consumer offset<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">An Event Hub name identifies a specific event stream within an Event Hubs namespace. Applications publish and consume events through the named event hub, while the namespace provides the broader resource boundary containing one or more event hubs. Capture interval controls supported capture timing, consumer offsets represent processing positions, and namespace quotas relate to service capacity. Naming event hubs appropriately is useful when an AI platform separates streams by workload, such as application telemetry, model events, operational messages, or user activity.<\/span><\/p>\n<h3><b>Question 369<\/b><\/h3>\n<p><b>Which Event Grid concept connects a publisher to an event-processing destination?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Event subscription<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Delivery endpoint<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Publisher identity<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Topic credential<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">An Event Grid event subscription defines how events from a topic or supported event source are delivered to a selected handler. It can include filtering and delivery-related configuration so that consumers receive appropriate events. A delivery endpoint represents where events are sent, while publisher identity and topic credential describe authentication or publishing concepts rather than the subscription object itself. Event subscriptions are fundamental to event-driven AI architectures because they connect resource or application events with processing functions, workflows, queues, or other supported handlers.<\/span><\/p>\n<h3><b>Question 370<\/b><\/h3>\n<p><b>Which Durable Functions pattern coordinates several independent activities before combining results?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Fan-out\/fan-in<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Chained execution<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Human interaction<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Monitor workflow<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The Durable Functions fan-out\/fan-in pattern starts multiple independent activities and later combines their results. It is useful when work can be performed concurrently but the workflow must wait for all required activities before proceeding. Chained execution handles sequential dependencies, human interaction patterns wait for external decisions, and monitor workflows repeatedly check conditions. Fan-out\/fan-in is well suited to AI batch scenarios such as processing multiple documents, evaluating several inputs, or running parallel transformations before creating one consolidated result.<\/span><\/p>\n<h3><b>Question 371<\/b><\/h3>\n<p><b>Which Azure Functions trigger starts execution when a queue message arrives?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Queue trigger<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Blob trigger<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Timer trigger<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Service endpoint<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">An Azure Functions queue trigger starts a function when a supported queue contains a message that meets the trigger&#8217;s processing conditions. This provides an event-driven mechanism for asynchronously processing queued workloads. A Blob trigger responds to supported blob changes, a Timer trigger invokes functions according to a schedule, and a service endpoint is a networking concept rather than a Functions trigger type. Queue-triggered functions are useful for AI workloads where incoming tasks need to be processed independently and asynchronously.<\/span><\/p>\n<h3><b>Question 372<\/b><\/h3>\n<p><b>Which Container Apps setting determines whether ingress is publicly reachable?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">External ingress<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Internal ingress<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Private routing<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Network exposure<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 2<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Azure Container Apps supports internal ingress for applications that should be reachable only within the appropriate Container Apps environment and networking context rather than being directly exposed through public ingress. External ingress is designed for publicly reachable application endpoints, while private routing and network exposure are broader networking concepts. Internal ingress can be useful for AI microservices that communicate with one another while keeping backend inference, preprocessing, or orchestration components inaccessible from the public internet.<\/span><\/p>\n<h3><b>Question 373<\/b><\/h3>\n<p><b>Which ACR feature supports pulling images using an immutable content reference?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Digest pinning<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Tag aliasing<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Repository mirroring<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Manifest labeling<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Digest pinning means referencing a container image by its content digest rather than relying on a mutable tag. Because the digest corresponds to specific image content, it provides a stable reference for reproducible deployments. Tag aliasing provides human-readable references, repository mirroring concerns copying or synchronizing content, and manifest labeling describes metadata concepts. Digest-based deployment is valuable for AI services because a production inference environment can be configured to run the exact container artifact that was tested and approved.<\/span><\/p>\n<h3><b>Question 374<\/b><\/h3>\n<p><b>Which Azure Monitor destination stores collected logs for KQL analysis?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Log Analytics workspace<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Metrics database<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Dashboard repository<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Alert archive<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A Log Analytics workspace stores supported Azure Monitor log data and provides a centralized environment where that data can be queried using Kusto Query Language. It supports investigation, troubleshooting, analytics, and monitoring workflows across many Azure resources and applications. Metrics are handled through different monitoring mechanisms, dashboards visualize information, and alert archives are not the primary centralized query store for Azure Monitor logs. A workspace is especially useful for AI platforms that need to correlate application, infrastructure, and security telemetry.<\/span><\/p>\n<h3><b>Question 375<\/b><\/h3>\n<p><b>Which Azure API Management policy can add a value to an HTTP header?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Set-header<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Forward-request<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Cache-lookup<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Rate-limit<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The API Management set-header policy modifies HTTP request or response headers according to the configured policy expression. It can be used to add, replace, or otherwise control supported header values as traffic passes through the gateway. Forward-request controls backend request forwarding behavior, cache lookup policies handle caching operations, and rate-limit policies control request frequency. Header manipulation can support AI APIs that need to pass correlation identifiers, routing information, or application-specific metadata between gateway and backend services.<\/span><\/p>\n<h3><b>Question 376<\/b><\/h3>\n<p><b>Which Azure SQL capability distributes databases across shared compute resources?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Elastic pool<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Hyperscale storage<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Serverless database<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Managed instance group<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Azure SQL elastic pools allow multiple databases to share a common pool of compute resources. This model can be useful when individual databases have varying usage patterns and do not all require their maximum capacity simultaneously. Hyperscale is a database architecture designed for large-scale workloads, serverless adjusts compute for supported workload patterns, and managed instance groups are not the relevant Azure SQL Database pooling mechanism. Elastic pools can help applications containing many AI-related databases manage fluctuating workloads more efficiently.<\/span><\/p>\n<h3><b>Question 377<\/b><\/h3>\n<p><b>Which PostgreSQL setting controls the maximum number of client connections?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Connection limit<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Backup retention<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Replica count<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Storage threshold<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A PostgreSQL connection limit controls how many client connections can be established according to the applicable server configuration and service constraints. Managing connection counts is important because excessive concurrent connections can consume resources and negatively affect database performance. Backup retention controls how long supported backups are retained, replica count concerns replicated instances, and storage thresholds relate to storage capacity. AI applications that create many concurrent requests should manage connection behavior carefully, often using connection pooling where appropriate.<\/span><\/p>\n<h3><b>Question 378<\/b><\/h3>\n<p><b>Which Microsoft Entra capability evaluates contextual conditions before granting access?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Conditional Access<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Application role<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Group membership<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Directory role<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Microsoft Entra Conditional Access evaluates contextual signals and configured conditions before allowing access to protected applications or resources. Policies can consider supported factors such as user identity, device state, location, application, and authentication strength. Application roles define application-specific permissions, group membership associates identities with groups, and directory roles provide administrative permissions. Conditional Access can provide an additional security layer for AI applications by requiring stronger authentication or imposing access restrictions when specific conditions are met.<\/span><\/p>\n<h3><b>Question 379<\/b><\/h3>\n<p><b>Which Azure Policy component determines what happens when a rule matches?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Policy effect<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Policy scope<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Policy metadata<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Policy parameter<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The Azure Policy effect determines the behavior applied when a policy rule evaluates a resource or operation. Supported effects can include actions such as auditing, denying, modifying, or deploying required resources, depending on the policy definition. Policy scope identifies where the policy applies, metadata contains descriptive information, and parameters provide configurable values. Understanding policy effects is important when designing governance for AI environments because the same compliance requirement can be implemented as an observation-only control or as an enforcement mechanism.<\/span><\/p>\n<h3><b>Question 380<\/b><\/h3>\n<p><b>Which Bicep feature returns a value from a deployment?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Output declaration<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Variable assignment<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Resource loop<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Parameter block<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 1<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">A Bicep output declaration returns a value from a deployment so that another deployment process, automation workflow, or dependent process can consume it. Outputs can expose values such as resource names, endpoints, or other calculated properties. Variables store reusable expressions inside the template, resource loops repeat declarations, and parameter blocks define deployment inputs. Outputs are useful in AI infrastructure deployments when newly created resources need to provide connection information or identifiers to subsequent automation stages without hard-coding those values.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>View Full Microsoft AI-200 Exam Dumps and Practice Test Dumps &nbsp; Question 361 Which Azure AI Search capability returns only selected document fields? Search mode Select clause Query type Scoring function Correct Answer: 2 Explanation: The $select parameter in Azure AI Search allows an application to specify which fields should be included in returned search [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[1648,1647],"tags":[],"_links":{"self":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/22833"}],"collection":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/comments?post=22833"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/22833\/revisions"}],"predecessor-version":[{"id":22834,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/22833\/revisions\/22834"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=22833"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=22833"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=22833"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}