Microsoft AB-650 Dumps Questions Answers

Statement

Correct Answer

User2 can reference files in the Vendor Contracts folder by using Copilot Chat.

Yes

User1 has the access required for Microsoft 365 Copilot to ground responses in the Forecast files.

No

User1 has the access required for Microsoft 365 Copilot to ground responses in the Vendor Contracts files.

Yes

Microsoft 365 Copilot and Copilot Chat respect existing SharePoint permissions and Microsoft Purview sensitivity label encryption restrictions when accessing organizational content.

Statement 1: Yes.

User2 belongs to Group1 and has access to the Vendor Contracts folder through the Everyone except external users permission.

Although User2 does not have a paid Microsoft 365 Copilot license, Copilot Chat supports explicitly referencing accessible files, subject to supported experiences and file types. User2 can therefore reference supported Vendor Contracts files in a prompt.

However, Copilot Chat without a paid license does not automatically discover and ground responses across all organizational files through Microsoft Graph.

Statement 2: No.

User1 has a Microsoft 365 Copilot license and SharePoint access to Forecast. However, the Forecast documents are encrypted by a sensitivity label granting usage rights only to Group1.

Because User1 is outside Group1, the user lacks the necessary encryption permissions. Microsoft 365 Copilot cannot use those files for grounding.

Statement 3: Yes.

Vendor Contracts contains unlabeled files and grants access to Everyone except external users.

User1 is an internal user with a Microsoft 365 Copilot license and appropriate SharePoint access. No additional sensitivity-label encryption restricts the files.

Therefore, Copilot can use accessible Vendor Contracts files to ground responses.

Microsoft References:

Microsoft Support — Refer to specific files in Microsoft Copilot .

Microsoft Learn — Copilot data protection, permissions, and encryption .

Microsoft Learn — How Copilot Chat grounding works .

Microsoft Purview Data Loss Prevention (DLP) uses sensitive information types (SITs) to detect sensitive content in Exchange Online email messages, documents, and other supported Microsoft 365 locations.

Option B is correct because the customer IDs follow a predictable format consisting of 10 digits followed by 10 characters, with hyphens separating the components.

Administrators can create a custom sensitive information type using a regular expression to identify this structure.

For example, to match the specific format shown in the question:

\b(\d{3}-\d{3}-\d{4}-[A-Za-z]{3}-[A-Za-z] {2}-[A-Za-z]{5})\b

Administrators can configure the SIT through Microsoft Purview portal → Information Protection → Classifiers → Sensitive info types → Create sensitive info type.

After creating and testing the SIT, administrators can reference it in the DLP policy ' s Content contains → Sensitive info types condition to detect emails containing matching customer IDs.

Option A is incorrect because sensitivity labels classify and protect content rather than independently defining custom detection patterns.

Option C is incorrect because a PowerShell script is not necessary to detect the specified customer ID format.

Option D is incorrect because retention labels control content retention and disposition rather than pattern-based sensitive information detection.

For production use, supporting keywords or additional validation can reduce false positives. The regular expression should also be adjusted if actual customer IDs permit characters or separators beyond those in the example.

Microsoft References:

Microsoft Learn — Create custom sensitive information types .

Microsoft Learn — Use regular expressions in DLP policies .

Microsoft 365 supports pay-as-you-go billing for Microsoft Copilot Chat and SharePoint agents through Azure subscriptions. Administrators can analyze the associated charges using Microsoft 365 Cost Management.

Option A is correct because Cost Management in the Microsoft 365 admin center provides service-level billing information for supported Microsoft 365 pay-as-you-go workloads.

Administrators can navigate to Microsoft 365 admin center → Billing → Cost management.

The Cost Management experience provides the following capabilities:

View billed consumption for Microsoft Copilot Chat and SharePoint agents.

Filter costs by service family to isolate the relevant Microsoft 365 AI workloads.

Select a historical reporting period, including the previous calendar month.

Review cost breakdowns and spending trends.

Export available billing information for financial analysis.

Although the billing policies are connected to Sub1, the Microsoft 365 reporting experience enables finance personnel to focus on the relevant AI services without including unrelated Azure virtual machines, storage, or other resources.

Option B is incorrect because the Copilot Chat usage report primarily measures adoption and engagement rather than billed service costs.

Option C is incorrect because Power Platform Capacity add-ons are not the appropriate reporting interface for these Microsoft 365 pay-as-you-go charges.

Option D is incorrect because Billing accounts manages billing relationships and invoices rather than providing the requested service-specific cost analysis.

Microsoft References:

Microsoft Learn — View costs and billing for Microsoft Copilot pay-as-you-go .

Microsoft Learn — Use Cost Management in the Microsoft 365 admin center