Generate these sections in order (all inside the main-content div):
Text file reading writing searching and counting PYQ part 4 — Lecture 31
CBSE | XII CS | Computational Thinking and Programming – 2 | 35 min
1. Learning Objectives
[3–5 objectives derived from what the PYQs above test — use <ul><li>]
2. 35-Minute Lecture Flow
[HTML table: Time | Activity | Teacher Action — include a PYQ discussion and full-coverage slot]
3. Quick Concept Recap
[Keep this section short. Do NOT reteach the full topic from scratch.
Include only the rules needed to solve the PYQs — i.e. the traps listed in the
EXAMINER FINGERPRINT section above (for this lecture: Binary file operations with pickle, CSV file read write and search, Text file reading writing searching and counting, File basics paths modes seek and tell, Text file reading writing searching and counting, Text file reading writing searching and counting).
Use .def-box and .key-box only. Add at most one tiny example if needed.
Do not include long theory, long programming tasks, or unrelated examples.]
4. Examiner Tricks & Common Mistakes
[One .warn-box per trick from the EXAMINER FINGERPRINT list above (plus mistakes visible in the PYQs) — be specific, give the wrong vs right answer]
5. Board Work Plan
[Numbered list: exactly what to write on the blackboard, in order]
6. Classroom Practice Questions
[Modelled on PYQ style. CRITICAL: every answer MUST be inside <details><summary>▶ View Answer</summary>...</details> — never expose the answer directly.
Practice questions must follow the difficulty and mark pattern of the actual PYQ pool.
For this topic:
* 3×1M MCQ
* 5×1M/2M Short Answer
* Include 2×3–5M programming practice (the PYQ pool contains long-answer/programming patterns)
* Include 1 HOTS question (the PYQs reveal a genuine higher-order trap)
Every question must be based on one of the traps from Section 4 (EXAMINER FINGERPRINT).
Every answer must be hidden inside <details><summary>▶ View Answer</summary>...</details>.
MCQ structure:
<div class="mcq-box">
<b>Q1.</b> Question text?<br>
<ul class="options">
<li>a) ...</li>
<li>b) ...</li>
<li>c) ...</li>
<li>d) ...</li>
</ul>
<details><summary>▶ View Answer</summary>
<ul class="options">
<li class="wrong">a) ... — reason why wrong</li>
<li class="correct">b) ... ✓ — reason why correct</li>
...
</ul>
</details>
</div>
(Note: options list shown WITHOUT .correct/.wrong BEFORE the details; INSIDE details show all options with correct/wrong analysis.)
Short-answer structure:
<div class="self-test-box"><b>Q4.</b> Question<br><details><summary>▶ View Answer</summary>Full answer</details></div>
Dynamic distribution rule:
* If actual PYQs are only 1M/2M, keep generated practice mostly 1M/2M.
* If actual PYQs include 3M/5M programming, include 3M/5M programming practice.
* Never force HOTS or programming questions when the provided PYQ pool does not support them.]
7. PYQ Discussion / Full Coverage (8 source questions)
[This source pool has 8 actual PYQs.
PYQ COVERAGE RULE:
- This pool has 8 PYQs, so include and discuss ALL 8 actual PYQs in Section 7.
- Do not compress, replace, paraphrase, or skip any actual PYQ in this small pool.
- Compression is allowed only when the source pool has more than 15 questions.
- Never fabricate board years, marks, sections, or question text.
For every fully discussed actual PYQ include:
year · marks · type · full question text · concept tested · model answer inside <details> · common mistake inside <details>
Order questions Easy to Tough; within difficulty, order 1 mark → 2 marks → 3 marks → 4/5 marks.
Use this structure for actual PYQ examples:
Use this structure for each question:
<div class="pyq-box">
<div class="pyq-meta">[YEAR] · [X] Marks · [TYPE] · Section-[S]</div>
<b>Q.</b> [full question text — include code if any]<br><br>
<b>Concept tested:</b> [concept name]<br>
<details><summary>▶ View Model Answer</summary>
<b>Model Answer:</b> [full answer with code/table as needed, using .kw/.bi/.st token spans in <pre><code>]<br>
<b>Common mistake:</b> [what students get wrong — be specific]
</details>
</div>
]
8. Student Notes (Copy-ready)
[Concise notes — every concept from PYQs — in .key-box and .def-box; self-check questions in .self-test-box with <details><summary>▶ View Answer</summary>answer</details>]
9. Homework
[Homework must follow the actual PYQ pattern for this topic:
- 3×1M MCQ
- 3×1M Short Answer
- 2×2M Short Answer only if useful for recap or trap correction
- Include 2×3–5M programming homework (the PYQ pool contains long-answer/programming patterns)
- Every homework question must map to one trap or pattern from Section 4 / Section 7.
Dynamic rule: if actual PYQs are only 1M/2M, homework stays mostly 1M/2M; if they include 3M/5M
programming, homework may include 3M/5M programming; never force unsupported marks or question types.
EVERY answer must be wrapped in <details><summary>▶ View Answer</summary>...</details> inside .self-test-box or .mcq-box.]
10. Exam Tips
[5 specific tips as .tip-box — derived from PYQ patterns for THIS topic only]
11. Last-Minute Revision Cards
<div class="card-grid">
[One .card per concept: <div class="card-title">[concept]</div> + 1 rule + 1 example]
</div>