Power

Automate
Interview Questions
Acknowledgements

We sincerely thanks all our Also thanks to all bloggers who PowerAutomate is a product
students who gave us inputs. provided the concepts in their from Microsoft.
blogs.
What is Power Automate?
• Power Automate is a cloud-based service provided by Microsoft that
allows users to create automated workflows between various
applications and services.
What is the "Delay" action
in Power Automate?
• The "Delay" action in Power Automate is a type of action that enables
the introduction of a delay between actions within a flow.

• Read more: https://d365demystified.com/2020/06/17/pause-a-flow-using-

delay-and-delay-until-power-automate/
What is a dynamic content
in Power Automate?
• A dynamic content in Power Automate is a type of content that is
automatically populated based on the inputs and outputs of
previous actions within a flow.in a flow.

• Read more: https://www.bigmountainanalytics.com/how-to-decipher-dynamic-

content-in-power-automate/
What is the "Switch" action
in Power Automate?
• The "Switch" action in Power Automate is a type of action that
enables the creation of multiple conditional branches within a flow.

• Read more: https://powerusers.microsoft.com/t5/Power-Apps-Community-

Blog/Switch-Statement-using-Power-Automate/ba-p/2032501
How to handle errors
in Power Automate?
• Use "Scope" actions: You can group multiple actions together in a "Scope" action, and set the error handling
options for that scope. For example, you can choose to continue the flow even if an error occurs within the scope,
or you can choose to stop the flow and send an email notification to a specific user.

• Use "Condition" actions: You can use "Condition" actions to check for errors or unexpected results in a flow. For
example, you can check if a value returned by an action is null or empty, and then take a specific action based on
the result.

• Use "Terminate" actions: You can use "Terminate" actions to stop a flow immediately if an error occurs. This can be
useful in situations where you need to ensure that a flow does not continue if it encounters an error.

• Use "Try/Catch" actions: You can use "Try/Catch" actions to catch specific types of errors that might occur during a
flow's execution. For example, you can catch errors related to authentication, connectivity, or data validation, and
then take specific actions to handle those errors.

• Use the "Run After" feature: You can configure actions to run only if a previous action in the flow succeeds or fails.
For example, you can configure an email notification to be sent only if a specific action fails.
• By using these options and combining them as needed, you can create robust and fault-tolerant flows that handle
errors gracefully.
How to read large data or
retrieve records in Power
Automate?
• In order to read all the rows from a large Excel file, we
need to recursively read data from it in batches, as
explained in the flowchart below.
• Read more: https://piyushksingh.com/2020/07/06/power-automate-read-
excel-file/
How to read large data or
retrieve records in Power
Automate?
• In order to read all the rows from a large Excel file, we
need to recursively read data from it in batches, as
explained in the flowchart below.
• Read more: https://piyushksingh.com/2020/07/06/power-automate-read-
excel-file/
What is a custom connector
in Power Automate, and why
would you use one?

A custom connector in Power Automate is a tool that

enables you to create a connection between your
organization's data and the Power Automate platform. It
allows you to extend the Power Automate capabilities by
creating an integration with a third-party service, a RESTful
API or a web service. You would use a custom connector
to connect to data sources that are not currently
supported in Power Automate, and to automate custom
workflows that require additional data or functionality.
Scenario: You need to Answer: I would use the "When a new response is
create a flow that submitted" trigger in Power Automate to monitor
the Microsoft Forms survey. Then, I would use the
automatically sends a "Control" action to add a condition that checks for
notification to a user the specific condition in the survey response. If the
whenever a specific condition is met, I would use the "Send an email" or
condition is met in a "Post a message" action to notify the designated
Microsoft Forms survey user of the condition.
response. How would
you approach this task?
Scenario: You need to Answer: I would use the "When a
create a flow that task is overdue" trigger in Power
triggers a reminder Automate to monitor the Planner
email to be sent to a task. Then, I would use the "Send an
user if a task in email" action to send a reminder
Microsoft Planner is email to the user responsible for
not completed by its
completing the task.
due date. How would
you set this up?
What is a trigger condition in
Power Automate?
• A trigger condition in Power
Automate is a type of expression that
is used to control when a workflow is
triggered based on specific criteria.
• Read
more: https://powerusers.microsoft.com/t5/Powe
r-Automate-Community-Blog/Power-Automate-
Trigger-Conditions-made-EASY/ba-p/441348
What is the
"Apply to The "Apply to each" action in Power
Automate is a control structure that is
used to iterate over a collection of
each" action items and perform a set of actions on
each item.

in Power
Automate? Read more: Use the apply to each
action in Power Automate to loop
through an array of items. (contains
video) - Power Automate | Microsoft
Learn
What is a trigger condition in
Power Automate?
• A trigger condition in Power
Automate is a type of expression that
is used to control when a workflow is
triggered based on specific criteria.
• Read
more: https://powerusers.microsoft.com/t5/Powe
r-Automate-Community-Blog/Power-Automate-
Trigger-Conditions-made-EASY/ba-p/441348
Can we create a child flow in
main flow using power
automate?
• Yes, you can create a child flow in a main flow using Power Automate. This allows you to create a modular and reusable design
for your flows, where you can separate specific functionality into separate child flows and reuse them across multiple main
flows.
• To create a child flow in Power Automate, you can follow these steps:
• Open the Power Automate designer and create a new blank flow.
• Add the actions that you want to perform in the child flow.
• Save and publish the child flow.
• In the main flow, add the "Child flow" action from the actions list.
• Select the child flow you want to use and configure any input parameters needed for the child flow.
• Save and publish the main flow.
• When the main flow is executed, it will call the child flow with the specified input parameters and wait for the child flow to
complete before continuing with the remaining actions in the main flow.
In which situation we will use
child flows in power
automate?
• Reusability: If you have a set of actions that are commonly used across multiple flows, you can create a child flow to contain
those actions and then reuse that child flow in other flows. This can save time and effort when creating and maintaining flows.
• Modularity: If you have a complex flow with many actions, you can break it down into smaller, more manageable parts by
creating child flows. This can make it easier to understand and maintain the flow, as well as enabling you to test and debug
individual parts more easily.
• Abstraction: If you have a flow that requires some specific functionality that is not directly supported by the available actions,
you can create a child flow to implement that functionality and then call it from the main flow. This can help to abstract away
the implementation details and make the main flow easier to understand and maintain.
• Error handling: If you have a flow that requires complex error handling, you can create a child flow to handle the errors and
then call it from the main flow when needed. This can help to keep the main flow simpler and more focused on the main
business logic.
 Can we call Powershell code from power
automate ?
• Yes, you can call PowerShell code from Power Automate. Power Automate provides the "Run PowerShell Script" action, which
allows you to execute PowerShell commands or scripts within your flow. Here's an overview of how you can do it:

• 1. Create a new flow or open an existing one in Power Automate.

• 2. Add a trigger or any previous actions required for your flow.

• 3. Search for and add the "Run PowerShell Script" action to your flow.

• 4. Configure the "Run PowerShell Script" action by providing the necessary inputs:
• - PowerShell script: Enter the PowerShell code or script you want to execute.
• - Script parameters: If your PowerShell script requires any parameters, you can provide them here.

• 5. Save your flow and test it to ensure it's working as expected.

• By using the "Run PowerShell Script" action, you can integrate PowerShell commands and scripts into your Power Automate
flows to perform various tasks, such as managing systems, interacting with external services, or automating administrative
tasks.
 What are the challenges you faced while moving Power
automate flows from Test environment to Production
environment
• 1. Environment Configuration: Configuring the production environment to support the Power Automate flows
and their dependencies can be challenging. This includes setting up connections, authentication, and access rights
in the target environment.
• Solution: I ensured that the required connections and credentials were properly configured in the production
environment. I collaborated with the IT or system administrators to set up the necessary permissions and access
rights for the flows and their associated resources.

• 2. Data Source Mapping: Power Automate flows often interact with various data sources, such as SharePoint,
Dataverse, or external systems. Mapping these data sources from the test to the production environment can be
complex, especially when dealing with different configurations or connection details.
• Solution: I documented the data sources used in the flows and their corresponding configurations during the
development phase. Before moving the flows to the production environment, I verified that the data source
connections were established and tested their functionality. I made sure to update any relevant connection or
authentication details to align with the production environment.
• 3. Dependency Management: Power Automate flows might rely on other resources, such as custom connectors, APIs, or shared data connections. Ensuring
that these dependencies are correctly configured and accessible in the production environment can be challenging.
• Solution: I created a detailed inventory of the dependencies required for each flow, including custom connectors, APIs, and shared resources. I verified that
these dependencies were available and properly set up in the production environment. If needed, I recreated or reconfigured the dependencies to align with
the production environment's specifications.

• 4. Error Handling and Monitoring: Identifying and resolving any errors or issues that arise during or after the migration process is crucial to ensure smooth
operation in the production environment.

• Solution: I conducted thorough testing of the flows in the production environment before deploying them to ensure their functionality and identify any potential
issues. I monitored the flow execution using the Power Automate admin center or other monitoring tools to track any errors or anomalies. I implemented
appropriate error handling mechanisms and logged relevant information for troubleshooting purposes.

• 5. Change Management and Communication: Moving flows to the production environment involves coordinating with stakeholders, ensuring proper
documentation, and communicating changes effectively to end users.

• Solution: I established a change management process that included version control, release notes, and communication plans. I coordinated with
stakeholders to schedule the migration during a suitable time frame to minimize disruptions. I provided documentation or training materials to end users to
help them understand the changes and any potential impacts.

• By addressing these challenges proactively and following best practices for migration and deployment, I ensured successful movement of Power Automate
flows from test environments to production environments, minimizing disruptions, ensuring data integrity, and providing a reliable automation solution.
What is environment and solutions in Power automate and what are its
benefits?
In Power Automate, an environment is a logical container that represents a specific instance of Power Automate. It encapsulates
resources such as flows, connections, gateways, and data gateways. Environments provide a way to separate and manage different
sets of resources and configurations within the Power Automate platform. They allow for segregation of development, testing,and
production environments, ensuring controlled access and management of resources.

A solution, on the other hand, is a package that contains a collection of related resources, such as flows, connectors, gateways, and
data gateways, that can be exported and imported across different Power Automate environments. Solutions allow for the
packaging and deployment of resources in a structured and portable manner. They help maintain consistency and facilitate the
movement of assets between environments, ensuring smooth development, testing, and deployment processes.

Here are some key uses and benefits of environments and solutions in Power Automate:

1. Separation of Environments: Environments provide a way to separate different stages of development, such as development,
testing, and production. Each environment can have its own set of resources and configurations, ensuring isolated and controlled
environments for various purposes.

2. Resource Management: Environments enable centralized management of resources, including flows, connections, and gateways.
They allow administrators to control access, permissions, and security settings for these resources within each environment.
3. Collaboration and Teamwork: Environments facilitate collaboration among multiple users and teams. Different users can work on
different environments simultaneously, ensuring parallel development, testing, and deployment efforts. Environments provide a
structured and organized way to manage shared resources and promote teamwork.

4. Solution Packaging and Deployment: Solutions help package related resources into a portable format that can be easily exported
and imported across different environments. They allow for the controlled movement of assets, including flows, connectors, an d
settings, from one environment to another. Solutions ensure consistency and simplify the deployment process across environments.

5. Version Control and Release Management: Solutions support version control, allowing developers to track changes made to
resources over time. They enable the management of releases and provide the ability to rollback or restore previous versions if
needed. Solutions facilitate proper release management practices, ensuring controlled and reliable deployments.

6. Application Lifecycle Management: Environments and solutions together provide a comprehensive application lifecycle
management (ALM) approach within Power Automate. They allow for the seamless progression of applications from development
to testing and ultimately to production, with controlled migration and resource management along the way.

By utilizing environments and solutions in Power Automate, organizations can effectively manage their automation assets, promote
collaboration, maintain consistency, and streamline the development and deployment processes across different environments.
More to come...
• Be in touch...
• [email protected]