{"id":13373,"date":"2026-09-16T08:04:10","date_gmt":"2026-09-16T08:04:10","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=13373"},"modified":"2026-09-16T08:04:10","modified_gmt":"2026-09-16T08:04:10","slug":"microsoft-ab-100-practice-test-questions-and-exam-dumps-part12-q221-240","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/microsoft-ab-100-practice-test-questions-and-exam-dumps-part12-q221-240\/","title":{"rendered":"Microsoft AB-100 Practice Test Questions and Exam Dumps Part12 Q221-240"},"content":{"rendered":"<h1><\/h1>\n<h2><b>View Full <\/b><a href=\"https:\/\/www.examlabs.com\/ab-100-exam-dumps\"><b>Microsoft AB-100 Exam Dumps<\/b><\/a><b> and Practice Test Dumps.<\/b><\/h2>\n<p>&nbsp;<\/p>\n<h3><b>Question 221<\/b><\/h3>\n<p><b>What is the primary purpose of an agent&#8217;s short-term memory?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Store permanent business records<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Replace the knowledge base<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Manage information relevant to the current task or conversation<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Define user permissions<\/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;\">Short-term memory allows an AI agent to retain information that is relevant during an active conversation or task. This can include recent user messages, intermediate results, decisions, and temporary task state. It helps the agent maintain continuity without repeatedly asking the user for information. Short-term memory differs from long-term storage because its contents are generally associated with the current interaction or workflow. Persistent business information should instead be stored in appropriate systems such as databases, knowledge repositories, or enterprise applications.<\/span><\/p>\n<h3><b>Question 222<\/b><\/h3>\n<p><b>An agent must remember a customer&#8217;s preferences across multiple conversations. Which capability is most appropriate?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Long-term memory<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Token compression<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Prompt formatting<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Load balancing<\/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;\">Long-term memory is appropriate when an agent needs to retain useful information across separate sessions or conversations. Customer preferences, previously confirmed settings, or other durable context can be stored in an approved persistent data source and retrieved when needed. The implementation should still follow privacy, retention, and access-control requirements. Short-term conversation context is not designed for durable storage across sessions. Properly designed long-term memory helps provide continuity while keeping persistent information under appropriate governance and security controls.<\/span><\/p>\n<h3><b>Question 223<\/b><\/h3>\n<p><b>A customer-service agent receives a request, checks an order system, and then creates a return request. Which capability coordinates these steps?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Data classification<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Agent planning<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Model fine-tuning<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Content filtering<\/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;\">Agent planning enables an agent to determine and coordinate multiple steps required to complete a goal. In this scenario, the agent needs to understand the customer&#8217;s request, retrieve order information, determine whether the request is valid, and then initiate the return process. Planning can involve selecting tools, maintaining task state, and determining the sequence of actions. This differs from simply generating a response because the agent must coordinate actions and intermediate results before completing the requested business process.<\/span><\/p>\n<h3><b>Question 224<\/b><\/h3>\n<p><b>Why should an AI agent validate tool outputs before using them?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To increase token limits<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To make the model larger<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To remove authentication requirements<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">To detect invalid, unexpected, or unsafe results<\/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;\">Tool output validation helps prevent an agent from blindly trusting information returned by external systems or APIs. A tool may return incomplete, malformed, outdated, or unexpected data because of service failures or incorrect inputs. Validation can check required fields, data types, allowed values, and business rules before the information is used in later reasoning or actions. This improves reliability and reduces the chance that an incorrect tool response will cause an inappropriate answer or business operation.<\/span><\/p>\n<h3><b>Question 225<\/b><\/h3>\n<p><b>Which mechanism is commonly used to protect an API from excessive request volume?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Rate limiting<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Prompt chaining<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Embedding generation<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Context expansion<\/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;\">Rate limiting controls how many requests a client, user, or application can make to an API within a defined period. It helps protect services from excessive traffic, accidental request loops, and resource exhaustion. AI agents that call APIs repeatedly can encounter rate limits, so architects should also consider retry policies and backoff strategies. Proper rate limiting supports service reliability and predictable capacity. It should be combined with authentication and authorization rather than being treated as a replacement for access control.<\/span><\/p>\n<h3><b>Question 226<\/b><\/h3>\n<p><b>An external API occasionally returns temporary errors. What should an agent architecture typically use to handle these failures?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Permanent data deletion<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Retry with appropriate backoff<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Larger prompts<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Manual model retraining<\/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;\">Temporary service failures can often be handled through controlled retries with an appropriate backoff strategy. Instead of immediately sending repeated requests, the system waits progressively longer between attempts, reducing pressure on the unavailable service. Retry limits should also be defined to prevent endless loops. For persistent failures, the agent can use a fallback service or escalate to a human. The retry strategy should consider the API&#8217;s documented behavior, especially whether repeated operations are safe and whether requests are idempotent.<\/span><\/p>\n<h3><b>Question 227<\/b><\/h3>\n<p><b>What is the main benefit of an idempotent operation in an agent workflow?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">It guarantees zero latency<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">It removes authentication<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Repeating the same operation does not create unintended additional effects<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">It increases model context automatically<\/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 idempotent operation can be safely repeated without causing additional unintended effects after the first successful execution. This is especially important when agents retry API calls because network failures may make it unclear whether the original request succeeded. For example, a carefully designed transaction operation can use a unique request identifier to prevent duplicate records. Idempotency therefore improves reliability in automated workflows and reduces the risk of duplicate purchases, tickets, records, or other business actions.<\/span><\/p>\n<h3><b>Question 228<\/b><\/h3>\n<p><b>A company wants an agent to access an internal application without storing a user&#8217;s password in the agent configuration. Which approach should be considered?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Managed identity or another secure workload identity<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Hard-coded password<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Password in the system prompt<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Plain-text credential file<\/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;\">Managed identities and other secure workload identity mechanisms allow applications and services to authenticate without embedding long-lived passwords directly into configuration files or prompts. Access can then be controlled through appropriate permissions and role assignments. This reduces credential exposure and simplifies credential management. The exact identity mechanism depends on the platform and architecture, but secrets should not be placed in prompts, source code, or plain-text files. Agents should receive only the permissions required for their approved business operations.<\/span><\/p>\n<h3><b>Question 229<\/b><\/h3>\n<p><b>Which search approach combines keyword matching with semantic similarity?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Exact-match search<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Hybrid search<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">File compression<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Static prompting<\/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;\">Hybrid search combines traditional keyword-based retrieval with semantic search techniques such as vector similarity. Keyword matching is useful when exact terms, identifiers, product codes, or names matter, while semantic search can find conceptually related content even when wording differs. Combining both approaches can improve retrieval quality for enterprise knowledge scenarios. The final architecture may also use filtering or reranking to improve results. Hybrid retrieval is particularly useful when a knowledge base contains both structured terminology and natural-language documents.<\/span><\/p>\n<h3><b>Question 230<\/b><\/h3>\n<p><b>A RAG system retrieves many documents, but only a few are actually relevant. Which improvement can help?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Increase unrelated context<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Remove all metadata<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Improve retrieval and reranking<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Disable the knowledge 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;\">When retrieval returns too many irrelevant documents, improving retrieval quality and reranking can help prioritize information that is most useful for the user&#8217;s query. Techniques may include better query formulation, metadata filtering, hybrid search, improved embeddings, and reranking retrieved results. Providing large amounts of irrelevant context can increase token usage and may reduce answer quality. The goal is to provide the model with a smaller set of high-quality evidence that directly supports the requested answer.<\/span><\/p>\n<h3><b>Question 231<\/b><\/h3>\n<p><b>What does a context window determine for a language model?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">The maximum amount of information it can process as context for a request<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">The number of users in an organization<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">The number of API keys available<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">The database storage capacity<\/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 model&#8217;s context window defines how much input and relevant conversational or retrieved information can be processed within a request, subject to the model&#8217;s limits. This may include system instructions, user messages, conversation history, retrieved documents, and other context. If an application provides excessive information, it may need summarization, truncation, or selective retrieval. Context-window capacity is therefore an important architectural consideration when designing agents that handle long conversations or large knowledge sources.<\/span><\/p>\n<h3><b>Question 232<\/b><\/h3>\n<p><b>An agent must answer questions using only approved company documents. What should the architecture emphasize?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Random web results<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Unrestricted user uploads<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Uncontrolled model memory<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Controlled knowledge sources and grounding<\/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;\">Controlled knowledge sources and grounding help ensure that the agent bases its responses on approved company information. The architecture should define which repositories are trusted, how documents are indexed and retrieved, and which users can access particular content. Retrieval should respect existing permissions and data boundaries. Grounding can reduce unsupported responses by providing relevant evidence to the model. Governance should also address document freshness, ownership, retention, and procedures for removing outdated or unauthorized information from the knowledge system.<\/span><\/p>\n<h3><b>Question 233<\/b><\/h3>\n<p><b>Which technique can reduce the amount of irrelevant content placed into an agent&#8217;s context?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Query rewriting and targeted retrieval<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Increasing all document sizes<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Disabling retrieval<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Adding every available document<\/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;\">Query rewriting and targeted retrieval can improve the relevance of information supplied to an agent. A rewritten query can clarify the user&#8217;s intent and help the retrieval system locate more appropriate documents. Filters based on metadata, permissions, dates, or document types can further reduce unnecessary results. Sending every available document to the model increases context consumption and can introduce conflicting or irrelevant information. Targeted retrieval therefore supports better answer quality, lower token usage, and more efficient agent operation.<\/span><\/p>\n<h3><b>Question 234<\/b><\/h3>\n<p><b>A business needs to classify incoming support requests into predefined categories. Which AI approach is generally suitable?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Image generation<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Classification<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Speech synthesis<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Vector storage<\/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;\">Classification is designed to assign inputs to predefined categories based on their characteristics. For example, support requests could be classified as billing, technical support, account access, or shipping issues. A classification model or appropriately configured AI capability can perform this task efficiently. The architecture should define the allowed categories and establish evaluation criteria for accuracy. Generative AI may also be involved in broader workflows, but a straightforward categorization requirement does not necessarily require a complex autonomous agent.<\/span><\/p>\n<h3><b>Question 235<\/b><\/h3>\n<p><b>What is a key reason to use a model catalog when selecting an AI model?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">It automatically approves every model<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">It replaces security testing<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">It provides information for comparing available models and capabilities<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">It eliminates deployment requirements<\/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;\">A model catalog can provide information about available models, supported capabilities, deployment options, performance characteristics, and other relevant attributes. This helps architects compare models against business requirements such as accuracy, latency, cost, context capacity, and supported workloads. Model selection should still include security, compliance, licensing, and evaluation considerations. A catalog supports informed selection but does not automatically determine which model is appropriate. Organizations should validate candidate models against representative workloads before production adoption.<\/span><\/p>\n<h3><b>Question 236<\/b><\/h3>\n<p><b>An organization wants to reduce AI costs while maintaining acceptable response quality. Which strategy can help?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Route simple requests to smaller models<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Send every request to the largest model<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Increase prompt length unnecessarily<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Disable monitoring<\/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;\">Routing simple workloads to smaller or less expensive models can reduce AI costs while preserving appropriate quality. More capable models can remain available for complex requests that require advanced reasoning or larger context. A model-routing strategy should be based on tested criteria rather than assumptions. Organizations can evaluate accuracy, latency, token consumption, and business impact for representative requests. Cost monitoring should continue after deployment because workload patterns may change and model usage can increase over time.<\/span><\/p>\n<h3><b>Question 237<\/b><\/h3>\n<p><b>Which control helps prevent an agent from accessing data outside its assigned business function?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Larger context windows<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Broader API permissions<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Unrestricted connectors<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Role-based access control<\/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;\">Role-based access control, or RBAC, can restrict an agent or its associated identity to permissions appropriate for its assigned responsibilities. This supports the principle of least privilege by preventing unnecessary access to applications, records, or operations. RBAC should be combined with authentication, authorization checks, and appropriate data-level controls where required. Increasing an agent&#8217;s permissions simply to make integrations easier can create unnecessary security exposure. Access should therefore be explicitly designed around the agent&#8217;s legitimate business tasks.<\/span><\/p>\n<h3><b>Question 238<\/b><\/h3>\n<p><b>What should an AI team establish before moving an agent from pilot to production?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Only a larger prompt<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Production readiness criteria<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Unlimited user access<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Removal of monitoring<\/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;\">Production readiness criteria provide measurable requirements that an agent should satisfy before deployment to real users. These can include accuracy, groundedness, latency, reliability, security, privacy, cost, monitoring, failure handling, and business acceptance criteria. Testing should use representative scenarios rather than only successful demonstrations. Clear readiness gates reduce the chance of deploying an immature solution. They also provide stakeholders with a consistent basis for deciding whether the system has met the technical and business requirements established for production use.<\/span><\/p>\n<h3><b>Question 239<\/b><\/h3>\n<p><b>An agent produces incorrect answers after a major change to its retrieval pipeline. What should the team investigate first?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Retrieval and evaluation results before and after the change<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">User interface colors<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Office network printers<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Employee vacation schedules<\/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 significant retrieval change can alter which evidence is provided to the model, directly affecting answer quality. The team should compare evaluation results before and after the change and inspect retrieval relevance, document coverage, ranking, filters, and grounding behavior. Representative test cases can help identify whether the problem affects specific query types or the overall system. Monitoring and evaluation data provide evidence for diagnosing the regression. Changes should be validated systematically before being promoted to production environments.<\/span><\/p>\n<h3><b>Question 240<\/b><\/h3>\n<p><b>Why is versioning important for AI prompts and agent configurations?<\/b><\/p>\n<ol>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">It prevents all model errors<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">It removes the need for testing<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">It allows teams to track and reproduce changes<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">It guarantees lower operating costs<\/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;\">Versioning allows teams to track changes to prompts, agent instructions, configurations, tools, and related assets over time. When behavior changes, teams can identify what was modified and reproduce earlier configurations for comparison or rollback. Versioning also supports controlled testing and collaboration across development environments. It does not guarantee that an AI system will be accurate or inexpensive. Combining version control with evaluation, deployment gates, monitoring, and documented change management creates a more reliable lifecycle for AI solutions.<\/span><\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>View Full Microsoft AB-100 Exam Dumps and Practice Test Dumps. &nbsp; Question 221 What is the primary purpose of an agent&#8217;s short-term memory? Store permanent business records Replace the knowledge base Manage information relevant to the current task or conversation Define user permissions Correct Answer: 3 Explanation Short-term memory allows an AI agent to retain [&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\/13373"}],"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=13373"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/13373\/revisions"}],"predecessor-version":[{"id":13390,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/13373\/revisions\/13390"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=13373"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=13373"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=13373"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}