The recommended type of workflow for designing a complex business process using UiPath Studio is Flowchart. Flowcharts are suitable for a more complex business logic, as they enable you to integrate decisions and connect activities in a more diverse manner, through multiple branching logic operators. Flowcharts can also be used as a part of other diagrams, such as Sequences or State Machines3.
Flowcharts provide a clear and visual representation of the flow of the process, as well as the possible outcomes and exceptions. Flowcharts can also be easily modified and expanded, as new activities and branches can be added or removed4. References: Flowchart and Understanding the Concept of Workflow of UiPath from UiPath documentation and Medium.

Explanation:
To configure the Filter Data Table Wizard to keep all invoices with a Total value that is over 10 000 USD, you should choose the following options from the drop-down lists:
Column: Total Operation: > Value: 10000
The reason for choosing these options is to filter the data table based on the condition that the Total column value is greater than 10000. This will keep only the rows that satisfy this condition and remove the rest. You can learn more about the Filter Data Table activity and how to use it from the following sources:
* Four Ways to Filter Data Tables in UiPath Studio | UiPath
* How to Filter Data Table - Help - UiPath Community Forum
* Filter Data table with specific column - UiPath Community Forum

The code is adding two items to the list, but since the list is initialized as an empty list, the count will be 0.
References:
* Data Manipulation with Lists and Dictionaries in Studio course, Lesson 2: Lists, Topic: Creating Lists
* How to initiate List<String[]>? forum post, Answer by @VishalS

This is the best option because it follows the best practices for using queues and assets in Orchestrator.
Queues are used to store and process multiple items of data that need to be processed separately, such as invoices. Each invoice can be uploaded as a queue item with the invoice data as Specific Data, which can be accessed and manipulated by the automation process. Assets are used to store and share global information that is constant or rarely changes, such as the finance team email address. An asset can be created for the email address and retrieved by the automation process when needed. The other options are not optimal because they either use assets for data that is not global or constant, or they use queues for data that is not related to the items to be processed. References: About Queues and Transactions, About Assets

UiPath Attended Robots do not require Windows credentials to be connected to Orchestrator, because:
* They run under the currently logged-in user and do not require a predefined Windows username
/password.
* Attended Robots must be manually triggered by a user and cannot run automatically like Unattended Robots.
* They do not require a remote desktop session like Unattended Robots.
Why Other Options Are Incorrect?
* A (UiPath Robots can be deleted if they have pending or active jobs in UiPath Orchestrator.) #
* Incorrect. Robots cannot be deleted if they have active or pending jobs in Orchestrator.
* Solution: You must stop or remove pending jobs before deleting the robot.
* B (Unattended robots can be connected to UiPath Orchestrator without the Windows username.)
#
* Incorrect. Unattended Robots require Windows credentials to log in and execute tasks without user intervention.
* C (UiPath Orchestrator consumes the Queue Items uploaded to the UiPath Robot.) #
* Incorrect.
* Orchestrator manages and distributes Queue Items to Robots.
* Robots consume the Queue Items, not Orchestrator.
References:
* UiPath Orchestrator Official Docs
* UiPath Attended vs. Unattended Robots