Generate these sections in order (all inside the main-content div):

Built-in modules and library functions Theory + PYQ — Lecture 20

CBSE | XII CS | Computational Thinking and Programming – 2 | 35 min

1. Learning Objectives

[3–5 objectives derived from the exam-importance analysis above (never naming PYQs) — use <ul><li>]

2. 35-Minute Lecture Flow

[HTML table: Time | Activity | Teacher Action — split the 35-minute lecture into: 15-18 min tight concept teaching; 4-5 min examiner traps and misconception correction; 10-12 min actual PYQ discussion; 2-3 min recap/exit check — use wording such as Theory teaching, concept check, PYQ discussion, model answer, marking point, common mistake; do NOT make the flow pure theory-only]

3. Concept Notes

[For EVERY sub-concept surfaced by the exam-frequency analysis, never naming or displaying actual board questions: - .def-box for definition with "In exam language: ..." line - .key-box with syntax/rules as <ul><li> - .example-box for worked examples - <pre><code> for code with .kw/.bi/.st/.cm/.nm token spans - .recall-box for output with exact expected output - after each important concept, embed 1–2 self-generated MCQ or Short Answer checks about THIS concept only - every Section 3 check question must hide its answer inside: <details><summary>▶ View Answer</summary>answer/explanation</details> - do not label any question as PYQ, previous year, board-style, PYQ-pattern, or PYQ-style - do not use .pyq-box or .pyq-meta here (in Combined mode .pyq-box is reserved for Section 7) ]

4. Examiner Tricks & Common Mistakes

[Create one .warn-box for each trap from the EXAMINER FINGERPRINT section. Each .warn-box must be specific and must include: - the mistake students commonly make - the correct rule - a tiny example or wrong-vs-right explanation Do not mention actual board questions, years, previous papers, PYQ, or source metadata.]

5. Board Work Plan

[Numbered list: exactly what to write on the blackboard, in order]

6. Classroom Practice Questions

[Self-generated from the examiner-trap patterns analysed above — never call these PYQ-pattern/PYQ-style/board-style. CRITICAL: every answer MUST be inside <details><summary>▶ View Answer</summary>...</details> — never expose the answer directly. 3×1M MCQ + 5×1-2M Short Answer only. Combined mode theory-section restriction: - Do NOT include actual PYQs. - Do NOT include programming/long-answer/HOTS questions in theory lecture practice. - Frame original MCQ/Short Answer questions from exam-frequency concepts and examiner traps only. - Every question must map to one concept/trap discovered in Section 4. 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> Short-answer structure: <div class="self-test-box"><b>Q4.</b> Question<br><details><summary>▶ View Answer</summary>Full answer</details></div>]

7. PYQ Discussion / Board Questions

[Since this is Combined Theory + PYQ mode, this section MUST include actual PYQs. Source pool has 11 PYQs. Because 11 <= 15, include ALL 11 actual PYQs. For each PYQ, use this structure: <div class="pyq-box"> <div class="pyq-meta">[YEAR] · [X] Marks · [TYPE] · Section-[S]</div> <b>Q.</b> [full actual question text]<br><br> <b>Concept tested:</b> [concept name]<br> <details><summary>▶ View Model Answer</summary> <b>Model Answer:</b> [answer]<br> <b>Marking point:</b> [what the examiner expects]<br> <b>Common mistake:</b> [student mistake] </details> </div> Rules: * Include all 11 actual PYQs. * Do not fabricate year, marks, section, or question text. * Model answer, marking point, and common mistake must be hidden inside <details>. * Question text and concept tested may remain visible. * Order Easy to Tough; within difficulty, order 1M → 2M → 3M → 4/5M. * If all questions are 1M, group them logically by concept pattern (e.g. identifiers, keywords, comments, Python basics).]

8. Student Notes (Copy-ready)

[Concise notes — every concept highlighted by the exam-frequency analysis, written purely as concept notes (no PYQ wording) — 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 exam pattern for this topic: - 4×1M MCQ - 4×1M Short Answer / True-False / one-line answer - 2×2M Short Answer only if useful for recap or trap correction - Do NOT force 3M/5M questions unless the actual PYQ pool contains such patterns. - Do NOT force programming or HOTS homework unless the actual PYQ pool supports it. - Every homework question must map to one concept/trap from Sections 3, 4, or 7. - Homework questions should be self-generated, not copied actual PYQs. 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>.]

10. Exam Tips

[5 specific tips as .tip-box — derived from examiner traps for THIS topic only — written as plain tips, no PYQ wording]

11. Last-Minute Revision Cards

<div class="card-grid"> [One .card per concept: <div class="card-title">[concept]</div> + 1 rule + 1 example] </div>