The Get Text activity is used to extract the text value of a specified UI element. It does not use any of the scraping methods by default, but it can be configured to use the Full Text method in the Properties panel. The Full Text method is able to capture hidden text from an application, as well as the entire visible text and editable text. The Full Text method uses an internal OCR engine that works with most applications and languages.
References:
Get Text activity documentation from UiPath
Screen Scraping Methods documentation from UiPath
Text scrapping forum post from UiPath Community
How to: Scrape the Whole Text, Including Hidden Elements from a Terminal Window article from UiPath Knowledge Base

The Show Elements button in the Computer Vision wizard is used to toggle the highlighting of all UI elements that have been detected by the Computer Vision engine on the target application. This helps to visualize the accuracy and scope of the UI element recognition and to select the desired UI element for automation. (UiPath Automation Developer study guide) References:
Computer Vision
Computer Vision Wizard

According to the UiPath documentation, the Try Catch activity requires at least one catch to be added1. If there is no catch defined for the Try Catch activity, the workflow will not pass the validation and will not execute. The validation error message will say: "Try Catch: At least one catch must be added to the Try Catch activity." Therefore, the outcome of executing a Try Catch activity with a sequence placed within the Try section and no Catches section present will be a validation error. References: Activities - Try Catch

* Strict selectors contain fixed attributes that define a UI element. These attributes can be edited or optimized for better resilience.
* The best way to view the complete list of attributes of a UI element is by using UI Explorer.
Why is A Correct?
# "Open in UI Explorer":
* This option provides access to all attributes of a UI element.
* Developers can modify, optimize, and make selectors more reliable.
* UI Explorer allows viewing multiple layers of selectors (strict & fuzzy).
References:
# UiPath Official Documentation - UI Explorer

The main benefit of importing profiling sessions is that it enables the analysis of potential flow issues in the automation workflows. By importing profiling sessions, the developer can examine previous runs and compare them with the current run. This can help the developer to identify which workflows or activities take longer to execute, which ones consume more resources, and which ones cause errors or exceptions. The developer can also use the Profiler app to visualize the profiling data and drill down into the details of each operation. This way, the developer can optimize the performance and reliability of the automation workflows and improve the user experience.
References:
Studio - Profile Execution - UiPath Documentation Portal
Process Mining - Application Profiling - UiPath Documentation Portal