Explanation:
Box 1: Entities
Out of the box, Power Virtual Agents comes with a set of prebuilt entities, which represent the most commonly used stereotype information in real-world dialogs, such as age, colors, numbers, and names.
With the knowledge granted by entities, a bot can smartly recognize the relevant information from a user input and save it for later use.
Box 2: Topics
In Power Virtual Agents, a topic defines a how a bot conversation plays out.
You can author topics by customizing provided templates, create new topics from scratch, or get suggestions from existing help sites.
A topic has trigger phrases - these are phrases, keywords, or questions that a user is likely to type that is related to a specific issue - and conversation nodes - these are what you use to define how a bot should respond and what it should do.
Box 3: Variables
Variables let you save responses from your customers in a conversation with your bot so that you can reuse them later in the conversation.
For example, you can save a customer's name in a variable called UserName. The bot can then address the customer by name as the conversation continues.
You can use variables to create logical expressions that dynamically route the customer down different conversation paths.
Incorrect Answers:
* Flows: You can enable your bot to perform an action by calling a Microsoft Power Automate flow. Flows can help you automate activities, or call backend systems. For example, you can use flows with end-user authentication to retrieve information about a user after they've signed in.
Reference:
https://docs.microsoft.com/en-us/power-virtual-agents/advanced-entities-slot-filling
https://docs.microsoft.com/en-us/power-virtual-agents/authoring-create-edit-topics
https://docs.microsoft.com/en-us/power-virtual-agents/advanced-flow
https://docs.microsoft.com/en-us/power-virtual-agents/authoring-variables

Anybody can use the Power Apps portal as an unauthenticated user. Power Apps portal provides two user authentication methods:
Local authentication - creates a local identity with a username and password stored in a Dataverse database internally.
External authentication - uses credentials of the third-party identity providers.
Power Apps portal divides external providers by the authentication protocol:
OpenID Connect - has two providers: Azure AD and Azure AD B2C (Number 1).
OAuth2 - portal offers several provides for this protocol: Microsoft, Twitter, Facebook, LinkedIn, and Google (Number 2).
SAML 2.0 - has two providers: Azure AD and Active Directory Federation Services (AD FS).
WS-Federation - has two providers: Azure AD and Active Directory Federation Services (AD FS).
On the Identity Providers screen for the Power Apps portal, portal administrators can add a new provider (Number 3) or change an Authentication Settings on the new panel after clicking on the Settings button (Number 4). By changing the provider's status, you can Enable/Disable and Configure the providers (Number 5).

A portal creates a contact record in the Dataverse database for each authenticated user. It also assigns a web role. The role defines a user's access to portal resources.
Suppose you select the Configure in the provider's Status column or click on three dots. In that case, the Power Apps interface opens a new panel with steps for provider configuration (Number
1), like configuration information for Azure AD B2C provider.

Microsoft recommends using Azure AD B2C as the primary provider for portal authentication. It enables external customers to use the local sign-ins based on the federation with the various social identity providers. There is a list of benefits using Azure AD B2C, like access management, customizable policies, branding, support of various external providers, multi-factor authentication, etc.
Reference:
https://docs.microsoft.com/en-us/learn/modules/authentication-user-management/5- authentication-providers
https://docs.microsoft.com/en-us/powerapps/maker/portals/configure/set-authentication-identity
https://docs.microsoft.com/en-us/powerapps/maker/portals/configure/configure-portal- authentication
https://docs.microsoft.com/en-us/powerapps/maker/portals/configure/use-simplified- authentication-configuration

C: Desktop flows are used to automate tasks on the Web or the desktop. Using Power Automate you can automate tasks on the desktop as well as the Web.
A: Alternatively, you can use the two legacy methods of creating desktop flows: Windows recorder (V1) and Selenium ID. With these you record mouse and keyboard events.
Reference:
https://docs.microsoft.com/en-us/power-automate/desktop-flows/create-flow
https://docs.microsoft.com/en-us/power-automate/desktop-flows/create-web

Any changes made to the chart are immediately available to everyone with access to the shared chart.