Dictionaries in UiPath, as in other .NET environments, allow for keys and values to be of different data types.
Keys must be unique within a dictionary, but the values can be duplicates. Dictionaries do not provide automatic sorting; they are collections designed for quick lookup of values based on a key. Therefore, the correct answer is B.
References:
UiPath Studio Guide: The Dictionary Data Type

Connections are the core component of the UiPath Integration Service. They enable you to create and manage tasks and exchanges between users and external applications using the authentication process of the API provider. Each connection is associated with a specific connector, which defines the actions and triggers that can be performed on the external application. You can create connections in the Integration Service page of the Automation Cloud portal, and use them in your automation projects in Studio, StudioX, Apps, or Assistant. You can also share connections with other users or groups in your organization using folders and permissions1.
References: Integration Service - Connections - UiPath Documentation Portal

Explanation:

When a UI element selector changes, it can break automation. The proper debugging sequence ensures an effective fix while preventing future failures.
Step 1: Examine Error Logs
# First, review error logs in the Output Panel to locate the failing activity.
* This helps determine which selector is causing the issue.
* Use UiPath's Exception Details to pinpoint the problem.
Step 2: Verify Selector and Insert Breakpoint
# Open UI Explorer to inspect the failing selector.
* Compare the new selector vs. old selector.
* Use a Breakpoint at the failing activity to analyze execution in Debug Mode.
Step 3: Modify Selector for Flexibility
# Adjust the selector to make it more resilient by:
* Using Wildcards (*) for dynamic attributes.
* Implementing Anchor-based selectors.
* Utilizing Modern UI Automation if applicable.
Step 4: Execute in Debug Mode
# Run the automation in Debug Mode to verify that:
* The updated selector correctly identifies the UI element.
* No further exceptions occur during runtime.
References:
# UiPath Official Documentation - Debugging Workflows# UiPath Best Practices - Handling Selectors# UiPath UI Explorer Guide

The Global Exception Handler is an error handling mechanism for a project. By default, it retries an activity that continually throws an error 3 times. The Global Exception Handler is a workflow that is executed when an exception occurs in the project. It allows the developer to define custom actions for handling different types of exceptions, such as logging, retrying, aborting, or continuing the execution1. When the Global Exception Handler encounters an exception, it logs the name of the activity which faulted and starts retrying the activity three times. If it encounters the same exception each time and the number of retries reaches 3, the execution is aborted at the level of the activity which threw the exception2. The number of retries can be modified by changing the value of the RetryCount variable in the Global Exception Handler workflow3. References: Global Exception Handler and Global Handler for Exceptions from UiPath documentation and Marketplace.