Explanation
The Activate property of the Type Into activity allows the developer to bring the specified UI element to the foreground and activate it before the text is written1. This property is useful when the web form fields are not visible or focused by default.

Explanation
The only step that requires human interaction is the first one, where the user is prompted for an input company name. The rest of the steps are performed by the automation process without any human intervention.

Explanation
The Invoke Code activity in UiPath is an activity that allows developers to execute custom code written in VB.NET or C# within a workflow. The activity can accept a list of input arguments and return a list of output arguments, which can be used to exchange data between the code and the workflow. The activity can also access the variables and arguments defined in the current scope of the workflow. The Invoke Code activity can be useful for scenarios where the existing activities do not meet the specific requirements or logic of the automation process. (UiPath Automation Developer study guide) References:
Invoke Code
How To Use Invoke Code Activity - In UiPath

Explanation
The App/Web Recorder is a tool that allows you to record your actions on an application or a web browser and generate activities automatically1. The App/Web Recorder has a toolbar that contains different actions that you can select before recording a step2. Some of these actions are:
Click: This action records a click on a button, link, or any other clickable element.
Type: This action records typing text in a text box or any other text area.
Check: This action records selecting or clearing a check box.
Send Hotkey: This action records sending keyboard shortcuts using your keyboard.
Select Item: This action records selecting an item from a drop-down list or any other selector.
These actions are automatically detected and recorded by the App/Web Recorder when you perform them on the application or web browser3. However, there are some actions that are not automatically detected and recorded by the App/Web Recorder, and you need to manually select them from the toolbar before recording a step. These actions are:
Get Text: This action records copying text from a label, paragraph, or any other text element.
Hover: This action records hovering over an element with your mouse cursor.
Highlight: This action records highlighting an element with a colored border.
These actions are useful for extracting data, triggering events, or identifying elements on the application or web browser4. To use these actions, you need to select them from the toolbar and then indicate the element on the screen that you want to apply them to5.
Therefore, option A is the correct answer, as it lists the actions that must be manually selected in the App/Web Recorder before recording a step. Option B includes some actions that are automatically detected and recorded by the App/Web Recorder, such as Click and Type. Option C also includes some actions that are automatically detected and recorded by the App/Web Recorder, such as Check and Send Hotkey. Option D includes all the actions that are automatically detected and recorded by the App/Web Recorder.

Explanation
Based on best practices, the selector attribute that is unreliable is innertext. The innertext attribute is the text content of a UI element, such as a table, a button, or a label. The innertext attribute is unreliable because it can change dynamically depending on the data or the state of the UI element. For example, the innertext attribute of a table can change when the table is updated with new values, or the innertext attribute of a button can change when the button is clicked or disabled. Using the innertext attribute in a selector can cause the selector to fail or to identify the wrong UI element if the text content is different from the expected value1. Therefore, the innertext attribute should be avoided or replaced with a more reliable attribute, such as tag, class, or title.
The tag attribute is the name of the HTML element, such as table, button, or input. The tag attribute is reliable because it does not change unless the UI element is replaced with a different element. The class attribute is the name of the CSS class that defines the style or the behavior of the UI element, such as ui_side_menu, btn-primary, or form-control. The class attribute is reliable because it does not change unless the UI element is styled or modified differently. The title attribute is the text that appears when the mouse pointer is hovered over the UI element, such as temperature now, submit, or username. The title attribute is reliable because it does not change unless the UI element is renamed or removed2.
References: Selectors with Wildcards and UiPath Selectors from UiPath documentation and forum.