Microsoft PL-900 Practice Test - Questions Answers, Page 13

Box 1: Yes

Managed solutions are used to deploy to any environment that isn't a development environment for that solution. Box 2: No

Unmanaged solutions can be exported either as unmanaged or managed.

Box 3: Yes

You can't edit components directly within a managed solution. To edit managed components, first add them to an unmanaged solution.

Reference:

https://docs.microsoft.com/en-us/power-platform/alm/solution-concepts-alm

Box 1: connector

A connection is a proxy or a wrapper around an API that allows the underlying service to talk to Microsoft Power Automate, Microsoft Power Apps, and Azure Logic Apps. It provides a way for users to connect their accounts and use a set of pre-built actions and triggers to build their apps and workflows.

Power Automate offers connectors (apps/services like SharePoint, Outlook, /.) and most connectors offer prebuilt triggers that you can use to start your flows. Box 2: solution

If you’re creating an action to include as part of a solution that will be distributed, create it in the context of the solution. Go to Settings > Solutions and locate the unmanaged solution that this action will be part of.

Reference: https://docs.microsoft.com/en-us/connectors/connectors https://docs.microsoft.com/en-us/powerapps/maker/data-platform/configure-actions

Box 1: Yes

With embedded canvas apps, makers can bring the power of canvas apps to their model-driven forms. Using embedded canvas apps, it is possible to create rich visual areas on a form and display data from a variety of sources right next to data from Microsoft Dataverse.

Box 2: No Box 3: Yes

Reference:

https://docs.microsoft.com/en-us/powerapps/maker/model-driven-apps/embed-canvas-app-in-form

Box 1: No

You can reorder screens.

In the left navigation bar, hover over a screen that you want to move up or down, select the ellipsis button that appears, and then select Move up or Move down. Box 2: No

You can add screens to the app after it has been created.

Box 3: No

For example, you can change a button's shape. By default, Power Apps creates a rectangular Button control with rounded corners. You can make basic modifications to the shape of a Button control by setting its Height, Width, and Radius properties.

Reference: https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/add-screen-context-variables https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/controls/control-button

Box 1: Yes

By default, you can download up to seven days of bot conversation transcript sessions from the past 30 days directly from the Power Virtual Agents portal. Box 2: No

You can set the permissions for a Flow.

Reference:

https://docs.microsoft.com/en-us/power-virtual-agents/analytics-sessions https://docs.microsoft.com/en- us/connectors/microsoftflowforadmins

Box 1: Yes

Chatbots built with Power Virtual Agents will understand and display content that's locally relevant to the user. Localized handling and formatting are based on the user's browser locale setting, and include the following elements within a chat conversation:

Date and time

Numbers

ZIP or postal code

Currency

Speed

Box 2: Yes

Custom entities:

The prebuilt entities cover commonly used information types, but on some occasions, such as when building a bot that serves a specific purpose, you'll need to teach the bot's language understanding model some domain-specific knowledge. For instance, let's say you want to build a bot for an outdoor store. In this case, you'll need to teach the bot to acknowledge the "outdoor gears product" category in a dialog.

Reference: https://docs.microsoft.com/en-us/power-virtual-agents/data-location https://docs.microsoft.com/en-us/powervirtual-agents/advanced-entities-slot-filling

Box 1: No

With Power Virtual Agents, you can hand off conversations to live agents seamlessly and contextually. When you hand off a conversation, you share the full history of the conversation (the context) as well as all user-defined variables. Having access to this context means live agents that are using any connected engagement hub can be notified that a conversation requires a live agent, see the context of the prior conversation, and resume the conversation. Box 2: Yes

By default, chatbots created with Power Virtual Agents and published to a website will load without a greeting, and will passively wait for the user to start the conversation.

However, you can use custom CSS and JavaScript code to automatically have the bot start the conversation when the bot loads.

Reference: https://docs.microsoft.com/en-us/power-virtual-agents/advanced-hand-off https://docs.microsoft.com/en- us/power-virtual-agents/configure-bot-greeting

Box 1: No

The following software combinations are the supported recommendations for consuming PowerApps with a screen reader:

Windows: Microsoft Edge / Narrator macOS: Safari / VoiceOver Android: PowerApps app / Talkback iOS: PowerApps app / VoiceOver

Box 2: Yes

Users who have vision, hearing, or other impairments can use your canvas app more easily and successfully if you consider accessibility as you design how the app looks and behaves. If you're not sure how to make your app more accessible, you can run the Accessibility checker in PowerApps Studio. This tool not only finds potential accessibility issues but also explains why each might be a potential problem for users who have a specific disability and offers suggestions on how to resolve each issue. The Accessibility checker detects screen-reader and keyboard issues for you, and you can find information about how to fix color-contrast issues by using accessible colors.

Reference: https://docs.microsoft.com/en-us/powerapps/user/screen-reader https://docs.microsoft.com/enus/powerapps/maker/canvas-apps/accessibility-checker

https://docs.microsoft.com/en-us/ai-builder/prebuilt-overview