PL-500 · Question #24
You create an unattended Office 365 automation. The automation stops running. You suspect that the runtime identity used by the automation caused the automation to stop running. Which two issues can…
The correct answer is B. The automation is attempting to open files that cannot be opened or edited based on per-user D. The automation is not set up to handle an additional sign-in UI element. Unattended automation issues often stem from the runtime identity's inability to access files due to permission restrictions or its failure to interact with unexpected UI elements, such as additional sign-in prompts.
Question
You create an unattended Office 365 automation. The automation stops running. You suspect that the runtime identity used by the automation caused the automation to stop running. Which two issues can the runtime identity cause in this scenario? Each correct answer presents a complete solution. NOTE: Each correct selection is worth one point.
Options
- AThe location of a specific user interface element has changed.
- BThe automation is attempting to open files that cannot be opened or edited based on per-user
- CThe unattended automation process suppressed an alert that was generated.
- DThe automation is not set up to handle an additional sign-in UI element.
How the community answered
(23 responses)- A4% (1)
- B83% (19)
- C13% (3)
Why each option
Unattended automation issues often stem from the runtime identity's inability to access files due to permission restrictions or its failure to interact with unexpected UI elements, such as additional sign-in prompts.
A change in the location of a specific user interface element is a design flaw in the automation script and not an issue caused by the runtime identity's permissions or capabilities.
Unattended automations run under a specific user account; if the automation attempts to access files that require specific per-user permissions or are locked, the runtime identity's access rights can cause the automation to fail.
Suppressing an alert is an action typically performed by the automation itself or configured within its error handling, not an issue caused by the runtime identity that would stop the automation from running.
An additional sign-in UI element that is not anticipated or handled by the automation design will block the flow because the unattended runtime identity cannot automatically interact with it without specific instructions.
Concept tested: Unattended automation runtime identity issues
Source: https://learn.microsoft.com/en-us/power-automate/desktop-flows/manage-machines#unattended-mode
Topics
Community Discussion
No community discussion yet for this question.