To check how many resources are utilized in a personal workspace in UiPath Orchestrator, you can use the See Usage option that displays the current consumption of resources for each workspace. You can also see the total number of resources allocated to all personal workspaces in your tenant. (Orchestrator - Personal Workspaces - UiPath Academy)

The Tenant context in UiPath Orchestrator allows management of tenant-wide settings, licenses, and entities.
* Tenant-level actions include:
* Managing licenses for attended/unattended robots.
* Configuring tenant-wide settings such as security policies.
* Managing users, roles, and permissions across folders.
# Why other options are incorrect:
* A (Assets & Storage Buckets): Managed at the folder level, not tenant level.
* C (Test Cases & Executions): Specific to folders, not tenant-wide.
* D (Folder Roles & Mixed Roles): Roles are assigned at the folder level, not tenant level.
# Reference: UiPath Orchestrator - Tenant vs Folder Context

A static selector is a selector that has fixed values for the attributes of the target element, such as name, id, class, etc. A static selector is appropriate to use when the target element's attributes do not change during runtime, meaning they are always the same regardless of the state of the application or the environment. A static selector is more reliable and faster than a dynamic selector, as it does not require any variables or arguments to identify the target element. A static selector is not suitable for situations where the target element's properties change frequently, such as when the element is generated dynamically, or when the automation requires high flexibility, such as when the element can have different names or ids depending on the input or output data. In those cases, a dynamic selector is preferred, as it can use variables or arguments to adjust the attribute values according to the changes in the target element. References: Dynamic Selectors, Selectors

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.

Variables and arguments are both used to store and pass data in UiPath, but they have some differences in their scope and direction. Variables are used to pass data between activities within the same workflow file.
They have a default direction of In/Out, which means they can be read and written by any activity in the workflow. Arguments are used to pass data between different workflow files. They have a specific direction of In, Out, or In/Out, which means they can only be read or written by the workflow that invokes them or the workflow that is invoked. Variables and arguments can have different data types, such as String, Int32, Boolean, etc. Variables can be assigned to an argument value, but arguments cannot be assigned to a variable value. References: Managing Arguments, Variables, Arguments, and Control Flow in Studio, Different between variables and arguments