PL-500 · Question #195
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might…
The correct answer is A. Yes. The Test feature allows you to verify whether the selector is working properly by testing it on the web application. However, this feature alone does not solve the problem of the button having dynamic behavior (changing its ID and function based on selections in the form).
Question
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen. You are building an RPA for a web application. The automation populates and submits a form. You observe that the Submit button required for form submission is sometimes located on the second page. When the Submit button is on the first page, it functions as a Next button with a different ID, depending on the selections made in the form. You need to configure a UI element for the Submit button that works in both scenarios. Solution: Use the Test feature. Does the solution meet the goal?
Options
- AYes
- BNo
How the community answered
(20 responses)- A80% (16)
- B20% (4)
Explanation
The Test feature allows you to verify whether the selector is working properly by testing it on the web application. However, this feature alone does not solve the problem of the button having dynamic behavior (changing its ID and function based on selections in the form).
Community Discussion
No community discussion yet for this question.