You solve DSSSB Computer Science PYQs, check the score and move on without knowing why marks were lost. Use a repeatable three-pass loop instead: attempt, diagnose and repair. All timings and question counts below are personal practice settings, not an official DSSSB paper pattern.
Turn a PYQ set into evidence, not just a score
Make a six-column attempt sheet: question number, chosen answer, confidence (H/M/L), elapsed seconds, result against a trusted key and primary gap label. Give each flagged row one label so the ledger counts cleanly.
The example uses a learner-chosen 25-question Computer Science block, a 35-minute window and a 90-second move-on checkpoint to keep diagnosis manageable. Map the wider path through the DSSSB preparation courses. Keep the Computer Science ledger separate because Section A subjects need their own plan.
Pass 1: attempt under a clock without interrupting the evidence
Start one 35-minute timer. Record time in 10-second bands and mark confidence before checking. Near 90 seconds, move on. Use no notes, solution videos, answer keys or topic revision.
The 25 items produce 17 correct, 5 wrong and 3 blank, with 17 + 5 + 3 = 25. Four correct answers took longer than 90 seconds. That makes 12 flagged rows: 8 wrong or blank, plus 4 correct-but-slow. This is why PYQs should come before another generic question bank: they expose what a score hides.
Pass 2: separate recall, concept and time-loss gaps
Use one decision rule:
Recall gap: you cannot retrieve a fact, formula or conversion.
Concept gap: you misunderstand the rule, especially with a high-confidence wrong answer.
Time-loss gap: you know the method but cross your practice checkpoint.
Here are three constructed practice examples, not quoted DSSSB questions.
Recall row, Q4
Question: “A system uses 4 KiB pages. How many offset bits are required?” The learner answers 10 in 35 seconds with medium confidence. But 4 KiB = 4 × 1024 bytes = 4096 bytes = 2^12 bytes, so the offset needs 12 bits. This is a recall gap.
Concept row, Q11
Let R(A,B) = {(1,x), (2,y), (3,z)} and S(A,C) = {(1,p), (1,q), (3,r)}. The learner predicts 3 rows for R LEFT JOIN S ON R.A = S.A in 75 seconds with high confidence.
The four rows are (1,x,p), (1,x,q), (2,y,NULL) and (3,z,r). A=1 has two matches; unmatched A=2 remains with NULL. Missing one-to-many duplication and unmatched-row preservation makes this a concept gap.
Time-loss row, Q18
Evaluate postfix 8 2 3 * + 4 -: 2 × 3 = 6, 8 + 6 = 14, and 14 - 4 = 10. The learner gets 10 in 190 seconds against a personal 90-second checkpoint. This is execution loss, not concept failure.
Pass 3: convert every label into a small revision task
For Q4, make a recall card: 1 KiB = 2^10, 2 KiB = 2^11, 4 KiB = 2^12, 8 KiB = 2^13, 16 KiB = 2^14 and 32 KiB = 2^15. Solve six fresh variants, then retest closed-book after 48 hours.
For Q11, redraw the four-row LEFT JOIN, explain why A=1 expands and A=2 produces NULL, then solve three new join tables the next day. For Q18, trace five postfix expressions in token and stack columns, aiming for each to finish within a learner-set 75 seconds. Retest after 72 hours.
A gap closes only after two unseen variants are correct in separate sessions. For a time-loss gap, both must meet the learner's threshold. Use structured Section B revision to support these tasks.
Use a 6.5-hour weekly loop in three phases
Follow this flexible practice week:
Day | Practice task | Minutes |
|---|---|---|
Monday | Concept repair | 60 |
Tuesday | Recall drills | 45 |
Wednesday | 35-minute PYQ block, then first check | 60 |
Thursday | Timed execution drills | 45 |
Friday | Second PYQ block and initial check | 60 |
Saturday | Full diagnosis and task creation | 90 |
Sunday | Closed-book retest and ledger update | 30 |
The total is 60 + 45 + 60 + 45 + 60 + 90 + 30 = 390 minutes, or 6.5 hours.
Weeks 1 and 2 use two 25-question blocks per week, so four blocks give 4 × 25 = 100 attempts. In Weeks 3 and 4, keep one unseen block each week and repair the two most frequent labels. In Weeks 5 and 6, restore two unseen blocks per week and compare gap counts, not only scores. These settings are not an official duration, marks scheme, syllabus weight, date or vacancy count.
Recover from missed days without creating a catch-up pile
If you miss one 45- or 60-minute session, carry at most 30 minutes into Sunday and drop the rest. Do not double the next day, because fatigue can distort time-loss data.
If you miss two or more days, protect Wednesday's 60-minute PYQ block and Saturday's 90-minute diagnosis. Add a 15-minute recall drill before each: 60 + 90 + 15 + 15 = 180 minutes. Restart the normal 390-minute cycle on Monday. When time is scarce, retain one timed attempt, its diagnosis and one retest. Remove extra drills first.
Read the ledger without fooling yourself
Consider this learner example, not a platform benchmark. Week 1 has 12 primary gaps: 4 recall + 3 concept + 5 time-loss = 12. On an unseen 25-question block in Week 4, the learner has 6 gaps: 2 recall + 2 concept + 2 time-loss = 6. Accuracy moves from 17/25 to 21/25, while median time on answered items moves from 82 to 68 seconds.
Do not let one better score hide a persistent weakness. If accuracy rises but high-confidence concept errors remain at 3, the concept is not repaired. If memorised questions improve but unseen variants do not, the ledger shows familiarity, not mastery. Move from diagnostic blocks to broader mocks only after the gap ledger is shrinking, and never use mocks as a substitute for diagnosis.
Short version: attempt, label, repair, retest
Attempt one bounded PYQ block.
Label each flagged row once.
Assign a recall, concept or speed task.
Retest on unseen variants after 48 to 72 hours.
Prepare the six-column sheet and run one 25-question, 35-minute diagnostic block today. Computer Science learners can start with the structured Section B course linked above. For a separate general-section track, use the DSSSB Section A course.