Exam UiARD topic 1 question 9 discussion

See UIPATH academy, question straight from the courses

From Academy: Flowchart When to use it? When you have a complex flow with several conditions, a flowchart is at least visually much easier to understand and follow. When you need a flow that terminates only in one of several conditions. Flowcharts should be used only as the general workflow (with sequences nested inside), not for individual parts of projects (nested inside other workflows). State Machine When to use it? First of all, let’s understand what a state machine is. It is an abstract machine consisting of a finite number of pre-defined states and transitions between these states. At any point, based on the external inputs and conditions verified, it can be in only one of the states. State machines can be used with a finite number of clear and stable states to go through. Some examples from your daily life include vending machines, elevators or traffic lights. State machines are not to be overused - they should define only the skeleton of the project.

State machines are better to make transitions in between, while Flowcharts are more recommended when it comes to multiple decision making/branching

ANSWER IS D

State Machine - A rather complex structure that can be seen as a flowchart with conditional arrows, called transitions. It enables a more compact representation of logic and we found it suitable for a standard high-level process diagram of transactional business process templates (REFRAMEWORK). Flowchart - "... Arrows that can point anywhere closely resemble the unstructured GoTo proramming statement and therefore make large workflows prone to chaotic interweaving of activities." Answer is A State Machine

answer is D

Answer is D