1.
Basic Questions
1.1 What is RPA, and how does it differ from traditional automation?
• RPA (Robotic Process Automation) refers to the use of software robots or "bots" to
automate repetitive tasks and workflows traditionally carried out by humans.
• Basically it will mimic the actions what we do in system which has logics and no decision
makings.
• Traditional automation involves scripted automation, custom-built code, or manual
configurations to automate a process but typically lacks the flexibility and scalability that
RPA offers.
• RPA tools like Automation Anywhere allow non-technical users to build automation
workflows with minimal coding, making it accessible to business users and enhancing
scalability.
1.2 Explain Automation Anywhere and its main components.
• Automation Anywhere is an RPA platform that automates business processes through the
use of bots. The platform includes:
o Bot Creator: Used to design and develop bots.
o Control Room: A centralized hub for bot management, deployment, and
monitoring.
o Bot Runner: Executes bots on a machine or server.
o Bot Insights: Provides analytics and reporting on bot performance.
1.3 What is the Control Room in Automation Anywhere?
• The Control Room is the web-based management interface for Automation Anywhere. It
allows you to manage, deploy, and monitor bots across multiple Bot Runners. The Control
Room also handles user authentication, role management, and scheduling of tasks.
1
1.4 Describe the types of bots available in Automation Anywhere.
Bot Creator and Bot Runner
Bot Creator has the below types of Bot types in AA
• Task Bots: Automate repetitive tasks like data entry or file management.
• IQ Bots: Use AI and ML to process unstructured data (e.g., invoices, receipts).
• MetaBots: Reusable automation components that can be utilized across different bots for
consistency. (DLL’s and API’s)
• Bot Runner: Executes automation tasks created in the Bot Creator.
Note: A360 has 2 types of bots-Tas Bot and IQ bot.meta bots are integrated to normal commands
where we have DLL’s
2
1.5 What is the difference between attended and unattended automation?
• Attended Automation requires human intervention and is typically triggered by a user
action (e.g., clicking a button).
• Unattended Automation runs independently, typically scheduled or triggers (file
exists/email receives etc), and does not require user interaction. It's best for back-office
processes.
2. Bot Building and Features
2.1 How do you create a simple bot in Automation Anywhere?
• To create a simple bot, you would:
1. Open the Bot Creator in the Automation Anywhere platform.
2. Use prebuilt commands like "Open Application," "Keystrokes," and "Data
Extraction" to automate the process.
3. Save and test the bot to ensure it performs the desired tasks.
2.2 Explain the use of the recorder feature in Automation Anywhere.
• The Recorder feature captures your actions, such as mouse movements and keyboard
inputs, and generates automation steps based on them. It's particularly useful for
automating repetitive tasks like data entry and web navigation.
2.3 What is Object Cloning, and when would you use it?
• Object Cloning allows you to interact with application UI elements (like buttons, text
fields, or images) as objects. It’s used when automation needs to work with non-HTML or
desktop applications where traditional methods might not be sufficient.
2.4 How does Error Handling work in AA, and why is it important?
3
• Error handling in Automation Anywhere is crucial for ensuring smooth automation. It
allows bots to handle unexpected scenarios (e.g., application crashes, missing data) using
commands like Try-Catch, logging errors, or sending notifications to the user.
2.5 Can you explain the concept of Metabots and how they are used?
• MetaBots are reusable components that allow you to encapsulate complex automation
tasks (like login procedures or data extraction routines) into one object. MetaBots are
reusable in multiple bots, improving consistency and reducing development time.
2.6 How does Automation Anywhere handle variable data types?
• Automation Anywhere supports various data types like String, Integer, Boolean, Date,
and List. Variables can be used to store data that bots can manipulate throughout the
process, allowing dynamic interaction with the system.
2.7 Describe the Workflow Designer in AA and its significance.
• The Workflow Designer is the environment where bots are designed. It provides a drag-
and-drop interface to define the steps in a bot, including conditional branching, loops, and
the integration of commands. It is significant because it provides a visual representation of
the process, making bot development easier and more intuitive.
3. Advanced Questions
3.1 What is IQ Bot, and how does it differ from a Task Bot?
• IQ Bot leverages artificial intelligence and machine learning to process unstructured data,
such as invoices or emails. It is capable of learning from data and improving over time.
• Task Bots, on the other hand, are designed to automate structured, rule-based processes
without AI or learning capabilities.
3.2 How do you work with unstructured data in Automation Anywhere?
• Unstructured data (e.g., PDFs, images, emails) is processed using IQ Bot in Automation
Anywhere. IQ Bot uses AI algorithms to extract key data, categorize information, and feed
structured data into downstream systems or processes.
3.3 What are reusable components, and how do you create them in AA?
• Reusable components are predefined, modular tasks or processes (such as logging in or
data extraction) that can be shared across different bots. These can be created using
MetaBots or by designing reusable scripts within the bot workflow.
3.4 Explain the function and advantages of Automation Anywhere’s Bot Store.
4
• The Bot Store is a marketplace where users can download prebuilt bots and components
created by Automation Anywhere or third-party developers. It helps accelerate RPA
implementation by providing ready-made solutions for common business processes.
3.5 Describe the use of triggers in AA for event-based automation.
• Triggers in Automation Anywhere are used to initiate bots based on specific events (e.g.,
file uploads, emails received, or a database update). Triggers can be configured to start a
bot when a predefined event occurs, enabling real-time automation.
3.6 How do you use looping and conditional statements in a bot?
• Looping (using commands like "For Each" or "While") allows bots to perform actions on
multiple items (e.g., iterating through a list of files).
• Conditional statements (e.g., "If-Else") let you control the flow of execution depending
on specific conditions, ensuring dynamic decision-making during automation.
4. Control Room and Administration
4.1 What are roles and permissions in the Control Room?
• Roles and permissions define what actions users can perform within the Control Room.
Administrators can configure roles like "Bot Creator," "Bot Runner," and "Control Room
Manager" to grant appropriate access and control over bots, processes, and reports.
4.2 How do you deploy a bot from the Control Room to a Bot Runner?
• To deploy a bot from the Control Room:
1. Ensure the bot is developed and tested.
2. Select the bot in the Control Room.
3. Assign it to a Bot Runner.
4. Schedule or trigger the bot for execution.
4.3 What are the main differences between Enterprise Control Room and Community
Edition?
• The Enterprise Control Room is intended for large-scale RPA deployments, providing
advanced features like multi-tenancy, enhanced security, and scalability.
• The Community Edition is a free, smaller-scale version of the Control Room, suitable for
personal use or small teams.
4.4 Explain how version control works in AA.
• Version control in Automation Anywhere allows you to manage and track changes made
to bots. It ensures that the correct version of a bot is deployed and used in production.
Users can roll back to previous versions if needed.
4.5 What is bot scheduling, and how do you set it up in AA?
5
• Bot scheduling allows you to specify when a bot should run automatically (e.g., at a
specific time, daily, weekly). In the Control Room, you can set the desired schedule for
bots to run based on business requirements.
Steps to Schedule a Bot in Automation Anywhere A360:
Step 1: Log in to Control Room
• Open your browser and go to your Automation Anywhere Control Room URL.
• Log in using your credentials (username and password).
Example login screen for Automation Anywhere Control Room.
Step 2: Navigate to the Bot Section
• Once logged in, from the left navigation pane, click on Bots.
Navigation to the Bots section in Automation Anywhere Control Room.
Step 3: Select the Bot to Schedule
• From the Bots page, find the bot you want to schedule.
• Click on the bot name to open the bot details.
List of bots available in Control Room.
Step 4: Open the Schedule Tab
• Inside the bot details page, you will see a Schedule option in the top-right corner.
• Click on Schedule to start configuring the bot schedule.
Click the “Schedule” option on the bot details page.
Step 5: Set the Schedule for the Bot
• In the Schedule Bot window, you need to configure the following:
o Start Date and Time: Select the date and time when the bot should first run.
o Frequency: Choose how often the bot should run (e.g., Daily, Weekly, Monthly,
or Custom).
o Time Zone: Ensure the correct time zone is set for execution.
o End Date (Optional): You can choose to specify an end date or leave it blank for
ongoing scheduling.
Scheduling window with options to set start time, frequency, and time zone.
6
Step 6: Select Bot Runner
• Choose the Bot Runner (the machine where the bot will run).
• You can either select an existing Bot Runner or configure a new one if required.
Choose the Bot Runner from the list.
Step 7: Set Notifications (Optional)
• If you want to be notified about the execution status (success or failure), you can enable
Notifications.
o You can opt to receive notifications via email or SMS.
Enable notifications for bot execution status.
Step 8: Save the Schedule
• After configuring the schedule, click Save to finalize the bot schedule.
Click on "Save" to schedule the bot.
Step 9: Monitor and View Scheduled Bot
• Once the bot is scheduled, you can view it in the Scheduler tab in the Control Room.
• You can monitor the bot's status, view execution logs, and make any adjustments if
necessary.
Scheduled bot status and logs.
Additional Features:
• Time-based Triggering: You can schedule bots to run based on specific triggers (e.g.,
date, time, or even specific events).
• Error Handling: Ensure your bot includes proper error handling to deal with unexpected
issues during its scheduled execution.
• Bot Availability: Make sure the selected Bot Runner is available at the scheduled time
for the bot to execute.
5. Debugging and Troubleshooting
5.1 How do you debug a bot in Automation Anywhere?
7
• Use the Debug mode in Bot Creator to step through your bot’s execution. This helps
identify errors, unexpected behaviors, or issues with commands, and logs detailed
information to help diagnose problems.
5.2 What steps would you take to handle an unexpected bot failure?
• First, review the error logs and debug information.
• Identify the root cause (e.g., missing data, application failure, unexpected UI changes).
• Fix the issue and re-test the bot.
• Implement better error handling using Try-Catch blocks or add more detailed logging for
future troubleshooting.
5.3 Describe the use of log files for troubleshooting in Automation Anywhere.
• Log files capture detailed information about bot execution, including any errors or issues
encountered. These logs are essential for identifying what went wrong and where the
failure occurred.
5.4 How can you manage error handling for unanticipated scenarios in bots?
• Use Error Handling techniques like Try-Catch blocks, sending email alerts, and
logging errors to provide insights into failures. This ensures bots can handle unexpected
issues and alert the user when necessary.
6. Real-World Application and Experience-Based Questions
6.1 Describe a project where you implemented an RPA solution with Automation Anywhere.
• Share details of the problem, process automation steps, and outcomes. Include specifics
like what bots were used (task bots, IQ bots), challenges faced (e.g., unstructured data),
and how Automation Anywhere solved them.
6.2 What challenges did you face, and how did you overcome them?
• Discuss challenges like dealing with unstructured data, changing system environments, or
ensuring bot reliability. Highlight any debugging or error handling techniques used to
overcome those challenges.
6.3 How would you assess a process to determine if it’s suitable for automation?
• Look for processes that are rule-based, repetitive, high volume, and stable. Ensure the
process is not too complex and that it can be executed without human intervention.
6.4 Describe how you optimized a bot to improve efficiency or performance.
• Discuss optimizing bot execution time by reducing unnecessary steps, using efficient
loops, or improving error handling to avoid delays.
8
7. Scenario-Based Questions
7.1 If you need to automate an end-to-end process for invoice processing, which types of bots
would you use and why?
• IQ Bot for processing invoices and extracting data from unstructured documents. Task
Bots for performing the backend automation like data entry, updating systems, and
generating reports.
7.2 How would you handle a situation where a bot fails due to a website layout change?
• Update the bot’s object-cloning steps, adjust XPath or UI element identification methods,
and re-test the automation after the layout update.
7.3 Given a scenario with sensitive data, how would you ensure data security in your bot?
• Use Encryption for storing sensitive data, Secure credentials management, and ensure
that bots follow data security policies (e.g., GDPR, CCPA).
• Use credential vault to store credentials-username and password.
• Create locker where it is going to store credentials.
9
7.4 How would you set up a bot to run on a schedule but only during specific conditions?
• Use conditional statements to check for the specific conditions before triggering the bot’s
execution, or integrate with external systems (e.g., databases or APIs) for the condition
check.
Steps to Schedule a Bot in Automation Anywhere A360:
Step 1: Log in to Control Room
• Open your browser and go to your Automation Anywhere Control Room URL.
• Log in using your credentials (username and password).
Example login screen for Automation Anywhere Control Room.
Step 2: Navigate to the Bot Section
10
• Once logged in, from the left navigation pane, click on Bots.
Navigation to the Bots section in Automation Anywhere Control Room.
Step 3: Select the Bot to Schedule
• From the Bots page, find the bot you want to schedule.
• Click on the bot name to open the bot details.
List of bots available in Control Room.
Step 4: Open the Schedule Tab
• Inside the bot details page, you will see a Schedule option in the top-right corner.
• Click on Schedule to start configuring the bot schedule.
Click the “Schedule” option on the bot details page.
Step 5: Set the Schedule for the Bot
• In the Schedule Bot window, you need to configure the following:
o Start Date and Time: Select the date and time when the bot should first run.
o Frequency: Choose how often the bot should run (e.g., Daily, Weekly, Monthly,
or Custom).
o Time Zone: Ensure the correct time zone is set for execution.
o End Date (Optional): You can choose to specify an end date or leave it blank for
ongoing scheduling.
Scheduling window with options to set start time, frequency, and time zone.
Step 6: Select Bot Runner
• Choose the Bot Runner (the machine where the bot will run).
• You can either select an existing Bot Runner or configure a new one if required.
Choose the Bot Runner from the list.
Step 7: Set Notifications (Optional)
• If you want to be notified about the execution status (success or failure), you can enable
Notifications.
o You can opt to receive notifications via email or SMS.
Enable notifications for bot execution status.
11
Step 8: Save the Schedule
• After configuring the schedule, click Save to finalize the bot schedule.
Click on "Save" to schedule the bot.
Step 9: Monitor and View Scheduled Bot
• Once the bot is scheduled, you can view it in the Scheduler tab in the Control Room.
• You can monitor the bot's status, view execution logs, and make any adjustments if
necessary.
Scheduled bot status and logs.
Additional Features:
• Time-based Triggering: You can schedule bots to run based on specific triggers (e.g.,
date, time, or even specific events).
• Error Handling: Ensure your bot includes proper error handling to deal with unexpected
issues during its scheduled execution.
• Bot Availability: Make sure the selected Bot Runner is available at the scheduled time
for the bot to execute.
12
