nerdexam
Microsoft

PL-500 · Question #170

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 B. No. Again, the answer is No - the proposed solution does not meet the requirements. This is part of a series where different solutions are evaluated against the same scenario. The challenge remains: the button can appear on two different pages and has a variable ID based on form…

Develop automations

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 on 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 Create a copy feature. Does the solution meet the goal?

Options

  • AYes
  • BNo

How the community answered

(35 responses)
  • A
    34% (12)
  • B
    66% (23)

Explanation

Again, the answer is No - the proposed solution does not meet the requirements. This is part of a series where different solutions are evaluated against the same scenario. The challenge remains: the button can appear on two different pages and has a variable ID based on form selections. A valid solution must handle both conditions - the variable page location and the variable element ID. Common correct approaches include using a UI selector based on stable text content (e.g., 'Submit' label), using conditional branching to detect which page is active, or using a wildcard/partial match selector. Any solution that does not account for both the page variability and the ID variability will be insufficient.

Topics

#UI element identification#Web automation#Dynamic selectors#Power Automate

Community Discussion

No community discussion yet for this question.

Full PL-500 Practice