Algorithm and flowchart: 28 MCQs with answers

A step-by-step procedure to solve a problem

An algorithm is a finite set of well-defined steps to solve a specific problem, not a visual or hardware.

Diamond

A diamond is used for decision points, leading to different branches based on a condition.

Input/Output

A parallelogram indicates input or output operations, like reading data or displaying results.

To visually represent the logic of an algorithm

A flowchart is a visual blueprint of an algorithm, helping to understand and communicate the logic.

Ovals or rounded rectangles

Ovals (or rounded rectangles) denote the beginning and end of a flowchart.

The sequence of steps and decisions

Flow lines show the order in which steps are executed, representing the control flow.

Rectangle

A rectangle represents a processing step, such as an arithmetic operation or assignment.

The direction of flow

Arrows show the direction of control flow from one step to the next.

Following a map to reach a destination

Following a map involves a step-by-step procedure to reach a goal, which is algorithmic.

True

Flowcharts use symbols and arrows to represent logic, so they can be purely visual.

False

An algorithm is a conceptual step-by-step procedure; it can be expressed in natural language or pseudocode.

Diamond

A diamond (or rhombus) is the standard flowchart symbol for a decision, with one entry and two or more exit paths labeled with conditions (e.g., Yes/No).

To indicate the sequence and control flow between steps

Arrows in a flowchart represent the flow of control, showing the order in which steps are executed, including branches and loops.

Input or output operation

A parallelogram is used for input/output operations, such as reading a value from the user or displaying a result.

Flowcharts provide a visual clarity that makes logic easier to understand and debug

Visual representation helps humans grasp the overall structure, spot logical flaws, and communicate the algorithm more effectively than text alone.

It must have clear, unambiguous steps and terminate

A good algorithm is precise, unambiguous, and finite—it must end after a finite number of steps.

A recipe for baking a cake

A recipe is a step-by-step procedure to achieve a result, just like an algorithm.

Selection (if-else)

Comparing numbers requires decision-making, which is implemented using selection (if-else) structures.

It provides a visual clarity that simplifies understanding

Flowcharts make the logic visually explicit, which helps in understanding and debugging.

Write the code in a specific programming language

An algorithm is language-independent; writing code is a later step, not part of algorithm design.

To connect different parts of a flowchart, especially across pages

Connectors (usually circles) link parts of a flowchart to avoid crossing lines or to continue on another page.

It can become complex and unwieldy for large algorithms

For very large algorithms, flowcharts can become messy and hard to manage, which is a known limitation.

A flowchart is a graphical representation of an algorithm

An algorithm is a step-by-step logical procedure, while a flowchart translates that logic into a visual diagram using standardized symbols.

Forgetting to update the loop control variable

If the loop variable is not updated inside the loop, the condition never becomes false, causing an infinite loop—a classic flowchart error.

Checking each item in a shopping list until all are purchased

Looping is used when a set of steps must be repeated for each item, like iterating over a list until a condition (end of list) is met.

Start → Input three numbers → Compare first two, then compare result with third → Output largest → End

The logical sequence is to start, get inputs, perform comparisons in a structured manner (e.g., pairwise), then output the result and end.

True

Standard flowchart conventions require a single start (to avoid ambiguity) but allow multiple end symbols, e.g., when different branches terminate at different points.

Rectangle with double vertical lines

A rectangle with extra vertical lines on each side denotes a predefined process, indicating a named subroutine or module that is defined elsewhere.