{"id":13380,"date":"2026-09-16T08:02:39","date_gmt":"2026-09-16T08:02:39","guid":{"rendered":"https:\/\/www.examlabs.com\/certification\/?p=13380"},"modified":"2026-09-16T08:02:39","modified_gmt":"2026-09-16T08:02:39","slug":"microsoft-ab-100-practice-test-questions-and-exam-dumps-part18-q341-360","status":"publish","type":"post","link":"https:\/\/www.examlabs.com\/certification\/microsoft-ab-100-practice-test-questions-and-exam-dumps-part18-q341-360\/","title":{"rendered":"Microsoft AB-100 Practice Test Questions and Exam Dumps Part18 Q341-360"},"content":{"rendered":"

<\/h1>\n

View Full <\/b>Microsoft AB-100 Exam Dumps<\/b><\/a> and Practice Test Dumps.<\/b><\/h2>\n

 <\/p>\n

Question 341<\/b><\/h3>\n

What is the primary purpose of agent memory?<\/b><\/p>\n

    \n
  1. Manage information that an agent needs to retain during or across tasks<\/span><\/li>\n
  2. Increase API quotas<\/span><\/li>\n
  3. Replace authorization<\/span><\/li>\n
  4. Encrypt databases<\/span><\/li>\n<\/ol>\n

    Correct Answer: 1<\/b><\/p>\n

    Explanation<\/b><\/p>\n

    Agent memory allows an AI agent to retain useful information needed to continue tasks or provide continuity across interactions. Depending on the architecture, memory can include short-term conversation context, task state, or approved long-term information. Memory should be designed around the actual business requirement and should follow privacy, retention, and access-control policies. Storing unnecessary information can create additional risk. Architects should also determine what information should be forgotten, summarized, or retained and for how long.<\/span><\/p>\n

    Question 342<\/b><\/h3>\n

    Which type of memory is most appropriate for information needed only during the current conversation?<\/b><\/p>\n

      \n
    1. Long-term memory<\/span><\/li>\n
    2. Short-term memory<\/span><\/li>\n
    3. Permanent database storage<\/span><\/li>\n
    4. Archived storage<\/span><\/li>\n<\/ol>\n

      Correct Answer: 2<\/b><\/p>\n

      Explanation<\/b><\/p>\n

      Short-term memory is designed for information needed during an active interaction or task. It can contain recent conversation messages, temporary decisions, intermediate results, and task context. This information helps the agent maintain continuity without repeatedly requesting the same details. Long-term memory is more appropriate when information must persist across separate sessions. The architecture should define retention behavior clearly because not every piece of conversation data should be stored permanently. Privacy and data-minimization requirements should also guide memory design.<\/span><\/p>\n

      Question 343<\/b><\/h3>\n

      A customer asks an agent to remember a preference for future conversations. What capability is relevant?<\/b><\/p>\n

        \n
      1. Long-term memory<\/span><\/li>\n
      2. API throttling<\/span><\/li>\n
      3. Prompt injection<\/span><\/li>\n
      4. Model routing<\/span><\/li>\n<\/ol>\n

        Correct Answer: 1<\/b><\/p>\n

        Explanation<\/b><\/p>\n

        Long-term memory can store approved information that should remain available across separate conversations. In this example, a customer preference may be stored in an appropriate persistent system and retrieved during future interactions. The organization should determine what information is appropriate to retain and establish consent, privacy, access, and retention controls where applicable. Long-term memory should not become an unrestricted storage mechanism for all conversation content. Only information with a legitimate business purpose should generally be retained.<\/span><\/p>\n

        Question 344<\/b><\/h3>\n

        Which capability helps an agent maintain the current progress of a multi-step workflow?<\/b><\/p>\n

          \n
        1. Task state<\/span><\/li>\n
        2. Model catalog<\/span><\/li>\n
        3. Data residency<\/span><\/li>\n
        4. Embedding refresh<\/span><\/li>\n<\/ol>\n

          Correct Answer: 1<\/b><\/p>\n

          Explanation<\/b><\/p>\n

          Task state records information needed to understand the current position of an agent within a workflow. It can identify completed actions, pending steps, retrieved values, decisions, and other information required to continue processing. Maintaining task state is particularly useful when workflows involve multiple tools or agents. It can prevent duplicated actions and help an agent resume work after an interruption. Task state should be protected appropriately because it may contain business information or other sensitive details related to the workflow.<\/span><\/p>\n

          Question 345<\/b><\/h3>\n

          An agent needs to call three independent APIs. Which approach may reduce total execution time?<\/b><\/p>\n

            \n
          1. Sequential execution<\/span><\/li>\n
          2. Parallel execution<\/span><\/li>\n
          3. Repeated retries<\/span><\/li>\n
          4. Manual approval for every call<\/span><\/li>\n<\/ol>\n

            Correct Answer: 2<\/b><\/p>\n

            Explanation<\/b><\/p>\n

            Parallel execution can reduce total execution time when multiple API calls are independent and do not depend on each other’s results. Instead of waiting for one call to complete before starting another, the orchestration layer can initiate the operations concurrently. The architecture must still consider API quotas, concurrency limits, failures, and resource capacity. If one operation depends on another, sequential execution remains necessary. Properly identifying dependencies allows teams to improve performance without compromising workflow correctness.<\/span><\/p>\n

            Question 346<\/b><\/h3>\n

            What should an AI agent use to determine whether a tool call is allowed?<\/b><\/p>\n

              \n
            1. Authorization and permission controls<\/span><\/li>\n
            2. Model temperature<\/span><\/li>\n
            3. Context window size<\/span><\/li>\n
            4. Document chunk size<\/span><\/li>\n<\/ol>\n

              Correct Answer: 1<\/b><\/p>\n

              Explanation<\/b><\/p>\n

              Authorization and permission controls should determine whether an agent is allowed to execute a particular tool operation. Natural-language instructions can describe boundaries, but technical controls should enforce them. Permissions should follow least privilege so the agent receives only the access needed for its assigned tasks. Tool-level authorization can prevent an agent from performing sensitive operations even if a user or malicious input attempts to instruct it to do so. Logging and monitoring should also record important tool actions for accountability.<\/span><\/p>\n

              Question 347<\/b><\/h3>\n

              Why is tool input validation important?<\/b><\/p>\n

                \n
              1. It prevents malformed or unsafe values from reaching backend systems<\/span><\/li>\n
              2. It guarantees perfect model reasoning<\/span><\/li>\n
              3. It removes the need for authorization<\/span><\/li>\n
              4. It increases model context automatically<\/span><\/li>\n<\/ol>\n

                Correct Answer: 1<\/b><\/p>\n

                Explanation<\/b><\/p>\n

                Tool input validation checks whether values provided by an agent meet expected formats, ranges, types, and business rules before the tool executes. This can prevent malformed requests, invalid identifiers, unexpected commands, or potentially unsafe values from reaching backend systems. Validation should be implemented at the tool or service boundary rather than relying only on model instructions. Authorization remains necessary because a correctly formatted request may still be unauthorized. Together, validation and authorization provide stronger protection for automated actions.<\/span><\/p>\n

                Question 348<\/b><\/h3>\n

                Which technique can help reduce the number of tokens sent in a long-running conversation?<\/b><\/p>\n

                  \n
                1. Context summarization<\/span><\/li>\n
                2. Unlimited history<\/span><\/li>\n
                3. Adding duplicate documents<\/span><\/li>\n
                4. Increasing prompt repetition<\/span><\/li>\n<\/ol>\n

                  Correct Answer: 1<\/b><\/p>\n

                  Explanation<\/b><\/p>\n

                  Context summarization can condense older conversation information while retaining details that remain important to the current task. This reduces the amount of conversation history that must be included in future model requests and can help manage context-window limits and token costs. The summary should preserve important facts, decisions, constraints, and unresolved tasks. Teams should evaluate summarization quality because losing a critical detail can cause incorrect behavior. Summarization can be combined with selective retrieval and task-state management.<\/span><\/p>\n

                  Question 349<\/b><\/h3>\n

                  A company wants to prevent an agent from using an outdated policy document. Which control is most useful?<\/b><\/p>\n

                    \n
                  1. Document freshness management<\/span><\/li>\n
                  2. Higher model temperature<\/span><\/li>\n
                  3. Larger context windows<\/span><\/li>\n
                  4. Unlimited retrieval<\/span><\/li>\n<\/ol>\n

                    Correct Answer: 1<\/b><\/p>\n

                    Explanation<\/b><\/p>\n

                    Document freshness management helps ensure that outdated or superseded information is not used as authoritative knowledge. Organizations can use effective dates, document status, ownership, review schedules, and automated ingestion processes to keep knowledge repositories current. Outdated documents can be removed, archived, or excluded from retrieval when appropriate. This is especially important for policies, pricing, procedures, and other information that changes frequently. Retrieval quality should be monitored because a technically functioning search system can still produce incorrect answers from stale content.<\/span><\/p>\n

                    Question 350<\/b><\/h3>\n

                    What is a key purpose of reranking in a RAG pipeline?<\/b><\/p>\n

                      \n
                    1. Put the most relevant retrieved content first<\/span><\/li>\n
                    2. Increase user permissions<\/span><\/li>\n
                    3. Replace all source documents<\/span><\/li>\n
                    4. Disable semantic search<\/span><\/li>\n<\/ol>\n

                      Correct Answer: 1<\/b><\/p>\n

                      Explanation<\/b><\/p>\n

                      Reranking evaluates retrieved candidates and reorders them according to their relevance to the user’s request. An initial retrieval step may return several potentially useful documents, but some may be more relevant than others. Reranking helps prioritize stronger evidence before the context is provided to the language model. This can improve answer quality and reduce irrelevant context. Reranking should work alongside appropriate indexing, query processing, access controls, and evaluation rather than being treated as a replacement for the retrieval system.<\/span><\/p>\n

                      Question 351<\/b><\/h3>\n

                      Which search method combines semantic and keyword-based retrieval?<\/b><\/p>\n

                        \n
                      1. Hybrid search<\/span><\/li>\n
                      2. Static search<\/span><\/li>\n
                      3. Manual search<\/span><\/li>\n
                      4. Random search<\/span><\/li>\n<\/ol>\n

                        Correct Answer: 1<\/b><\/p>\n

                        Explanation<\/b><\/p>\n

                        Hybrid search combines keyword-based matching with semantic retrieval methods. Keyword matching can be effective for exact names, identifiers, codes, and terminology, while semantic retrieval can identify content with related meaning even when the wording differs. Combining the approaches can improve retrieval quality across diverse enterprise content. Additional filtering and reranking may further improve results. The effectiveness of hybrid search should be measured using representative queries because the best retrieval configuration depends on the organization’s data, terminology, and business requirements.<\/span><\/p>\n

                        Question 352<\/b><\/h3>\n

                        What should an organization consider when selecting chunk sizes for RAG documents?<\/b><\/p>\n

                          \n
                        1. Content structure and retrieval requirements<\/span><\/li>\n
                        2. Only the model’s name<\/span><\/li>\n
                        3. User password length<\/span><\/li>\n
                        4. Number of employees<\/span><\/li>\n<\/ol>\n

                          Correct Answer: 1<\/b><\/p>\n

                          Explanation<\/b><\/p>\n

                          Chunk size should be selected based on the structure of the source content and the type of information users need to retrieve. Very large chunks may contain unnecessary information and consume more context, while very small chunks may separate related concepts and reduce useful context. Appropriate overlap can help preserve continuity between sections. Teams should test different approaches using representative queries and retrieval evaluations. Metadata, document structure, and expected answer requirements should also influence the chunking strategy.<\/span><\/p>\n

                          Question 353<\/b><\/h3>\n

                          Which feature can help an agent retrieve only records the current user is permitted to access?<\/b><\/p>\n

                            \n
                          1. Access-aware retrieval<\/span><\/li>\n
                          2. Temperature adjustment<\/span><\/li>\n
                          3. Prompt repetition<\/span><\/li>\n
                          4. Model compression<\/span><\/li>\n<\/ol>\n

                            Correct Answer: 1<\/b><\/p>\n

                            Explanation<\/b><\/p>\n

                            Access-aware retrieval applies user or service permissions when selecting information for an agent. The retrieval layer should ensure that documents or records are returned only when the requesting identity is authorized to access them. This is particularly important in enterprise RAG systems where a common knowledge index may contain information belonging to different departments or users. Authorization should be enforced technically rather than relying on the model to hide unauthorized content. Access-aware retrieval should also be tested with users having different permission levels.<\/span><\/p>\n

                            Question 354<\/b><\/h3>\n

                            An agent needs current inventory information before recommending products. Which approach is most appropriate?<\/b><\/p>\n

                              \n
                            1. Retrieve current inventory through an approved data connection<\/span><\/li>\n
                            2. Rely only on model training<\/span><\/li>\n
                            3. Store inventory permanently in the system prompt<\/span><\/li>\n
                            4. Ignore inventory changes<\/span><\/li>\n<\/ol>\n

                              Correct Answer: 1<\/b><\/p>\n

                              Explanation<\/b><\/p>\n

                              Current inventory should be retrieved from an approved business data source when the information changes frequently. A connector, API, or other authorized data connection can provide the latest inventory status at runtime. This avoids relying on stale information embedded in model training or static instructions. The integration should include authentication, authorization, validation, error handling, and monitoring. If inventory information is unavailable, the agent should follow a defined fallback or clarification process rather than inventing availability.<\/span><\/p>\n

                              Question 355<\/b><\/h3>\n

                              Which architecture pattern is appropriate when specialized agents collaborate on different parts of a business process?<\/b><\/p>\n

                                \n
                              1. Multi-agent architecture<\/span><\/li>\n
                              2. Single static prompt<\/span><\/li>\n
                              3. Database backup<\/span><\/li>\n
                              4. Token compression<\/span><\/li>\n<\/ol>\n

                                Correct Answer: 1<\/b><\/p>\n

                                Explanation<\/b><\/p>\n

                                A multi-agent architecture divides responsibilities among specialized agents that collaborate to complete a broader workflow. For example, one agent may handle customer identification, another may analyze billing information, and another may manage service requests. An orchestration layer can coordinate these agents and manage handoffs. Each agent should have clearly defined responsibilities and appropriate permissions. Multi-agent designs can provide specialization but also introduce additional complexity, so organizations should use them when the business workflow genuinely benefits from separated capabilities.<\/span><\/p>\n

                                Question 356<\/b><\/h3>\n

                                Why should an organization define agent ownership?<\/b><\/p>\n

                                  \n
                                1. To establish responsibility for maintenance, governance, and operational decisions<\/span><\/li>\n
                                2. To give everyone administrator access<\/span><\/li>\n
                                3. To eliminate monitoring<\/span><\/li>\n
                                4. To avoid documentation<\/span><\/li>\n<\/ol>\n

                                  Correct Answer: 1<\/b><\/p>\n

                                  Explanation<\/b><\/p>\n

                                  Defined ownership establishes who is responsible for maintaining an AI agent and responding to operational or governance issues. Owners may oversee configuration changes, access reviews, evaluations, incident handling, knowledge updates, and lifecycle decisions. Clear ownership prevents situations where an agent remains active without anyone responsible for its security or performance. Ownership should be documented and aligned with organizational processes. In larger environments, technical, business, security, and compliance responsibilities may be shared across different roles.<\/span><\/p>\n

                                  Question 357<\/b><\/h3>\n

                                  Which practice helps detect whether an AI solution’s performance is declining over time?<\/b><\/p>\n

                                    \n
                                  1. Drift monitoring<\/span><\/li>\n
                                  2. Removing evaluation datasets<\/span><\/li>\n
                                  3. Disabling telemetry<\/span><\/li>\n
                                  4. Increasing permissions<\/span><\/li>\n<\/ol>\n

                                    Correct Answer: 1<\/b><\/p>\n

                                    Explanation<\/b><\/p>\n

                                    Drift monitoring helps identify changes in data, user behavior, or system performance that may cause an AI solution to behave differently over time. Changes in the underlying business environment can reduce model or retrieval effectiveness even when the application itself has not been modified. Monitoring can track relevant quality, usage, and operational metrics against established baselines. When drift is detected, teams can investigate data, prompts, retrieval, models, or business processes and determine whether retraining, reconfiguration, or other action is required.<\/span><\/p>\n

                                    Question 358<\/b><\/h3>\n

                                    What is a key benefit of using an API gateway with multiple AI services?<\/b><\/p>\n

                                      \n
                                    1. Centralized traffic and access management<\/span><\/li>\n
                                    2. Automatic removal of all security risks<\/span><\/li>\n
                                    3. Elimination of model evaluation<\/span><\/li>\n
                                    4. Unlimited backend access<\/span><\/li>\n<\/ol>\n

                                      Correct Answer: 1<\/b><\/p>\n

                                      Explanation<\/b><\/p>\n

                                      An API gateway can provide a centralized point for managing traffic between applications and multiple backend services. Depending on the platform, it can support authentication, authorization, routing, rate limiting, monitoring, and policy enforcement. This can simplify governance when an AI solution interacts with several APIs or services. The gateway does not automatically eliminate security risks, and backend services should continue to enforce their own authorization where appropriate. Centralized management should complement, not replace, service-level security controls.<\/span><\/p>\n

                                      Question 359<\/b><\/h3>\n

                                      A model change reduces cost but also decreases response quality below the business requirement. What should the team do?<\/b><\/p>\n

                                        \n
                                      1. Deploy it immediately<\/span><\/li>\n
                                      2. Ignore the quality reduction<\/span><\/li>\n
                                      3. Reassess the model against the required acceptance criteria<\/span><\/li>\n
                                      4. Remove all evaluation metrics<\/span><\/li>\n<\/ol>\n

                                        Correct Answer: 3<\/b><\/p>\n

                                        Explanation<\/b><\/p>\n

                                        A lower-cost model should not be adopted solely because it reduces operating expenses if its quality falls below defined business requirements. The team should compare the model using representative workloads and established acceptance criteria. The evaluation should consider accuracy, groundedness, safety, latency, and cost as appropriate for the use case. If quality is insufficient, the team can consider routing only suitable tasks to the smaller model or using a more capable model for important scenarios. Architecture decisions should reflect both business value and technical performance.<\/span><\/p>\n

                                        Question 360<\/b><\/h3>\n

                                        What should happen to unnecessary agent permissions after a system is retired?<\/b><\/p>\n

                                          \n
                                        1. They should remain permanently active<\/span><\/li>\n
                                        2. They should be reviewed and revoked<\/span><\/li>\n
                                        3. They should be shared with users<\/span><\/li>\n
                                        4. They should be copied to another system automatically<\/span><\/li>\n<\/ol>\n

                                          Correct Answer: 2<\/b><\/p>\n

                                          Explanation<\/b><\/p>\n

                                          When an agent is retired, associated permissions, credentials, service identities, connectors, and access paths should be reviewed and revoked when they are no longer required. Leaving unused permissions active creates unnecessary security exposure and can result in orphaned access. Retirement should also include dependency review, documentation, data-retention decisions, and appropriate audit records. If another system replaces the retired agent, its permissions should be independently designed according to least privilege rather than simply inheriting all of the previous agent’s access.<\/span><\/p>\n

                                           <\/p>\n","protected":false},"excerpt":{"rendered":"

                                          View Full Microsoft AB-100 Exam Dumps and Practice Test Dumps.   Question 341 What is the primary purpose of agent memory? Manage information that an agent needs to retain during or across tasks Increase API quotas Replace authorization Encrypt databases Correct Answer: 1 Explanation Agent memory allows an AI agent to retain useful information needed […]<\/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\/13380"}],"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=13380"}],"version-history":[{"count":1,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/13380\/revisions"}],"predecessor-version":[{"id":13384,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/posts\/13380\/revisions\/13384"}],"wp:attachment":[{"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/media?parent=13380"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/categories?post=13380"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.examlabs.com\/certification\/wp-json\/wp\/v2\/tags?post=13380"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}