A.

Audit summary view

B.

Solution history

D.

Plug-in trace log

A: How to View Auditing Log Details?
System administrators can see activities for the entities that are enabled for audit logging.
To view the audit logs:
Go to Settings > System >Auditing.
Choose Audit Summary View.
Under Audit Summary View, you will see the list of audit entries

B: You can view details about solution operations from the Solutions area of Power Apps.
An operation can be a solution import, export, or uninstall. The solution history displays
information such as solution version, solution publisher, type of operation, operation start
and end time, and operation status.
D: Trace log records are written to the PluginTraceLog Table. Writing of these records is
controlled by the trace settings mentioned in Enable trace logging.
This data can be found in model-driven applications by navigating to Settings and choosing
the Plug-in Trace Log tile.
Reference:
https://www.sherweb.com/blog/dynamics-365/audits-dynamics-365/
https://docs.microsoft.com/en-us/powerapps/developer/data-platform/logging-tracing

B.

Add security to the Core Records and assign users to the Customer Service
Representative role.

E.

Copy the Customer Service Representative role.

Scenario: The security rule for agents must contain the privileges in the default Customer
Service
Representative security role.
Create a security role by Copy Role:
Step 1 (E): Copy the Customer Service Representative role.
Step 2 (F): Select the New Role Name.
Step 3 (B): When Copying Role is complete, navigate to each tab, ie Core Records,
Business Management, Customization, etc.
Set the privileges on each tab.
Reference:
https://docs.microsoft.com/en-us/power-platform/admin/create-edit-security-role

B.

Power Apps Component Framework control

Power Apps component framework empowers professional developers and app makers to
create code components for model-driven and canvas apps (public preview) to provide
enhanced user experience for the users to work with data on forms, views, and
dashboards.
Reference:
https://docs.microsoft.com/en-us/powerapps/developer/component-framework/overview

A.

Consolidate asynchronous workflow into a single real-time workflow.

B.

Consolidate multiple asynchronous workflows into a single asynchronous workflow.

Box 1: Microsoft Teams
First up employees must be able to contact each other by using a secure system to ask
and answer questions about medical cases.
Microsoft Teams key capabilities:
Connected
Secure
Managed
Collaborative and productive
Box 2: Microsoft 365 Business Voice
Workers must be able to communicate in near real-time with worker support agents.
Microsoft 365 Business Voice makes it easy for small and medium organizations to turn
Microsoft Teams into a powerful and flexible telephone system. It's a replacement for
traditional telephony providers and in-house phone systems that can be difficult and costly
to manage.

Box 1: Automated cloud flow.
Create a cloud flow when you want your automation to be triggered either automatically,
instantly, or via a schedule.
Automated flows: Create an automation that is triggered by an event such as arrival of an
email from a specific person, or a mention of your company in social media.
Box 2: Desktop flow and AI Builder
Desktop flows are used to automate tasks on the Web or the desktop. Using Power
Automate Desktop you can automate tasks on the desktop as well as the Web.
Box 3: Model-driven app dashboard with Power BI
The Power BI cloud service works with Microsoft Dataverse apps to provide a self-service
analytics solution. Power BI automatically refreshes the app's data displayed.

B.

customer maintenance procedures

D.

solution regulatory compliance

E.

time-to-load forms

Non-functional requirements capture the elements that users might not directly care about
but are important to support the proposed architecture and operational viability of the
solution. Non-functional requirements often influence user adoption and perceived
satisfaction with the solution.
Examples of common non-functional requirement types include:
Availability
Compliance/regulatory
Data retention/residency
Performance (response time, and so on)
Privacy
Recovery time
Security
Scalability
Reference:
https://docs.microsoft.com/en-us/learn/modules/work-with-requirements/4-non-functionalrequirements

Box 1: Reduce usage of near real-time workflows
A real-time workflow can be converted to asynchronous workflow and back to real-time.
Box 2: Convert all Dynamics 365 workflows to Power Automate cloud flows.
Workflows are limited to Microsoft Dynamics 365/CRM application only.
Power Automate can span across multiple web-based services or applications at the same
time.
Dynamics 365 CRM Workflows can be converted to Power Automate flows