Explanation
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/power-virtual-agents/advanced-entities-slot-filling

Explanation
Graphical user interface, text, application Description automatically generated

Reference:
https://docs.microsoft.com/en-us/power-virtual-agents/authoring-fundamentals
https://docs.microsoft.com/en-us/power-virtual-agents/advanced-entities-slot-filling

Explanation

Box 1: business rules
You can create business rules and recommendations to apply logic and validations without writing code or creating plug-ins. Business rules provide a simple interface to implement and maintain fast-changing and commonly used rules.
Box 2: business process flows
Flows Power Automate includes several types of processes, each designed for a different purpose:
* Automated flows. Create a flow that performs one or more tasks automatically after it's triggered by an event.
* Button flows. Perform repetitive tasks simply by tapping a button on your mobile device.
* Scheduled flows. Create a flow that performs one or more tasks on a schedule such as once a day, on a specific date, or after a certain time.
* Business process flows. Ensure that people enter data consistently and follow the same steps every time they work in an app by creating a business process flow.
* Workflows and actions. Dynamics 365 customizers may be familiar with the classic Common Data Service processes, which are workflows and actions.
Box 3: Common Data Model
Model-driven app design is a component-focused approach to app development. Model-driven app design doesn't require code and the apps you make can be simple or very complex. Unlike canvas app development where the designer has complete control over app layout, with model-driven apps much of the layout is determined for you and largely designated by the components you add to the app.
Reference:
https://docs.microsoft.com/en-us/powerapps/maker/model-driven-apps/guide-staff-through-common-tasks-proce
https://docs.microsoft.com/en-us/powerapps/maker/model-driven-apps/model-driven-app-overview