Get Microsoft AB-620 Exam Practice Questions - Real and Updated

Answer : A

Comprehensive and Detailed Explanation From [Atlassian Jira Cloud Documentation]

The cause is the Jira Browse users and groups global permission. Atlassian states that users with this permission can view user names when working with user-picker fields or @mentioning users. Without it, Jira cannot provide the affected users with the complete user directory required to search for and select another person through an @mention.

The fact that users can enter and save ordinary text in the paragraph field confirms that the field is present, editable, and available on the applicable work-item layout. Therefore, field settings and screen settings are not responsible. Notification settings determine how users receive updates after an event and do not control whether names appear in the mention picker.

Project permissions and issue-level security can affect whether a particular person can access the project or work item. However, a general inability to search for or mention other users indicates that the initiating users lack the site-wide user-browsing capability.

A Jira administrator should review Settings System Global permissions and grant Browse users and groups to an appropriate group containing the affected users, subject to the organization's privacy policies.

Relevant documentation topic: Jira Cloud administration Global permissions Browse users and groups. See What are global permissions, and what do they control?.

Answer : A, E

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: The Service Desk Agent must be both published and available for connections from other agents. Publishing establishes a runtime version that the primary agent can call; an unpublished draft is not a valid connected-agent target. On the Service Desk Agent, the setting that allows other agents to connect and use it must also be enabled. Microsoft additionally requires the connected agent to be in the same environment and the maker to own it or have it shared, but those conditions are not offered as choices. Replacing the agent with an MCP server would discard the existing agent's orchestration and ticket-routing logic. Adding it as a knowledge source would expose content for retrieval, not delegate an IT request to another agent. Publishing Operations Concierge alone does not satisfy the prerequisites of the target agent. After connection, the local description in Operations Concierge should clearly define when IT-specific work is delegated, because descriptions influence routing. Any later changes to the Service Desk Agent must be published before the main agent can use the updated version. Study Guide alignment: Integrate and extend agents in Copilot Studio > Configure multi-agent collaboration from Copilot Studio > Integrate an existing agent in Copilot Studio.

===============

Answer : C

Comprehensive and Detailed 150 to 250 words of Explanation From [Microsoft AB-620 study guide]: Azure AI Search must be configured as the authoritative retrieval source, with ungrounded or general-knowledge responses disabled. In the retrieval-augmented generation process, Copilot Studio first reformulates the user's question, searches the connected vector index, and supplies relevant results to the Microsoft Foundry-hosted model for response generation. Requiring grounding prevents the model from answering solely from its pretrained knowledge when Azure AI Search returns no sufficiently relevant content. In that situation, the agent should return no generated answer and follow its configured fallback or escalation behavior. Selecting a Foundry model alone does not enforce grounding because model selection controls the generation layer, not the retrieval requirement. Citations provide traceability but likewise do not prevent an unsupported answer. Uploading duplicate documents would introduce another knowledge store and undermine Azure AI Search as the controlled enterprise index. The Azure AI Search connection should identify the intended vector index and use semantic ranking where appropriate. Testing should confirm that valid queries return supported answers and citations, while out-of-scope queries produce no ungrounded response. Study Guide alignment: Integrate and extend agents in Copilot Studio Connect to Azure AI Search; Integrate agents with Azure Configure generative answers by using Azure AI Search with Foundry.

Answer : B, E

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: The test passed because the score of 0.92 exceeds the configured threshold of 0.80 and the evaluation method recognizes semantic equivalence. The actual answer conveys the same policy meaning as the expected response even though the wording is different, so an exact textual match is unnecessary. The recorded knowledge source is RefundPolicy_KB, which is the expected grounding path; confirming that source behavior is therefore appropriate. No tool was expected or invoked, so investigating tool configuration would add noise rather than address a defect. A score below 1.00 is not itself a failure, and rewriting the expected answer to mirror every valid paraphrase would undermine a meaning-based evaluation. The result can be accepted while still being retained as regression evidence. Reviewers should confirm that the cited or retrieved policy content supports the non-refund statement and that the chosen threshold reflects the business risk. For fixed codes or legally prescribed phrases, exact match might be preferable, but this natural-language policy answer is correctly evaluated by semantic similarity. Study Guide alignment: Test and manage agents > Evaluate agent performance > Review test results.

===============

Answer : A, E

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: Computer use is the Copilot Studio capability for operating a website or desktop application's graphical interface when an API is unavailable. Enabling it gives the agent a UI automation tool driven through the supported machine execution context. During testing, the builder can open the computer-use activity or remote session from the agent's activity view to observe steps, inspect logs, and understand failures in real time. Adding a desktop flow is a different deterministic automation technology and is not required by the stated computer-use design. Publishing alone does not provision the UI automation or its machine. A custom connector cannot automate screen controls when the application exposes no API. The tool should be configured with narrowly scoped instructions, a healthy supported machine, protected credentials, and human confirmation for sensitive actions. Because computer-use behavior is probabilistic and visual interfaces change, the team should test alternate screen states, pop-ups, timing, and recovery, then monitor production sessions under strict access and retention controls. Study Guide alignment: Integrate and extend agents in Copilot Studio > Add tools to agents > Configure and monitor computer use for an agent.

===============