Skip to content
CS Exit Ethiopia
Computer Science Exit Exam

Revision outlines for all sixteen courses

Review the complete study guide through short, nested recall cues. Open a topic, explain its cues aloud, then reveal the explanation to check your understanding.

646 teaching topics · 12385 revision cues

Use the outlines to review topics and test your recall. Expand each explanation to check your understanding after recalling a cue.

Web Programming

9 / 100 blueprint items

41 topics · 821 cues · 305 questions

Compiler Design

6 / 100 blueprint items

43 topics · 717 cues · 200 questions

How to revise without skipping topics
  • Explain each cue before revealing its explanation.
  • Work through every topic, including unmarked topics.
  • Mark a topic reviewed after testing recall.
  • Use related questions to check understanding.
  • Export progress before changing browsers or computers.

[Exam Focus] marks topics explicitly linked to learning outcomes in the blueprint alignment of the complete note. It is a priority cue, not a reason to skip the other topics.

Study guidance from the complete note
A practical study cycle

Start with a small set of questions before reading. Mark the exact thing that stopped you: an unknown term, a rule, a calculation, a trace or a choice between alternatives. Use the question lookup to open the relevant section.

Read one section, close it, and explain the rule in your own words. Solve the question again and say why each other choice fails. Then change one assumption or input and solve the variation. This checks understanding beyond recognition.

  • A useful 60-minute session: 10 minutes of cold questions, 20 minutes of focused reading, 20 minutes of closed-book solving and 10 minutes updating an error log. Adjust the timing to your needs.
  • Revisit mistakes after a gap, for example the next day, several days later and the following week. These intervals are a practical starting plan, not a fixed learning law.
  • Record the section ID, your mistaken rule, the corrected rule and one boundary case. Keep the log short enough to review.
  • Mix related courses during revision: programming with data structures; databases with security; networking with administration. Explain how the same word changes meaning across contexts.
Open in full note
What to emphasize

Emphasize definitions, key differences, algorithm costs, SDLC models, databases, networking and security. Use short oral questions to check understanding and correct common misconceptions. Combine those habits with the tracing, calculation, design and diagnosis demanded by the Ministry learning outcomes.

Allocate revision by both exam share and your error log. A course with fewer items can still deserve more time if your foundations are weak. The blueprint is a planning baseline, not a prediction of exact questions.

  • Definitions: distinguish nearby concepts, not just their names.
  • Calculations: write units, formulas, assumptions and intermediate steps.
  • Code and SQL: check validity before tracing the text; state any changes before analyzing a corrected version.
  • Algorithms and protocols: know the input, decision rule, state change, termination and failure cases.
  • Design choices: state the criterion. A choice can change when cost, reliability, consistency or latency matters more.
Course groupItems in the 100-item blueprintRevision implication
Web Programming9Reserve extra practice for HTML, CSS, JavaScript, PHP, client/server behavior and safe data handling.
Data Structures and Algorithms7Trace operations and compare their assumptions and costs.
Each of the other fourteen courses6 eachStudy all sixteen; do not abandon a whole course based on a short note or an alleged repeated-question list.
Open in full note
How to handle exam traps

Underline NOT, FALSE, BEST and EXCEPT before comparing choices. Check whether the stem supplies enough facts to select one answer. A long scenario is not automatically an analysis question, and a familiar answer letter is not evidence.

When code is invalid, a diagram is absent, or two choices express the same rule, identify the clarification needed before answering. Learn the correct rule and the smallest clarification needed. Do not memorize an arbitrary key as a universal fact.

  • Distinguish worst case from average case, and an upper bound from a tight bound.
  • Check language version, SQL dialect, addressing assumptions, graph weights and tie-breaking rules.
  • For subnetting and scheduling, calculate rather than guess from a familiar number.
  • Use timed mixed papers only after you can explain your errors. Revisit the reading sections behind recurring mistakes.
Open in full note