Correct Answers: C and E
Power Virtual Agents bots are potentially dealing with customer’s personal information and taking actions on behalf of the customer. Therefore, the customer authentication and security of the data is the highest priority.
Power Virtual Agents provides three options for the customer authentication for the web app: No authentication — the bot will not require any authentication for the use.
Only for Teams — simple option if you are planning to use a bot only within Microsoft Teams. Authentication will be automatically set up for Azure AD for Teams. This option will not allow using the bot in other channels.
Manual — you can use a bot with any channel, including Teams. This option supports Azure AD and OAuth2 identity providers (Microsoft, Twitter, Facebook, Google, etc.). If you want to use Azure AD authentication, you need to register your web app with Azure AD and provide Client ID and Client secret during the bot’s Authentication setup.
You can set the Power Virtual Agents authentication options from the PVA portal by selecting the Manage section (Number 1) and Security subsection (Number 2) from the menu. Then on the Security screen, you select the Authentication panel button, and the new Authentication panel opens to the right. On this panel, you can choose the authentication options for the bot: No Authentication (Number 3), Only for Teams (Number 4), and Manual (Number 5). You should provide Client ID and Client secret for the manual option if you select one of the Azure AD entries (Number 6).
All other options are incorrect because they are the identity provider types but not the authentication options for Power Virtual Agents.
For more information about Power Virtual Agents authentication, please visit the below URLs:
https://docs.microsoft.com/en-us/learn/modules/architect-power-virtual-agents/4-best-practice
https://docs.microsoft.com/en-us/power-virtual-agents/configuration-end-user-authentication