To filter rows in a DataTable based on a condition (e.g., Quantity > 500), the best activity to use is Filter Data Table.
Why is Option D Correct?
* Filter Data Table allows filtering rows based on specific conditions (e.g., Quantity > 500).
* It can be configured via UI settings or using expressions in the advanced filter options.
* The result is stored in a new or existing DataTable.
Example Usage in UiPath Studio:
* Drag the Filter Data Table activity into the workflow.
* Set Input DataTable = dtInput
* Set Output DataTable = dtFiltered
* Configure the filter condition:
vbnet
CopyEdit
Column: "Quantity"
Operator: "Greater than"
Value: 500
* Now, dtFiltered contains only rows where "Quantity" > 500.
Why Other Options Are Incorrect?
* A (Sort Data Table) #
* Sort Data Table only sorts data; it does not filter rows.
* B (Output Data Table) #
* Converts the DataTable into a string representation, used for display purposes, not filtering.
* C (Lookup Data Table) #
* Searches for specific values in a column but does not filter multiple rows.
References:
* UiPath Documentation - Filter Data Table
* UiPath Forum - Filtering DataTable Efficiently

The default URL of the OCR server that runs the Computer Vision service is https://cv.uipath.com/. This is the endpoint of the UiPath Computer Vision Cloud service, which provides OCR capabilities for document understanding and UI automation1. The other options are not valid URLs for the OCR server.
References:
* Document Understanding - UiPath.DocumentUnderstanding.OCR.LocalServer Activities documentation, Introduction section

Unattended robots are designed to run without human interaction. They can be triggered by events, schedules, or via a command from Orchestrator and are capable of executing processes independently. This is particularly useful for batch processing or automations that need to run at specific times without requiring a human to initiate them. Hence, the correct answer is D.
References:
UiPath Orchestrator Guide: About Robots

When a process is executed from the Start Job window in UiPath Orchestrator, the runtime value of an "In" argument in the "Main.xaml" file will be the value provided in Orchestrator if specified. If no value is provided in Orchestrator for this argument, then the default value specified in the "Main.xaml" file will be used, in this case, "String.Empty". Therefore, option C is correct. Arguments can be passed to the "Main.
xaml" file from Orchestrator, and there is a mechanism to handle default values for arguments in case they are not provided at runtime.References:
* UiPath Orchestrator Guide: Starting a Job
* UiPath Studio Guide: Managing Arguments

A Queue Item is moved to an "Abandoned" status in UiPath Orchestrator when the item was "In Progress" but the transaction status was never set to "Successful" or "Failed". This can happen when the item remained in the "In Progress" status for a long period of time (approx. 24 hours) without being processed, or when the Robot that was processing the item encountered an error or was stopped1. The "Abandoned" status indicates that the item was not completed and needs to be retried or deleted. The item can be retried manually from the Transactions page in Orchestrator, or programmatically using the API2. The item can also be deleted manually from the Transactions page, or automatically using the Auto Delete option in the Queue settings3. References: Queue Item Statuses, Changing the abandon status of Queue Transaction, and About Queues and Transactions from UiPath documentation and forum.