Exam strategy
Software Engineering MCQ Trap Guide
Distractor patterns from AMU, Haramaya, MoEE, and national SWE model exams — keyed items plus extracted stems across 12 core courses.
6-step elimination flow
Run this on every hard item — takes under 15 seconds once practiced.
- 1
Read the lead-in first
Know whether you need a definition, complexity class, NOT/EXCEPT, SDLC phase, or protocol layer.
- 2
Predict before peeking
Cover the options. Name the layer, phase, or complexity before looking at letters.
- 3
Eliminate aggressively
Cross out options that belong to the wrong testing level, SQL class, or OOP rule.
- 4
Compare survivors by verb
Between two plausible options, match the stem's primary verb or constraint exactly.
- 5
Apply last-resort heuristics
Prefer the more specific complete option; on NOT questions eliminate the 'most textbook' distractor first.
- 6
Commit or flag
Explain your choice in one sentence. If you cannot, flag and move on.
15-second mental checklist
- 1.What is the stem asking? (define / NOT / complexity / layer / phase)
- 2.What was my prediction before I looked at the options?
- 3.Are two options from the same topic but different levels?
- 4.Does each surviving option match the stem's verb exactly?
- 5.Any = vs ==, DDL vs DML, or scheduler name trap?
- 6.Can I explain this in one sentence? If yes → commit.
22 trap patterns
Tap a category, then study each pattern. After every wrong answer in practice, name which trap got you.
Familiar API names or buzzwords in the wrong layer or phase.
High-frequency BME traps
Themes that repeat across Jimma, Gondar, Hawassa, and the national bank.
| Theme | Classic trap | Correct instinct |
|---|---|---|
| Software Engineering | Aggregation vs composition in UML | Whole-part lifetime → composition |
| Operating Systems | Scheduler name vs duration | Short-term = CPU dispatcher |
| Networks | Port vs protocol | Layer first, then service |
| Databases | Normalization vs dependency | Functional dependency drives normal form |
| Testing | Validation artifact vs test level | Mockups validate; unit tests verify code |
Strategic guessing
Answer-key distribution for keyed SWE items is shown under Key patterns. Use elimination first — letter stats are tiebreakers only when you are genuinely stuck.
View answer key probabilities