Explanation
The percentages from the Test Explorer panel represent the coverage of the test cases, which is the ratio of the number of activities that are executed by the test cases to the total number of activities in the project. The higher the coverage, the more thorough the testing is. The coverage percentage is calculated for each test case, test set, and the entire project. You can view the coverage details in the Coverage sub-panel of the Test Explorer1.
References:
Test Explorer documentation from UiPath

Explanation
A screenshot of a computer Description automatically generated

The correct sequence for the computation of the signature for client apps that receive Orchestrator requests and need to check their authenticity is:
Retrieve the X-UiPath-Signature HTTP header. This header contains the signature of the request body, encoded in Base64. (UiPath Orchestrator documentation1) To obtain the raw signature bytes, decode the value of the header from Base64. You can use any tool or library that supports Base64 decoding. (UiPath Orchestrator documentation1) Compute the hash using SHA256 and the signing key (UTF-8 encoded). The signing key is a secret value that is shared between Orchestrator and the client app. You can use any tool or library that supports SHA256 hashing. (UiPath Orchestrator documentation1) Compare the computed signature to the value from X-UiPath-Signature HTTP header. If they match, then the request is authentic and has not been tampered with. If they do not match, then the request is invalid and should be rejected. (UiPath Orchestrator documentation1) References:
1: Webhooks - UiPath Orchestrator.

Explanation
Credential stores are secure locations where you can store and retrieve sensitive data such as robot credentials and credential assets1. Orchestrator supports the use of multiple credential stores and has built-in integrations with the following ones2:
Azure Key Vault: A cloud-based service that provides secure storage and management of secrets, keys, and certificates3.
CyberArk CCP: A component of the CyberArk Privileged Access Security Solution that provides centralized management and distribution of credentials to applications and robots4.
HashiCorp Vault: A tool that enables secure access to secrets and encryption keys across dynamic environments5.
Thycotic Secret Server: A web-based solution that protects privileged accounts and credentials from cyberattacks and insider threats.
BeyondTrust: A platform that offers privileged access management, remote access, and vulnerability management solutions.
CyberArk: A leader in privileged access management that secures credentials, sessions, and endpoints across hybrid and cloud environments.
Therefore, option A is the correct answer, as it lists all the credential stores that have built-in support in Orchestrator. Option B is incorrect because it includes Cisco and Google Credentials, which are not credential stores supported by Orchestrator. Option C is incorrect because it includes Amazon Security Services, which is not a credential store supported by Orchestrator. Option D is incorrect because it includes Cisco, Amazon Security Services, Microsoft SCS, and IBM Vault, which are not credential stores supported by Orchestrator.

Explanation
When the activity encounters a NullReferenceException, the Finally block is not executed and a runtime error occurs. This is because the Catches section of the Try Catch activity only handles the ArgumentException type, which is a specific type of exception that occurs when one of the arguments provided to a method is not valid1. A NullReferenceException is a different type of exception that occurs when there is an attempt to dereference a null object reference2. Since the Catches section does not have a handler for the NullReferenceException type, the exception is not caught and the execution is stopped with a runtime error. The Finally block, which contains the activities that are always executed regardless of the outcome of the Try Catch activity, is also skipped3. References: ArgumentException Class, NullReferenceException Class, and Try Catch from UiPath documentation.

Explanation
The Assign activity is used to assign a value to a variable. In this case, the variable is "qty". The value of the variable will be 80 after executing the Assign activity because the expression in the Assign activity is
"dt.AsEnumerable().Where(Function(x) x("Item").ToString.Equals("mango")).Select(Function(y) y("Quantity")).ToString". This expression is filtering the data table "dt" for rows where the "Item" column is equal to "mango" and then selecting the "Quantity" column from those rows. Since there is only one row in the data table where "Item" is equal to "mango", the value of the "Quantity" column in that row is 80. (UiPath Studio documentation) References:: [Assign - UiPath Activities].