Microsoft 365 Copilot and Agent Administration Fundamentals AB-900 Perform basic administrative tasks for Copilot and agents: 391 practice questions

12 of the 391 Perform basic administrative tasks for Copilot and agents questions in the Certsqill Microsoft 365 Copilot and Agent Administration Fundamentals AB-900 bank, shown in full below. Each one carries an explanation for every option, not just the correct one — the wrong answers are where the marks go.

Preparing for Microsoft 365 Copilot and Agent Administration Fundamentals AB-900? Take the free 5-min readiness check →

1. Use built-in Copilot for broad productivity assistance: Select TWO.

Select two. More than one option is correct — every correct one is ticked below.

1. Use built-in Copilot for broad productivity assistance during onboarding. ✓

   Copilot provides broad productivity assistance suitable for common onboarding questions and drafting tasks.
2. Create a custom agent for organization-specific onboarding instructions and workflows. ✓

   Custom agents can provide scoped organization-specific instructions, knowledge, and supported workflows.
3. Assume an agent automatically grants access to its connected source content.

   Agents respect source authorization; using an agent does not independently grant users access.
4. Use Researcher to replace onboarding access governance and permission reviews.

   Researcher supports research synthesis but does not replace permission governance or access reviews.
5. Use Analyst as a tenant permission administrator for new employees.

   Analyst supports data analysis, reasoning, and visualizations; it is not an administrative permission tool.

Built-in Copilot supports broad productivity; a custom agent can provide scoped organization-specific onboarding instructions and workflows.

2. Connect the billing policy to the supported Copilot: What should the administrator diagnose first?

1. Increase the pay-as-you-go budget notification threshold for the finance group.

   Budget notifications do not enable service access, and changing thresholds cannot create metered usage.
2. Grant every finance user full SharePoint site permissions and remove the billing policy scope.

   Source permissions are separate, while removing policy scope would not activate pay-as-you-go service access.
3. Replace the monthly licenses with a larger monthly Copilot license assignment.

   Monthly licensing does not activate an unconnected pay-as-you-go policy or explain absent metered service access.
4. Connect the billing policy to the supported Copilot service. ✓

   A billing policy requires connection to a supported Copilot service before scoped metered access and charges can occur.

The policy exists, but pay-as-you-go requires connection to a supported Copilot service.

3. Enable Researcher in the applicable Copilot feature: Which action addresses the missing prerequisite?

1. Enable Researcher in the applicable Copilot feature control. ✓

   The team already has licensing and provisioning, so enabling the feature control addresses the stated prerequisite.
2. Assign another SharePoint site role to researchers.

   SharePoint permissions govern source access, not whether the Researcher feature is enabled for users.
3. Add all researchers to a billing policy and connect it to SharePoint agents.

   Pay-as-you-go configuration concerns supported metered services, not a disabled Researcher feature control.
4. Create a custom research agent with equivalent instructions and connected knowledge sources.

   A custom agent is an alternative capability, not the missing prerequisite for enabling Researcher.

Licensing and provisioning are present; the disabled Researcher feature control is the missing prerequisite.

4. Researcher for multi-step research and synthesis across: Which capability is the best fit?

1. Researcher for multi-step research and synthesis across authorized sources. ✓

   Researcher supports multi-step research and synthesis across sources while respecting the user’s existing source access.
2. A saved prompt in Copilot.

   A saved prompt preserves reusable instructions but does not itself provide specialized multi-source research capability.
3. Analyst.

   Analyst is intended for data analysis, reasoning, and visualizations rather than multi-source research synthesis.
4. A tenant administration agent that grants broader access to product documents.

   Administrative agents do not replace source authorization or provide unrestricted access to confidential product plans.

Researcher is designed for multi-step research and synthesis across authorized sources.

5. Analyst for data analysis and visualizations: Which capability should the manager use?

1. A custom agent with sales terminology, meeting instructions, and organization-specific workflow guidance.

   A custom agent can provide scoped instructions or knowledge, but it does not by itself replace the specialized analytical capability needed here.
2. A saved prompt.

   A saved prompt standardizes instructions but does not provide the specialized data-analysis and visualization capability requested.
3. Researcher for multi-step research and synthesis across external and organizational sources.

   Researcher is oriented toward research and synthesis across sources, while this request centers on structured quantitative analysis and charts.
4. Analyst for data analysis and visualizations. ✓

   Analyst supports reasoning over data, identifying patterns, interpreting anomalies, and producing visualizations from authorized information.

Analyst fits structured data analysis, anomaly reasoning, and visualizations.

6. Create a scoped custom agent: Which option best fits?

1. Save a general Copilot prompt for every service-desk technician.

   A saved prompt preserves wording but does not define the scoped knowledge and workflow behavior required.
2. Create a scoped custom agent. ✓

   A custom agent can provide organization-specific instructions, knowledge, and supported workflows within defined governance boundaries.
3. Publish a Researcher request asking Copilot to follow onboarding procedures.

   Researcher supports research synthesis, not a narrowly governed organization-specific operational workflow.
4. Assign monthly Copilot licenses to the service-desk team.

   Licenses provide eligibility but do not create organization-specific instructions, knowledge, or workflow behavior.

A custom agent is intended for scoped organizational instructions, knowledge, and supported workflows.

7. License assignment does not grant SharePoint permissions: What boundary should the administrator recognize?

1. License assignment does not grant SharePoint permissions. ✓

   A Copilot license provides eligibility, while access to SharePoint documents remains governed by SharePoint permissions.
2. The billing policy must be expanded before SharePoint permissions can apply.

   Billing scope affects metered service access, not the employee’s authorization to documents in SharePoint.
3. The license should automatically grant access after its next provisioning cycle.

   Provisioning may enable the service, but it does not automatically authorize restricted SharePoint content.
4. The employee needs a second Copilot license specifically for restricted libraries.

   Additional licensing does not replace the SharePoint permissions required to read restricted documents.

Copilot licensing provides eligibility; SharePoint permissions separately control document access.

8. Connect the existing billing policy to the supported: What is the next troubleshooting step?

1. Connect the existing billing policy to the supported Copilot service. ✓

   Connecting the already scoped policy is the required next step before eligible metered service access can operate.
2. Raise the budget notification amount for the department.

   Budget notifications warn about spending and do not activate an unconnected metered Copilot service.
3. Review the department’s monthly license assignments.

   Monthly licenses do not complete the missing pay-as-you-go service connection identified in the scenario.
4. Delete the policy and recreate it with unrestricted tenant-wide scope.

   Recreating broader scope is unnecessary and does not address the missing connection to the supported service.

The existing policy must be connected to the supported Copilot service before metered access works.

9. Use Copilot Analytics and relevant usage reports to review: Which approach is most appropriate?

1. Use Copilot Analytics and relevant usage reports to review adoption and impact. ✓

   Copilot Analytics and applicable usage reports support review of adoption and available impact views when their prerequisites and permissions are satisfied.
2. Use saved prompts to authorize HR access and display employee adoption results.

   Saved prompts preserve instructions; they do not grant access to employee records or provide Copilot adoption analytics.
3. Use usage counts alone to prove productivity gains.

   Usage counts can indicate activity but do not by themselves prove productivity or return on investment.
4. Use the Microsoft 365 admin center to review adoption activity only.

   The admin center can provide relevant usage information, but adoption and impact review should use the applicable analytics and reports.

Use Copilot Analytics and usage reports for adoption and impact review, without treating usage as proof of productivity.

10. The prompt is removed: What should the administrator expect?

1. The prompt is removed and all previous activity records are purged.

   Deleting a saved prompt does not necessarily erase previous activity or retained audit evidence.
2. The prompt’s source documents are deleted with the saved prompt.

   A saved prompt is separate from the documents it references, so deleting it does not delete those documents.
3. The prompt is removed, but its source documents remain available according to their permissions. ✓

   Deleting the saved prompt removes that reusable prompt and does not inherently delete the referenced documents or change their permissions.
4. The prompt’s sharing settings change while the saved prompt remains.

   Deleting a saved prompt removes the prompt; it does not merely change its sharing settings.

Deleting a saved prompt removes the prompt, not its source documents or historical evidence.

11. Add the technician to the agent’s assigned access group: Which administrative action is appropriate?

1. Add the technician to the agent’s assigned access group. ✓

   Adding the technician to the agent’s assigned users or groups addresses agent availability while preserving existing source permissions.
2. Publish the agent again and assume publication makes it available organization-wide.

   Publishing does not automatically provide tenant-wide approval or access to every intended user.
3. Grant the technician tenant-wide administrator rights before testing the agent.

   Tenant administrator rights are unnecessary because agent access and source access should use narrower appropriate controls.
4. Give the technician broader permissions on the connected knowledge source.

   The source already permits required reading, so broader data permissions would not fix missing agent assignment.

Assign the technician through the agent’s users or groups; publication alone does not grant access.

12. Complete the required approval before assigning the agent: What should the administrator diagnose first?

1. Complete the required approval before assigning the agent to users. ✓

   Pending approval can prevent availability even after publication and group assignment are configured.
2. Share the agent with the audit group.

   Sharing may assign users, but it does not resolve the displayed pending approval requirement.
3. Rebuild the agent with a different supported knowledge source and then publish it again.

   Rebuilding changes the agent configuration but does not address its recorded governance approval state.
4. Wait for indexing.

   Indexing is not the observed prerequisite issue because the agent still has pending approval.

The pending approval status explains why publication and assignment have not made the agent available.

Other Microsoft 365 Copilot and Agent Administration Fundamentals AB-900 domains

• Understand data protection and governance tasks for Microsoft 365 and Copilot — 513 questions →
• Identify the core features and objects of Microsoft 365 services — 446 questions →
• All 1350 Microsoft 365 Copilot and Agent Administration Fundamentals AB-900 questions →
• Microsoft 365 Copilot and Agent Administration Fundamentals AB-900 certification: requirements, cost and exam format →