{"id":22811,"date":"2026-09-26T08:02:09","date_gmt":"2026-09-26T08:02:09","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=22811"},"modified":"2026-09-26T08:02:09","modified_gmt":"2026-09-26T08:02:09","slug":"microsoft-ai-200-practice-test-questions-and-exam-dumps-part8-q141-160","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/microsoft-ai-200-practice-test-questions-and-exam-dumps-part8-q141-160\/","title":{"rendered":"Microsoft AI-200 Practice Test Questions and Exam Dumps Part8 Q141-160"},"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 141<\/b><\/h3>\n<p><b>Which Azure AI Search feature maps equivalent terms during queries?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Synonym map<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Skillset<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Index alias<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Analyzer<\/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 synonym map in Azure AI Search lets developers define equivalent or related terms so searches can match documents using alternate wording. For example, an application could associate terms such as \u201cautomobile\u201d and \u201ccar\u201d so users can retrieve relevant results despite using different terminology. Skillsets are used for enrichment, index aliases help applications switch between indexes, and analyzers process text during indexing or querying. Synonym maps are therefore useful when an AI application needs more flexible textual retrieval without changing the underlying documents.<\/span><\/p>\n<h3><b>Question 142<\/b><\/h3>\n<p><b>Which Azure AI Search feature adjusts relevance based on selected fields?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Indexer<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Scoring profile<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Data source<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Skill<\/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;\">A scoring profile in Azure AI Search allows developers to influence how matching documents are ranked based on selected fields or ranking functions. For example, an application might give greater importance to a product name than to a less important descriptive field. This helps tailor search relevance to application-specific requirements. An indexer imports content, a data source identifies the source repository, and a skill performs enrichment operations. Scoring profiles are particularly useful when default relevance ranking does not fully reflect the business importance of particular searchable fields.<\/span><\/p>\n<h3><b>Question 143<\/b><\/h3>\n<p><b>Which Azure AI Search component determines how text is tokenized?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Index alias<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Scoring profile<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Analyzer<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Data source<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">An analyzer in Azure AI Search determines how text is processed into searchable terms. Depending on its configuration, analysis can include tokenization, normalization, and language-specific processing. This affects how text is indexed and subsequently matched during searches. Index aliases provide an abstraction for switching indexes, scoring profiles influence relevance ranking, and data sources identify content repositories. Selecting an appropriate analyzer is important when building search applications because different languages and domain-specific terminology may require different text-processing behavior.<\/span><\/p>\n<h3><b>Question 144<\/b><\/h3>\n<p><b>Which Azure Cosmos DB capability supports analytical queries without affecting transactional containers?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Transactional batch<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Analytical store<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Time to Live<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Point reads<\/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 Cosmos DB analytical store is designed to support analytical workloads separately from the transactional store. It can provide an analytical representation of operational data so analytical processing does not need to compete directly with normal transactional queries against the operational container. Transactional batch provides atomic operations within a logical partition, TTL automatically expires items, and point reads retrieve individual items efficiently. Analytical store is useful when an AI solution needs to analyze operational data at scale while maintaining the responsiveness of its transactional workload.<\/span><\/p>\n<h3><b>Question 145<\/b><\/h3>\n<p><b>Which Azure Cosmos DB setting controls how long unused items remain automatically?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Partition key<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Indexing mode<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Default TTL<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Consistency level<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">The default TTL setting in Azure Cosmos DB establishes a default expiration period for items in a container when TTL is enabled. This allows applications to automatically remove data after a defined lifetime without implementing separate cleanup logic. Partition keys determine how data and workload are distributed, indexing mode controls indexing behavior, and consistency level determines how reads observe replicated data. Default TTL is especially useful for temporary records, event data, session information, or other content whose useful lifetime can be predetermined.<\/span><\/p>\n<h3><b>Question 146<\/b><\/h3>\n<p><b>Which Azure Service Bus feature sends a message to another entity after processing?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Message settlement<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Message forwarding<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Session locking<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Peek operation<\/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 Service Bus message forwarding allows messages from one queue or subscription to be automatically forwarded to another Service Bus entity. This can help construct messaging pipelines and route messages between logical processing stages without requiring an application to explicitly receive and resend every message. Message settlement controls completion or abandonment of received messages, session locking coordinates session processing, and peek allows applications to inspect messages without removing them. Message forwarding can therefore simplify routing architectures involving multiple queues or subscriptions.<\/span><\/p>\n<h3><b>Question 147<\/b><\/h3>\n<p><b>Which Azure Event Hubs setting increases capacity automatically as traffic rises?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Auto-inflate<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Consumer checkpoint<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Capture destination<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Partition key<\/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 Event Hubs auto-inflate can automatically increase throughput capacity when incoming traffic approaches the configured throughput limit. This helps applications accommodate temporary increases in event volume without manually scaling capacity every time demand changes. Consumer checkpoints track processing progress, Capture stores event data for later processing, and partition keys influence event distribution across partitions. Auto-inflate is useful for telemetry-heavy AI applications where traffic can vary significantly and maintaining sufficient ingestion capacity is important for continuous event processing.<\/span><\/p>\n<h3><b>Question 148<\/b><\/h3>\n<p><b>Which Azure Storage option copies blob data between storage accounts?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Blob lease<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Object replication<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Access tier<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Lifecycle rule<\/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 Blob Storage object replication asynchronously copies supported blob data between source and destination storage accounts. It can help maintain replicated copies for scenarios such as business continuity, geographic distribution, or read-oriented application architectures. A blob lease is used for coordination, access tiers manage storage costs based on access patterns, and lifecycle rules automate actions such as tiering or deletion. Object replication is therefore appropriate when an application needs copies of blob content maintained across separate storage accounts.<\/span><\/p>\n<h3><b>Question 149<\/b><\/h3>\n<p><b>Which Azure Functions setting configures runtime behavior through host.json?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Function endpoint<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Host-level configuration<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Storage container<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">DNS resolution<\/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 host.json file configures behavior for an Azure Functions application at the host or runtime level. Depending on the extension and workload, it can control settings related to functions runtime behavior, bindings, logging, concurrency, and other host capabilities. Function endpoints define how triggers are exposed, storage containers hold application data, and DNS resolution handles name-to-address mapping. Understanding host.json is important when tuning a Functions application because some runtime behaviors are configured globally rather than independently inside each function.<\/span><\/p>\n<h3><b>Question 150<\/b><\/h3>\n<p><b>Which Azure Functions feature supports dependency injection in supported runtimes?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Service registration<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Dependency injection<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Storage binding<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Trigger metadata<\/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 Functions supports dependency injection in supported development models, allowing application services and dependencies to be registered and provided to function components. This approach can improve modularity, testing, and separation of concerns by avoiding hard-coded construction of dependencies inside every function. Storage bindings connect functions with supported storage resources, trigger metadata describes invocation information, and service registration is the configuration mechanism used to establish dependencies. Dependency injection is particularly useful in larger AI applications where functions interact with multiple application services.<\/span><\/p>\n<h3><b>Question 151<\/b><\/h3>\n<p><b>Which Azure Container Apps feature exposes an application only within its environment?<\/b><\/p>\n<ol>\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;\">External endpoint<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Registry credential<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Revision label<\/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;\">Internal ingress in Azure Container Apps allows an application to receive traffic only from within the configured Container Apps environment and associated private network context. This is useful for backend services that should not be directly exposed to public internet traffic. An external endpoint provides public accessibility, registry credentials authenticate access to container images, and revision labels help identify deployed revisions. Internal ingress is therefore appropriate for microservices that need communication with other application components while remaining inaccessible through a public endpoint.<\/span><\/p>\n<h3><b>Question 152<\/b><\/h3>\n<p><b>Which Azure Resource Graph tool is designed for querying resource metadata at scale?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Resource locks<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Resource Graph Explorer<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Cost alerts<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Deployment history<\/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 Resource Graph Explorer provides an interactive interface for querying Azure resource metadata across subscriptions and other supported scopes. It uses Azure Resource Graph queries to help administrators and developers discover, filter, and analyze resource information efficiently. Resource locks protect resources from certain modifications, cost alerts monitor spending conditions, and deployment history records deployment activity. Resource Graph Explorer is useful when an AI solution spans many Azure resources and developers need a centralized way to inspect resource properties without opening each service individually.<\/span><\/p>\n<h3><b>Question 153<\/b><\/h3>\n<p><b>Which Azure Monitor feature stores platform diagnostic data for analysis?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Diagnostic setting<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Data collection endpoint<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Action group<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Workbook<\/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 Monitor diagnostic settings define which platform logs and metrics should be collected and where that data should be sent. Destinations can include supported monitoring or storage services, allowing organizations to retain and analyze diagnostic information according to their operational requirements. Data collection endpoints support specific data ingestion architectures, action groups define notification or automation responses, and workbooks present telemetry visually. Diagnostic settings are therefore a key configuration point when an AI application needs centralized monitoring data from Azure resources.<\/span><\/p>\n<h3><b>Question 154<\/b><\/h3>\n<p><b>Which Azure App Configuration capability supports gradual feature rollout?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Configuration snapshot<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Feature filter<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Connection string<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Secret identifier<\/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 App Configuration feature filters allow feature flags to use rules that determine whether a feature should be enabled for a particular request or audience. This supports controlled rollouts where functionality can be introduced gradually rather than activated for every user simultaneously. A configuration snapshot represents configuration state, a connection string provides connection information, and a secret identifier references sensitive configuration. Feature filters are valuable for AI applications that need controlled experimentation, staged deployments, or audience-specific feature activation.<\/span><\/p>\n<h3><b>Question 155<\/b><\/h3>\n<p><b>Which Azure API Management feature lets developers reuse policy logic?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">API revision<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Subscription product<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Policy fragment<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Backend pool<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Azure API Management policy fragments allow reusable policy statements to be defined once and incorporated into multiple API policies. This can reduce duplication when several APIs require common processing such as header manipulation, validation, transformation, or other supported policy operations. API revisions represent versions of an API configuration, products group APIs for consumers, and backend pools represent backend connectivity concepts. Policy fragments are useful for maintaining consistent gateway behavior across larger AI applications that expose multiple APIs through Azure API Management.<\/span><\/p>\n<h3><b>Question 156<\/b><\/h3>\n<p><b>Which Azure SQL feature captures historical query execution information?<\/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;\">Query Store<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Firewall policy<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Service tier<\/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;\">Query Store in Azure SQL Database captures query-related performance information over time. It can help developers investigate query behavior, identify performance changes, and understand which queries consume resources. An elastic pool provides shared database resources, firewall policies control network access, and the service tier determines available database capabilities and resources. Query Store is particularly useful during performance troubleshooting because it provides historical information rather than only showing what is happening during a single monitoring session.<\/span><\/p>\n<h3><b>Question 157<\/b><\/h3>\n<p><b>Which Azure AI Search feature provides vector representations during indexing?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Index alias<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Semantic caption<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Integrated vectorization<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Search suggestion<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 3<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Integrated vectorization in Azure AI Search can automate aspects of converting source content into vector representations during indexing workflows. This helps applications build vector-search experiences without requiring every vectorization step to be implemented independently in application code. Index aliases help manage index references, semantic captions provide concise passages from search results, and search suggestions assist users while entering queries. Integrated vectorization is useful for AI applications that need semantic retrieval from documents and want ingestion and vector preparation to form part of the search pipeline.<\/span><\/p>\n<h3><b>Question 158<\/b><\/h3>\n<p><b>Which Azure Container Registry capability builds container images from source code?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Repository scope<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Image manifest<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Registry webhook<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">ACR Tasks<\/span><\/li>\n<\/ol>\n<p><b>Correct Answer: 4<\/b><\/p>\n<p><b>Explanation:<\/b><\/p>\n<p><span style=\"font-weight: 400;\">Azure Container Registry Tasks provides managed capabilities for building container images in Azure Container Registry. Tasks can automate image builds and can be integrated into development workflows so container images can be produced without requiring a dedicated build server. Repository scope controls permissions, image manifests describe image metadata and layers, and registry webhooks can notify external systems about registry events. ACR Tasks is useful for AI applications that need repeatable container image builds as part of an automated cloud development and deployment process.<\/span><\/p>\n<h3><b>Question 159<\/b><\/h3>\n<p><b>Which Azure Storage mechanism removes old blob data according to defined rules?<\/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;\">Blob lease<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Object replication<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Static website<\/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 lets administrators define rules that automatically transition or delete blobs according to conditions such as age, access patterns, or blob state. This can reduce storage costs and automate retention processes for data that becomes less valuable over time. Blob leases provide coordination, object replication creates copies between supported storage accounts, and static website hosting serves web content. Lifecycle management is especially useful for AI workloads that generate large amounts of intermediate or historical data and need predictable retention behavior.<\/span><\/p>\n<h3><b>Question 160<\/b><\/h3>\n<p><b>Which Azure Service Bus operation lets an application inspect a message without removing it?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Complete<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Peek<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Abandon<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Dead-letter<\/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 Peek operation in Azure Service Bus allows an application to inspect messages without receiving them for normal processing and without removing them from the entity. This can be useful for diagnostics, message inspection, or examining queued content without changing its delivery state. Complete settles a successfully processed message, Abandon releases a received message for possible redelivery, and Dead-letter moves a message into the dead-letter subqueue. Peek is therefore appropriate when an application needs visibility into queued messages without altering their processing lifecycle.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>View Full Microsoft AI-200 Exam Dumps and Practice Test Dumps &nbsp; Question 141 Which Azure AI Search feature maps equivalent terms during queries? Synonym map Skillset Index alias Analyzer Correct Answer: 1 Explanation: A synonym map in Azure AI Search lets developers define equivalent or related terms so searches can match documents using alternate wording. [&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\/22811"}],"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=22811"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/22811\/revisions"}],"predecessor-version":[{"id":22812,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/22811\/revisions\/22812"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=22811"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=22811"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=22811"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}