Thursday, 09 April 2026

PYQ references used by both prompts 7 included

Flagged questions are excluded from both Study Notes and PPT references until corrected in Paper Analyzer.

Included ID 6500 · 2021 · 1 mark(s)

Identify the output of the following Python statements.
x = 2
while x < 9:
    print(x, end='')
    x = x + 1
a) 12345678
b) 123456789
c) 2345678
d) 23456789

Revision of Python & Core Concepts → Control flow and loops

Included ID 6501 · 2021 · 1 mark(s)

Identify the output of the following Python statements.
b = 1
for a in range(1, 10, 2):
    b += a + 2
print(b)
a) 31
b) 33
c) 36
d) 39

Revision of Python & Core Concepts → Control flow and loops

Included ID 6569 · 2023 · 1 mark(s)

State True or False:
"In a Python program, if a break statement is given in a nested loop, it terminates the execution of all loops in one go."

Revision of Python & Core Concepts → Control flow and loops

Included ID 6149 · 2024 · 2 mark(s)

Differentiate between Break and Continue statements in Python.

Revision of Python & Core Concepts → Control flow and loops

Included ID 6666 · 2025 · 1 mark(s)

Write the output of the following Python code:
for k in range(7,40,6):
    print ( k + '-' )

Revision of Python & Core Concepts → Control flow and loops

Included ID 6683 · 2025 · 2 mark(s)

B. Explain the difference between break and continue statements in Python with a suitable example.

Revision of Python & Core Concepts → Control flow and loops

Included ID 6210 · 2025 · 5 mark(s)

Write the Python code for the following output (pattern):
0
12
345
6789

Revision of Python & Core Concepts → Control flow and loops

.txt

You are an expert CBSE XII CS Computer Science teacher, examiner, and study material creator.

===========================================
SCOPE — READ BEFORE GENERATING ANYTHING
===========================================
Today's lecture covers ONE topic only: "Control flow and loops"
Lecture number 7 of 91 | Duration: 35 minutes | Board: CBSE
Chapter: Computational Thinking and Programming – 2

HARD RULE: Every piece of content you generate — notes, examples, questions, tips —
must be directly relevant to "Control flow and loops" only.
DO NOT pull content, examples, or questions from any other topic or chapter.

LECTURE MODE: SUBTOPIC PYQ PRACTICE
- Scope: "Control flow and loops" only.
- Do not reteach the topic from scratch. Use a short recap only when a PYQ needs it.
- Main output must be previous-year-question practice: question analysis, marking points, model answers, common mistakes, and timed strategy.
- Use the 7 real PYQ record(s) provided below as the source of truth. Do not fabricate board years, marks, or questions.

===========================================
SECTION 1: LECTURE INFORMATION
===========================================

Class: XII CS | Subject: Computer Science | Board: CBSE
Topic: Control flow and loops PYQ
Subtopics to cover today:
- Control flow and loops

Student level: Class XII, CBSE Board, average to above-average students preparing for board exams

===========================================
SECTION 2: TEACHER'S REFERENCE NOTES
===========================================

Control flow and loops PYQ

PYQ PRACTICE SCOPE: Control flow and loops.
Concept ID: U1_CONTROL_FLOW_LOOPS.
Use only previous-year questions whose concept_ids include U1_CONTROL_FLOW_LOOPS.

Teaching ideas: Timed PYQ round, board solution, peer marking, and correction of recurring examiner traps.

===========================================
SECTION 3: EXAM FREQUENCY DATA (Year-wise)
===========================================

Teaching priority: HIGH
High-yield concepts: Control flow and loops

| Year | Questions | Marks |
|------|-----------|-------|
| 2021 | 2 | 2 |
| 2023 | 1 | 1 |
| 2024 | 1 | 2 |
| 2025 | 3 | 8 |
| **Total** | **7** | **13** |

===========================================
SECTION 4: ACTUAL PREVIOUS YEAR QUESTIONS
(Scope: "Control flow and loops" only — 7 questions from board papers)
===========================================

PYQ LECTURE RULE: use these questions as the source pool for practice.
- This pool has 7 questions: preserve and discuss ALL 7 actual PYQs in Section 7.
- Do not compress, replace, paraphrase, or skip any actual PYQ.
- Do not create substitute or newly framed questions for this small pool.
- Do not fabricate board years, marks, sections, or questions.


--- 2021 Board Exam (2 questions | 2 marks) ---

Q1. [MCQ] [1M] [Easy] Section-B
Identify the output of the following Python statements.
x = 2
while x < 9:
    print(x, end='')
    x = x + 1
a) 12345678
b) 123456789
c) 2345678
d) 23456789

Q2. [MCQ] [1M] [Easy] Section-B
Identify the output of the following Python statements.
b = 1
for a in range(1, 10, 2):
    b += a + 2
print(b)
a) 31
b) 33
c) 36
d) 39

--- 2023 Board Exam (1 question | 1 marks) ---

Q1. [Short Answer] [1M] [Easy] Section-A
State True or False:
"In a Python program, if a break statement is given in a nested loop, it terminates the execution of all loops in one go."

--- 2024 Board Exam (1 question | 2 marks) ---

Q1. [Short Answer] [2M] [Easy] Section-B
Differentiate between Break and Continue statements in Python.

--- 2025 Board Exam (3 questions | 8 marks) ---

Q1. [Output Prediction] [1M] [Easy] Section-A
Write the output of the following Python code:
for k in range(7,40,6):
    print ( k + '-' )

Q2. [Short Answer] [2M] [Easy] Section-B
B. Explain the difference between break and continue statements in Python with a suitable example.

Q3. [Short Answer] [5M] [Hard] Section-D
Write the Python code for the following output (pattern):
0
12
345
6789

===========================================
===========================================
QUESTION PATTERN BANK (What the board actually asks for THIS topic)
===========================================
Scope: ONLY questions for today's lecture topic are listed below.
DO NOT import questions from other topics or chapters.
These are concept-pattern summaries (what TYPE the board asks), not copies of the
actual questions — never reproduce full question text here.

### Concept: Control flow and loops
  Pattern: MCQ=2, Output Prediction=1, Short Answer=4 | Marks: 1M=4, 2M=2, 5M=1 | Total: 7 questions
  [MCQ] [1M] [Easy] × 2
    → Output/result interpretation for the current concept
  [Short Answer] [1M] [Easy]
    → True/False: nested try/except behaviour
  [Short Answer] [2M] [Easy] × 2
    → Core concept of Control flow and loops
  [Output Prediction] [1M] [Easy]
    → Output/result interpretation for the current concept
  [Short Answer] [5M] [Hard]
    → Output/result interpretation for the current concept


===========================================
===========================================
IMPORTANCE ANALYSIS (allocate teaching time by this ranking)
===========================================
| Rank | Concept | Score | Times Tested | Total Marks | Recent Years | Priority |
|------|---------|-------|-------------|-------------|--------------|----------|
| 1 | Control flow and loops | 42 | 7 | 13M | 2025, 2024, 2023 | CRITICAL |

CRITICAL concepts → full sub-section + comparison table + 2 worked examples
HIGH concepts     → 1 sub-section + 1 worked example
MEDIUM concepts   → definition + 1 quick example only

===========================================
EXAMINER FINGERPRINT — TRAPS TO COVER INTERNALLY
===========================================

Use the exam-frequency input and actual previous-year questions to identify traps, marking points, and common mistakes. In this PYQ Practice lecture, actual PYQs may be printed in Section 7 only. Do not print them randomly in concept notes, homework, or unrelated sections.

For this lecture, the generated teaching material must strongly cover these traps:

No static trap list exists yet for "Control flow and loops". Self-generate 4–7 traps from:
- actual question patterns for Control flow and loops
- common wrong assumptions students make about this concept
- output-tracing traps
- syntax-vs-runtime traps
- comparison traps
- order/sequence traps

Important: this list should be treated as dynamic — for lectures with no static trap list, generate traps yourself from the categories above rather than leaving this section thin.
===========================================
YOUR TASK — Generate a complete classroom-ready teaching package
===========================================

Output format: FULL HTML (print-ready, A4, same format as CBSE study material).
Use the CSS classes below. NO plain Markdown — use HTML elements only.

HTML STRUCTURE TO GENERATE:

<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width,initial-scale=1">
<title>Control flow and loops PYQ — Lecture 7</title>
<style>
/* ── PRINT SETUP ── */
@page { size: A4; margin: 12mm 14mm 12mm 14mm; }
* { box-sizing: border-box; }

/* ── BASE ── */
body { font-family: 'Segoe UI', Arial, sans-serif; font-size: 9.5pt; color: #1a1a2e; line-height: 1.4; background: #fff; margin: 0; padding: 0; }

/* ── HEADINGS ── */
h1 { font-size: 17pt; text-align: center; color: #16213e; border-bottom: 3px solid #e94560; padding-bottom: 5px; margin: 0 0 8px; }
h2 { font-size: 12pt; color: #0f3460; background: linear-gradient(90deg,#e8f4f8,#fff); padding: 5px 10px; margin: 14px 0 6px; border-left: 5px solid #e94560; }
h3 { font-size: 10.5pt; color: #16213e; border-bottom: 1.5px dashed #ccc; padding-bottom: 3px; margin: 10px 0 4px; }

/* ── CONTENT BOXES ── */
.def-box { background:#e3f2fd; border-left:3px solid #1976d2; padding:4px 8px; margin:4px 0; font-size:9pt; border-radius:0 4px 4px 0; }
.key-box { background:#fff8e1; border-left:3px solid #f9a825; padding:4px 8px; margin:4px 0; font-size:9pt; border-radius:0 4px 4px 0; }
.key-box ul { margin:3px 0 0 12px; padding:0; }
.key-box li { margin:2px 0; }
.example-box { background:#f3e5f5; border-left:3px solid #7b1fa2; padding:4px 8px; margin:4px 0; font-size:9pt; border-radius:0 4px 4px 0; }
.warn-box { background:#ffebee; border-left:3px solid #c62828; padding:4px 8px; margin:4px 0; font-size:9pt; border-radius:0 4px 4px 0; }
.warn-box::before { content: "⚠ EXAMINER TRAP: "; font-weight:bold; color:#e65100; }
.tip-box { background:#e8f5e9; border-left:3px solid #2e7d32; padding:4px 8px; margin:4px 0; font-size:9pt; border-radius:0 4px 4px 0; }
.recall-box { background:#e8f5e9; border-left:3px solid #2e7d32; padding:4px 8px; margin:4px 0; font-size:9pt; font-weight:bold; border-radius:0 4px 4px 0; }
.pyq-box { background:#fff3e0; border:1px solid #ffe0b2; padding:6px 10px; margin:6px 0; border-radius:6px; font-size:9pt; }
.pyq-box .pyq-meta { font-size:7.5pt; color:#e65100; font-weight:bold; margin-bottom:3px; }
.mcq-box { background:#f8f9fa; border:1px solid #dee2e6; padding:6px 10px; margin:5px 0; border-radius:4px; font-size:9pt; }
.options { list-style:none; margin:4px 0 0 0; padding:0; }
.options li { padding:2px 0; }
.options li.wrong { color:#c62828; }
.options li.correct { color:#2e7d32; font-weight:bold; }
.options .why { font-size:8pt; color:#555; margin-left:8px; font-style:italic; }
.self-test-box { background:#e8eaf6; border:1px dashed #5c6bc0; padding:6px 10px; margin:6px 0; border-radius:4px; font-size:9pt; }
details summary {
  cursor:pointer; display:inline-block; margin-top:6px; padding:2px 10px;
  background:#e8eaf6; color:#3949ab; border:1px solid #9fa8da;
  border-radius:4px; font-size:8.5pt; font-weight:600; user-select:none;
  list-style:none;
}
details summary::-webkit-details-marker { display:none; }
details[open] > summary { background:#c5cae9; }
details > *:not(summary) { margin-top:6px; }

/* ── CODE ── */
pre {
  background:#f8f9fa;
  color:#212529;
  border:1px solid #dee2e6;
  border-radius:4px;
  margin:4px 0;
  padding:8px 10px;
  font-size:8.5pt;
  line-height:1.5;
  white-space:pre-wrap;
  word-break:break-word;
}
pre code {
  white-space:pre;
  word-break:normal;
  display:block;
  overflow-x:auto;
  font-size:inherit;
}
code {
  font-family:'Courier New', monospace;
  font-size:0.95em;
}
.kw { color:#0000ff; } .bi { color:#267f99; } .st { color:#a31515; }
.cm { color:#008000; } .nm { color:#098658; } .fn { color:#795e26; }
.va { color:#001080; }

/* ── TABLES ── */
table { border-collapse:collapse; width:100%; margin:5px 0; font-size:8.5pt; }
th, td { border:1px solid #bbb; padding:3px 6px; text-align:left; }
th { background:#eeeeee; font-weight:bold; color:#333; }
tr:nth-child(even) { background:#fafafa; }
.highlight-row { background:#fff9c4 !important; font-weight:bold; }

/* ── CARDS ── */
.card-grid { display:grid; grid-template-columns:repeat(auto-fit,minmax(200px,1fr)); gap:6px; margin:8px 0; }
.card { background:#fff; border:1px solid #ccc; border-radius:4px; padding:6px 8px; font-size:8.5pt; }
.card .card-title { font-weight:bold; font-size:9pt; color:#0f3460; margin-bottom:3px; border-bottom:1px solid #eee; padding-bottom:2px; }

/* ── PRIORITY TAGS ── */
.priority-tag { font-size:7.5pt; padding:1px 6px; border-radius:10px; font-weight:bold; white-space:nowrap; }
.critical { background:#fce4ec; color:#ad1457; }
.high { background:#fff3e0; color:#e65100; }
.medium { background:#fff8e1; color:#f57f17; }
.marks-badge { display:inline-block; background:#e94560; color:#fff; font-size:7.5pt; padding:1px 5px; border-radius:10px; font-weight:bold; margin-left:5px; }

/* ── TOC STICKY SIDEBAR (screen only) ── */
@media screen {
  body { display:grid; grid-template-columns:165px 1fr; gap:0; }
  .toc-sidebar { position:sticky; top:0; height:100vh; overflow-y:auto; background:#f8f9fa; padding:10px 6px; font-size:8pt; color:#333; border-right:1px solid #ddd; }
  .toc-sidebar h4 { font-size:8.5pt; color:#16213e; margin:0 0 8px; padding-bottom:4px; border-bottom:1px solid #ddd; }
  .toc-sidebar a { display:block; color:#0f3460; text-decoration:none; padding:2px 4px; border-radius:3px; margin-bottom:1px; }
  .toc-sidebar a:hover { background:#e8f4f8; }
  .toc-sidebar .toc-h3 { padding-left:10px; font-size:7.5pt; color:#555; }
  .main-content { padding:10px 14px; min-width:0; }
}
@media screen and (max-width:640px) {
  body { grid-template-columns:1fr; }
  .toc-sidebar { display:none; }
  .main-content { grid-column:1 / -1; padding:8px; }
}
@media print {
  .toc-sidebar { display:none; }
  .main-content { grid-column:1 / -1; padding:0; }
  body { display:block; }
  .print-bar { display:none; }
  .collapse-btn { display:none !important; }
  .section-body { display:block !important; }
  /* Force all <details> open and hide the toggle-button summary text */
  details { display:block !important; }
  details > *:not(summary) { display:block !important; visibility:visible !important; }
  details > summary { display:none !important; }
}

/* ── PRINT BUTTONS ── */
.print-bar { position:fixed; top:8px; right:8px; display:flex; gap:6px; z-index:999; }
.print-btn { padding:5px 14px; color:#fff; border:none; border-radius:4px; cursor:pointer; font-size:9pt; box-shadow:0 2px 6px rgba(0,0,0,0.3); }
.print-btn.color-btn { background:#e94560; }
.print-btn.bw-btn { background:#333; }
.print-btn.back-btn { background:#1976d2; display:none; }
.print-btn.read-btn { background:#2e7d32; }

/* ── READ MODE ── */
@media screen {
  body.read-mode .print-bar { display:none !important; }
  body.read-mode .toc-sidebar { display:none !important; }
  body.read-mode .main-content {
    grid-column:1 / -1; max-width:860px; margin:0 auto;
    padding:24px 32px; font-size:11pt; line-height:1.75;
  }
}
#btnExitRead {
  display:none; position:fixed; bottom:16px; right:16px;
  background:rgba(0,0,0,0.55); color:#fff; border:none; border-radius:20px;
  padding:6px 14px; font-size:9pt; cursor:pointer; z-index:9999;
}
body.read-mode #btnExitRead { display:block; }
@media print { #btnExitRead { display:none !important; } }

/* ── B&W MODE OVERRIDES ── */
body.bw-mode { background:#fff !important; color:#000 !important; }
body.bw-mode .def-box, body.bw-mode .key-box, body.bw-mode .example-box,
body.bw-mode .warn-box, body.bw-mode .tip-box, body.bw-mode .recall-box,
body.bw-mode .pyq-box, body.bw-mode .mcq-box, body.bw-mode .self-test-box {
  background:#fff !important; border:1px solid #ccc !important; border-left:none !important;
}
body.bw-mode h1 { color:#000 !important; border-bottom:2px solid #000 !important; }
body.bw-mode h2 { background:#fff !important; border-left:2px solid #000 !important; color:#000 !important; }
body.bw-mode h3 { color:#000 !important; border-bottom:1px solid #000 !important; }
body.bw-mode pre { background:#fff !important; color:#000 !important; border:1px solid #ccc !important; }
body.bw-mode .kw, body.bw-mode .bi, body.bw-mode .st, body.bw-mode .cm,
body.bw-mode .nm, body.bw-mode .fn, body.bw-mode .va { color:#000 !important; }
body.bw-mode table th { background:#eee !important; color:#000 !important; }
body.bw-mode tr:nth-child(even) { background:#fff !important; }
body.bw-mode .priority-tag, body.bw-mode .marks-badge { background:#fff !important; color:#000 !important; border:1px solid #000 !important; }
body.bw-mode .card { background:#fff !important; border:1px solid #ccc !important; }
body.bw-mode .highlight-row { background:#fff !important; }
body.bw-mode .toc-sidebar { background:#fff !important; border-right:1px solid #ccc !important; }
body.bw-mode .toc-sidebar a { color:#000 !important; }

/* ── COLLAPSIBLE SECTIONS ── */
.collapse-btn { float:right; background:none; border:none; cursor:pointer; font-size:10pt; color:#aaa; padding:0 4px; margin-left:6px; }
.collapse-btn:hover { color:#e94560; }
</style>
</head>
<body>

<!-- Print / mode buttons (hidden on print) -->
<div class="print-bar">
  <button class="print-btn read-btn"   id="btnReadMode" onclick="toggleReadMode()">&#128214; Read Mode</button>
  <button class="print-btn back-btn"   id="btnBackColor" onclick="backToColor()">&#127775; Back to Color</button>
  <button class="print-btn bw-btn"     id="btnPrintBW"   onclick="printBW()">&#128438; Print B&amp;W</button>
  <button class="print-btn color-btn"                    onclick="printColor()">&#128438; Print Color</button>
</div>
<button id="btnExitRead" onclick="toggleReadMode()">&#10005; Exit Read Mode</button>

<!-- JS: print modes + collapsible sections + TOC auto-build -->
<script>
function printColor() {
  document.body.classList.remove('bw-mode');
  document.getElementById('btnPrintBW').style.display='inline-block';
  document.getElementById('btnBackColor').style.display='none';
  window.print();
}
function printBW() {
  document.body.classList.add('bw-mode');
  document.getElementById('btnPrintBW').style.display='none';
  document.getElementById('btnBackColor').style.display='inline-block';
  window.print();
}
function backToColor() {
  document.body.classList.remove('bw-mode');
  document.getElementById('btnPrintBW').style.display='inline-block';
  document.getElementById('btnBackColor').style.display='none';
}
function toggleReadMode() {
  document.body.classList.toggle('read-mode');
}

// Auto-collapsible h2/h3 sections
(function(){
  function setup(){
    document.querySelectorAll('.main-content h2,.main-content h3').forEach(function(h){
      var btn=document.createElement('button');
      btn.className='collapse-btn';btn.textContent='▼';
      h.appendChild(btn);
      var wrapper=document.createElement('div');wrapper.className='section-body';
      var level=parseInt(h.tagName[1]),next=h.nextElementSibling;
      while(next){
        var tag=next.tagName||'';
        if(/^H[1-6]$/.test(tag)&&parseInt(tag[1])<=level)break;
        var after=next.nextElementSibling;wrapper.appendChild(next);next=after;
      }
      h.insertAdjacentElement('afterend',wrapper);
      btn.addEventListener('click',function(e){
        e.stopPropagation();
        var open=wrapper.style.display!=='none';
        wrapper.style.display=open?'none':'';
        btn.textContent=open?'▶':'▼';
      });
    });
    // Expand/Collapse All in TOC
    var toc=document.querySelector('.toc-sidebar');
    if(toc){
      var bar=document.createElement('div');
      bar.style.cssText='display:flex;gap:4px;margin-bottom:8px;';
      ['Expand All','Collapse All'].forEach(function(label){
        var b=document.createElement('button');
        b.textContent=label;
        b.style.cssText='flex:1;font-size:7.5pt;padding:2px 4px;border:1px solid #ccc;border-radius:3px;cursor:pointer;background:#fff;';
        b.addEventListener('click',function(){
          var expand=label==='Expand All';
          document.querySelectorAll('.section-body').forEach(function(w){w.style.display=expand?'':'none';});
          document.querySelectorAll('.collapse-btn').forEach(function(b){b.textContent=expand?'▼':'▶';});
        });
        bar.appendChild(b);
      });
      toc.insertBefore(bar,toc.firstChild);
    }
    // Auto-build TOC links from h2/h3 IDs
    if(toc){
      document.querySelectorAll('.main-content h2,.main-content h3').forEach(function(h){
        if(!h.id){h.id=h.textContent.trim().replace(/[^a-z0-9]+/gi,'-').toLowerCase().slice(0,40);}
        var a=document.createElement('a');
        a.href='#'+h.id;
        a.textContent=h.textContent.replace('▼','').replace('▶','').trim();
        if(h.tagName==='H3')a.classList.add('toc-h3');
        toc.appendChild(a);
      });
    }
  }
  if(document.readyState==='loading'){document.addEventListener('DOMContentLoaded',setup);}else{setup();}
})();

// Auto-open details when printing
(function(){
  function openDetails(){
    document.querySelectorAll('details').forEach(function(d){
      if(!d.hasAttribute('open')){d.setAttribute('data-was-closed','');d.setAttribute('open','');}
    });
    document.querySelectorAll('.section-body').forEach(function(w){
      if(w.style.display==='none'){w.setAttribute('data-was-hidden','');w.style.display='';}
    });
  }
  function restoreDetails(){
    document.querySelectorAll('[data-was-closed]').forEach(function(d){d.removeAttribute('open');d.removeAttribute('data-was-closed');});
    document.querySelectorAll('[data-was-hidden]').forEach(function(w){w.style.display='none';w.removeAttribute('data-was-hidden');});
  }
  window.addEventListener('beforeprint',openDetails);
  window.addEventListener('afterprint',restoreDetails);
})();
</script>

<!-- TOC SIDEBAR -->
<nav class="toc-sidebar" aria-label="Table of Contents">
  <h4>&#128214; Contents</h4>
  <!-- TOC links auto-built by JS above -->
</nav>

<!-- MAIN CONTENT -->
<div class="main-content">

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

<h1 id="top">Control flow and loops PYQ — Lecture 7</h1>
<p style="text-align:center;color:#555;font-size:8.5pt;">CBSE | XII CS | Computational Thinking and Programming – 2 | 35 min</p>

<h2 id="s1">1. Learning Objectives</h2>
[3–5 objectives derived from what the PYQs above test — use &lt;ul&gt;&lt;li&gt;]

<h2 id="s2">2. 35-Minute Lecture Flow</h2>
[HTML table: Time | Activity | Teacher Action — include a PYQ discussion and full-coverage slot]

<h2 id="s3">3. Quick Concept Recap</h2>
[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: Control flow and loops).
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.]

<h2 id="s4">4. Examiner Tricks &amp; Common Mistakes</h2>
[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]

<h2 id="s5">5. Board Work Plan</h2>
[Numbered list: exactly what to write on the blackboard, in order]

<h2 id="s6">6. Classroom Practice Questions</h2>
[Modelled on PYQ style. CRITICAL: every answer MUST be inside &lt;details&gt;&lt;summary&gt;▶ View Answer&lt;/summary&gt;...&lt;/details&gt; — 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 &lt;details&gt;&lt;summary&gt;▶ View Answer&lt;/summary&gt;...&lt;/details&gt;.

MCQ structure:
&lt;div class="mcq-box"&gt;
  &lt;b&gt;Q1.&lt;/b&gt; Question text?&lt;br&gt;
  &lt;ul class="options"&gt;
    &lt;li&gt;a) ...&lt;/li&gt;
    &lt;li&gt;b) ...&lt;/li&gt;
    &lt;li&gt;c) ...&lt;/li&gt;
    &lt;li&gt;d) ...&lt;/li&gt;
  &lt;/ul&gt;
  &lt;details&gt;&lt;summary&gt;▶ View Answer&lt;/summary&gt;
    &lt;ul class="options"&gt;
      &lt;li class="wrong"&gt;a) ... — reason why wrong&lt;/li&gt;
      &lt;li class="correct"&gt;b) ... ✓ — reason why correct&lt;/li&gt;
      ...
    &lt;/ul&gt;
  &lt;/details&gt;
&lt;/div&gt;
(Note: options list shown WITHOUT .correct/.wrong BEFORE the details; INSIDE details show all options with correct/wrong analysis.)

Short-answer structure:
&lt;div class="self-test-box"&gt;&lt;b&gt;Q4.&lt;/b&gt; Question&lt;br&gt;&lt;details&gt;&lt;summary&gt;▶ View Answer&lt;/summary&gt;Full answer&lt;/details&gt;&lt;/div&gt;

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.]

<h2 id="s7">7. PYQ Discussion / Full Coverage (7 source questions)</h2>
[This source pool has 7 actual PYQs.
PYQ COVERAGE RULE:
  - This pool has 7 PYQs, so include and discuss ALL 7 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 &lt;details&gt; · common mistake inside &lt;details&gt;
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:
  &lt;div class="pyq-box"&gt;
    &lt;div class="pyq-meta"&gt;[YEAR] · [X] Marks · [TYPE] · Section-[S]&lt;/div&gt;
    &lt;b&gt;Q.&lt;/b&gt; [full question text — include code if any]&lt;br&gt;&lt;br&gt;
    &lt;b&gt;Concept tested:&lt;/b&gt; [concept name]&lt;br&gt;
    &lt;details&gt;&lt;summary&gt;▶ View Model Answer&lt;/summary&gt;
      &lt;b&gt;Model Answer:&lt;/b&gt; [full answer with code/table as needed, using .kw/.bi/.st token spans in &lt;pre&gt;&lt;code&gt;]&lt;br&gt;
      &lt;b&gt;Common mistake:&lt;/b&gt; [what students get wrong — be specific]
    &lt;/details&gt;
  &lt;/div&gt;
]

<h2 id="s8">8. Student Notes (Copy-ready)</h2>
[Concise notes — every concept from PYQs — in .key-box and .def-box; self-check questions in .self-test-box with &lt;details&gt;&lt;summary&gt;▶ View Answer&lt;/summary&gt;answer&lt;/details&gt;]

<h2 id="s9">9. Homework</h2>
[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 &lt;details&gt;&lt;summary&gt;▶ View Answer&lt;/summary&gt;...&lt;/details&gt; inside .self-test-box or .mcq-box.]

<h2 id="s10">10. Exam Tips</h2>
[5 specific tips as .tip-box — derived from PYQ patterns for THIS topic only]

<h2 id="s11">11. Last-Minute Revision Cards</h2>
&lt;div class="card-grid"&gt;
[One .card per concept: &lt;div class="card-title"&gt;[concept]&lt;/div&gt; + 1 rule + 1 example]
&lt;/div&gt;

</div><!-- end .main-content -->
</body>
</html>

HARD OUTPUT RULES:
- Output ONLY the HTML document starting with &lt;!DOCTYPE html&gt;
- Do NOT wrap in markdown code fences
- Do NOT add explanatory text outside the HTML
- Use ONLY content from "Control flow and loops" — zero content from other topics
- PYQ lecture: include and discuss ALL 7 actual PYQs in Section 7; do not compress, replace, paraphrase, or skip any source question
- Always finish the document completely through &lt;/html&gt;. If the answer is getting long, keep Sections 3 and 7 complete, then compact Sections 8–11 instead of truncating.
- If 15 or fewer PYQs are provided, include ALL actual PYQs in Section 7.
- If more than 15 PYQs are provided, fully discuss the highest-yield 15 and list the rest compactly in Section 7 with concept tested + exam trap.
- ANSWER HIDING (most important for student use):
    * Section 6 MCQs: options listed WITHOUT .correct/.wrong BEFORE details; full analysis only INSIDE &lt;details&gt;
    * Section 6 short/programming/HOTS questions: EVERY answer in &lt;details&gt;&lt;summary&gt;▶ View Answer&lt;/summary&gt;...&lt;/details&gt;
    * Section 8 self-check and Section 9 homework: EVERY answer in &lt;details&gt;&lt;summary&gt;▶ View Answer&lt;/summary&gt;
    * Section 7 PYQ Discussion / Full Coverage: model answer + common mistake inside &lt;details&gt;&lt;summary&gt;▶ View Model Answer&lt;/summary&gt;
    * .pyq-box question text and concept tested stay visible outside &lt;details&gt;; only Model Answer + Common mistake are hidden inside &lt;details&gt;
    * The beforeprint JS already auto-opens all &lt;details&gt; for printing — never skip this feature
- INLINE CODE SIZE RULE:
    * Inline code (function/method names and short snippets relevant to "Control flow and loops") must appear almost the same size as surrounding normal text.
    * Do NOT use fixed 8.5pt size for all &lt;code&gt; elements.
    * Use code { font-size:0.95em; } for inline code.
    * Use pre { font-size:8.5pt; } for block code.
    * Use pre code { font-size:inherit; } so code blocks remain compact.
    * Inline code inside paragraphs, tables, boxes, tips, questions, and answers must not look smaller than nearby text.
- BOX / CLASS USAGE: this is a PYQ lecture, so .pyq-box/.pyq-meta are used as shown in Section 7 above (never in theory lectures).
- All content goes inside &lt;div class="main-content"&gt;
- The &lt;nav class="toc-sidebar"&gt; is already in the template — JS auto-builds TOC links
- Print buttons (.print-bar), including Read Mode, are in the template — DO NOT add them again; they auto-hide on print
- Include the full CSS and JS exactly as given (the CODE CSS already follows the INLINE CODE SIZE RULE above).

# ENHANCED PPT GENERATION PROMPT
## Topic: Control flow and loops PYQ | CBSE XII CS Computer Science

================================================
SECTION A -- VISUAL IDENTITY (READ FIRST, APPLY TO EVERY SLIDE)
================================================

COLOUR PALETTE -- "Deep Code" Theme
  Role              Hex        Name             Where Used
  Primary (dark)    #0D1B2A    Midnight Navy    Title bg, conclusion bg
  Secondary         #1B4F72    Ocean Blue       Section header cards, accent shapes
  Accent            #00D4FF    Cyan Electric    Keywords, callout borders, badges
  Neutral light     #F0F4F8    Ice White        All content slide backgrounds
  Warning/Error     #E74C3C    Alert Red        Common mistakes slide, warnings
  Success/Tip       #27AE60    Emerald Green    Tips, correct syntax, exam tips
  Text primary      #1A1A2E    Near Black       Body text on light slides
  Text on dark      #FFFFFF    Pure White       All text on dark background slides
  Text muted (dark) #C9D4E0    Slate Mist       Sub-lines / captions on navy slides

ON-LIGHT VARIANTS (use for ANY text, keyword, icon, or thin border on Ice White):
  Cyan  -> Accent-Deep  #0077A3      Emerald -> #1E8449      Red -> #C0392B
CONTRAST RULE: bright Cyan #00D4FF / Emerald #27AE60 / Red #E74C3C are for DARK
backgrounds or thick (>=4 pt) shape fills ONLY -- never for thin text, borders, or
badges on a light slide (bright cyan on Ice White is ~1.6:1 contrast = invisible
from the back row). On light slides always use the deep variants above.

COLOUR DISCIPLINE -- 60 / 30 / 10 (this is what separates "designed" from "filled-in")
  * 60% of every content slide is the Ice White background + generous EMPTY space.
    Empty space is a design element, not a slide you failed to fill.
  * 30% is ONE neutral structural element -- a single card, panel, or diagram.
  * 10% -- and NO MORE -- is the accent (Cyan Electric or one status colour). One
    accent MOMENT per slide: the focal chip, the keyword, the one arrow that
    matters. A slide where every box is coloured has NO accent -- it is noise.
  * Build depth with TINTS of one hue, never many saturated hues. A card fill is a
    6-8% tint of its header colour (pale-blue body under an Ocean Blue header),
    never a strong fill behind text. Status tints: blue 6% = definition,
    green 6% = correct/tip, red 6% = wrong/trap. Borders are 1 pt in the deep
    variant -- not thick coloured frames.
  * Navy dominates ONLY the Title and Key Takeaways slides. Never split a content
    slide 50/50 navy-vs-white -- it destroys hierarchy.

GRID & COMPOSITION (the missing rule that makes slides look intentional)
  * Lay every content slide on a 12-column grid inside the safe area with a
    consistent ~0.2 inch gutter. Snap every card, text block, icon and diagram
    edge to a column line -- never free-float objects at arbitrary x positions.
  * ONE alignment spine per slide: a single left text column (Left Icon+Text),
    two balanced 6-column halves (Two Column), or one centred focal object
    (Callout / Exam Spotlight). Do not mix three alignments on one slide.
  * Align tops and left edges across objects. Ragged, slightly-off edges are the
    #1 reason a slide reads as amateur even when nothing technically overlaps.

VISUAL HIERARCHY -- ONE FOCAL POINT PER SLIDE
  * Every slide answers "what is the ONE thing the eye lands on first?" Make that
    element the largest / boldest / the only accent-coloured object; everything
    else is visibly secondary (smaller, neutral, lighter).
  * Hierarchy comes from SCALE CONTRAST and SPACE, not from boxing everything. A
    big number, one code line, or a single diagram surrounded by white beats
    three equal-weight bordered boxes every time.
  * Reserve bold + accent colour for the focal point ONLY. If three things are
    bold and coloured, nothing is emphasised.

INFORMATION-CARRYING VISUALS (the default -- not decorative chrome)
  * The visual must MEAN something: it carries the concept, it is not an ornament
    around text. Prefer, in order: a labelled code-breakdown (one code line on a
    dark card with arrows naming each part's role), a before/after, a flow
    (input -> process -> output), a comparison table, a decision tree.
  * A rounded box with a clip-art icon beside a bullet is chrome -- it explains
    nothing and should be cut. One strong visual that teaches the idea beats four
    small decorative ones.
  * Icons: line-style, ONE consistent family, used to label SECTIONS only -- not
    one circle per bullet. An icon on every line is clutter, not design.

TYPOGRAPHY -- CLASSROOM-OPTIMISED (NON-NEGOTIABLE)
  Element             Font              Size   Weight    Notes
  Slide title         Montserrat        44 pt  Bold      Visible from back row (Arial Bold if Montserrat unavailable)
  Focal number/word   Montserrat        60+ pt Bold      The one hero element may go large for scale contrast
  Section header      Arial             32 pt  Bold      Sub-headings inside slides
  Body bullets        Calibri           28 pt  Regular   MAX 3 bullets -- min 28 pt
  Code text           Courier New       24 pt  Regular   On dark card only
  Captions/labels     Calibri           24 pt  Italic    Footer only; keep non-essential and brief

  NEVER go below 24 pt for ANY visible text.
  NEVER use Aptos, Thin fonts, or Calibri Light.
  Line spacing 1.15+. Title case for titles; sentence case for body.

VISUAL MOTIF -- "Bracket Accent" (restrained signature, not the main visual)
  * Small { } mark (Cyan Electric on dark / Accent-Deep #0077A3 on light) sits
    quietly top-left of the title -- a signature, never a slide's main visual.
  * Definitions: a single rounded callout with a 4 pt Cyan-Electric LEFT border
    only (no full frame). Code: dark #0D1B2A card, #00D4FF keywords, white rest.

DESIGN NEVER-DO LIST
  NO accent lines below titles
  NO colour bars or stripes spanning full slide width
  NO vertical sidebar stripes
  NO cream/beige backgrounds
  NO saturated colour fills behind body text (use 6-8% tints instead)
  NO icon-circle on every bullet, no clip-art decoration
  NO three competing focal points -- exactly one hero element per slide
  NO evenly-tiled grid of identical boxes whose only job is to fill the slide
  NO text-only slides -- every slide needs ONE information-carrying visual
  NO centred body text -- left-align all bullets
  NO more than 3 bullets per slide
  NO bullet longer than 10 words
  NO font below 24 pt

LAYOUT VARIETY -- ROTATE WHEN IT HELPS CLARITY
  Layout Name         When to Use
  Full-bleed Dark     Title slide, Key Takeaways slide
  Left Icon+Text      Theory slides -- icon circle left, bullets right
  Two Column          Comparisons (list vs tuple, == vs is, mutable vs immutable, etc.)
  Code Card           All code examples -- dark card on light background
  Callout Box         Definitions -- rounded rect, Cyan Electric border
  Exam Spotlight      PYQ slides -- large question centred on card
  3-Icon Grid         Key Takeaways -- 3 icons in equal columns
  Warning Banner      Common Mistakes -- red accent, alert icon

================================================
SECTION A1 -- LAYOUT SAFETY & OVERLAP PREVENTION
================================================

NON-NEGOTIABLE SAFE ZONE RULES:
  * Every slide must use a fixed 16:9 widescreen canvas.
  * Keep a minimum 0.35 inch margin from all slide edges.
  * No text box, badge, icon, card, or diagram may overlap another object.
  * Title area must be reserved separately from body area.
  * Body content must start only after the title area ends.

TITLE SAFE AREA:
  * Slide title box position: top 0.35 inch to 1.15 inch only.
  * No badge, icon, card, or body text may enter this title zone.
  * If title is long, wrap into maximum 2 lines.
  * Never allow title text to touch badges or cards.

BADGE PLACEMENT RULE:
  * Badges such as "Quick Recap", "PYQ", "1M", "60 seconds" must be placed
    in a fixed safe badge zone.
  * Badge zone: top-right corner, x >= 10.0 inch, y between 0.35 and 0.85 inch.
  * Badge must never be placed near the centre title area.
  * Badge text must stay inside the badge shape with 0.08 inch internal padding.

BODY SAFE AREA:
  * Body content must begin at y >= 1.45 inch on every content slide.
  * Large cards/callouts must begin at y >= 1.55 inch.
  * Bottom footer/caption area starts at y >= 6.85 inch.
  * Do not place main content in the footer zone.

TEXT FITTING RULE:
  * Do NOT shrink font below the required size.
  * If content does not fit, split into a continuation slide.
  * Use "(contd...)" in the title for continuation slides.
  * Never use PowerPoint auto-fit that reduces font size.
  * Never compress line spacing below 1.05.

OBJECT COLLISION CHECK -- before finalising each slide, verify:
  [ ] Title does not overlap badge.
  [ ] Badge does not overlap title or body.
  [ ] Body text does not overlap cards or icons.
  [ ] Code card has enough internal padding.
  [ ] No object is outside slide boundary.
  [ ] All text is fully visible after rendering.

RENDER QUALITY CHECK:
  After creating the PPT, render every slide as an image and inspect all
  rendered slides visually. If any slide has overlapping, clipped, hidden, or
  tiny text: fix the layout, split the slide if needed, render again, and only
  then provide the final PPT.

STRICT FAILURE RULE:
  A slide with overlapping text, clipped title, hidden badge, or unreadable
  content is considered FAILED and must be rebuilt before delivery.

================================================
SECTION B -- CONTENT SPECIFICATION
================================================

Topic     : Control flow and loops PYQ
Lecture   : #7 | Target duration: 35 min | Board: CBSE
Chapter   : Computational Thinking and Programming – 2
Class     : XII CS | Subject: Computer Science
Audience  : Class XII, CBSE Board, average to above-average students preparing for board exams

STRICT RULE: Every slide must be about "Control flow and loops PYQ" ONLY.

GENERATED STUDY NOTES HTML INPUT (OPTIONAL BUT PREFERRED):
  If the user provides/pastes the generated HTML study notes file for this lecture,
  treat that HTML as the AUTHORITATIVE PYQ practice source for the deck.
  Summarise all concepts into slide-friendly recap bullets, examples, diagrams,
  tables, and speaker notes without copying long HTML paragraphs verbatim.
  Quick Recap and exam-trap slides may be summarised from the HTML.
  PYQ Practice slides must follow Section F's PYQ Practice Question Rule.

DECK GOAL: This is a PRACTICE & APPLICATION session — students already
learned "Control flow and loops" in an earlier lecture. Do NOT re-teach the theory from
scratch and do NOT reproduce that lecture's theory/worked-example slides.
Open with ONE quick recap slide per subtopic (definition restated in one
line + one example, nothing more), then spend the MAJORITY of the deck on
INTENSIVE MIXED DRILLING: as many real previous-year questions as exist for
this topic, mixed difficulty, timed rounds, peer-marking, and a heavier
Common Mistakes / exam-strategy emphasis. Cover every concept the PYQ
pattern bank names — drop none to save slides.

SLIDE COUNT -- DETERMINE BY CONTENT, NOT A FIXED NUMBER:
  Do not compress or stretch the topic to hit a fixed slide count.
  For a single-concept PYQ Practice deck, typical deck size is 10-14 slides.
  For multi-concept PYQ Practice decks, typical deck size is 15-24 slides.
  The actual count depends on source PYQ count, unique traps, answer slides, and practice flow.
  Never stretch a small PYQ pool only to reach a large slide count.
  Never cram multiple PYQ answers into unreadable slides by shrinking fonts or overcrowding.
    * Every subtopic listed in Section D gets EXACTLY 1 recap slide — no
      worked-example or theory-elaboration slides; that already happened in
      the teaching lecture. The bulk of the deck is PYQ/mixed-practice slides.
    * CRITICAL/HIGH/MEDIUM priority (Section F) only changes drilling ORDER
      (critical concepts drilled first), not slide count — recap stays
      minimal regardless of priority.
    * CONTINUATION (encouraged — do NOT cram): when one concept needs more room
      than a single slide allows (more than 3 bullets, or theory + worked example
      + an exam trap), SPLIT it across consecutive slides. Title the overflow slide
      "<SAME TOPIC> (contd...)" and add a small "...continue ->" marker bottom-right
      of the first slide so the flow is obvious. Two clean slides always beat one
      crowded slide — never shrink the font or exceed 3 bullets just to make it fit.
  Fixed-position slides (always present, regardless of total count):
    Title, Agenda, Quick Recap        -- start of deck
    Common Mistakes                         -- immediately after content slides
    PYQ Practice block: use EXACTLY 7 actual PYQs from the source pool. First create 1-2 question-only slide(s); then create one answer/explanation slide per question. So this block normally contains 8-9 slides -- after Common Mistakes
    Key Takeaways, Exit Ticket              -- final two slides, in that order


RECAP CLARITY (the only "explain" rule that applies here):
  Students already learned this in an earlier lecture — the Quick Recap slide(s)
  only need to JOG memory, not re-teach from zero:
    * One line plain-English restatement ("In simple words: ...") + ONE tiny
      example — never a full derivation or multi-step explanation.
    * If the recap risks reviving a known confusion (e.g. == vs is, append vs extend, list vs tuple),
      a single Two Column reminder slide is fine — but do not expand it into a
      full theory lesson; that belongs in the original teaching lecture, not here.

================================================
SECTION C -- SLIDE OUTPUT FORMAT (USE EXACTLY)
================================================

+=======================================================+
SLIDE [n]: [SLIDE TITLE IN CAPS]
Layout     : [Full-bleed Dark / Left Icon+Text / Two Column /
              Code Card / Callout Box / Exam Spotlight /
              3-Icon Grid / Warning Banner]
Background : [#0D1B2A or #F0F4F8]
Title font : Montserrat Bold -- 44 pt on body slides / 54 pt on the Title slide
Body font  : Calibri 28 pt Regular
-------------------------------------------------------
VISUAL ELEMENT: [icon/shape/code card/diagram on this slide]

[Bullet 1 -- max 10 words]  (blue circle = definition)
[Bullet 2 -- max 10 words]  (green circle = tip)
[Bullet 3 -- max 10 words]  (red circle = warning)

CODE SLIDES -- paste inside dark card:
  +------------------------------------------+
  |  nums = [10, 20, 30]                      |
  |  print(nums[-1], len(nums))   # 30 3     |
  |  d = {"a": 1}; d["b"] = 2                 |
  |  print(d.get("a"), "b" in d)  # 1 True   |
  +------------------------------------------+
  OUTPUT: 30 3
          1 True

DIAGRAM SLIDES: describe shapes, arrows, labels, layout
-------------------------------------------------------
SPEAKER NOTES: [2-3 sentences for teacher -- NOT on slide.
Real-life analogy / Did You Know fact / exam tip / story.
EXCEPTION -- on Exit Ticket slides the notes carry the COMPLETE answer + explanation; PYQ Practice answer slides instead show the full solution + explanation + Critical Trap directly ON the slide (never in notes) (code may span many lines).]
+=======================================================+

================================================
SECTION D -- MANDATORY SLIDE SPECIFICATIONS
================================================

TITLE SLIDE (slide 1)
  Layout     : Full-bleed Dark (#0D1B2A background)
  Topic name : "Control flow and loops PYQ" -- 54 pt Bold Cyan Electric (#00D4FF)
  Sub-line 1 : "XII CS Computer Science" -- 32 pt White
  Sub-line 2 : "CBSE Board | Lecture 7" -- 24 pt Slate Mist (#C9D4E0)
  Motif      : semi-transparent { } bracket centred background (15% opacity)

AGENDA (slide 2)
  Layout     : Left Icon+Text
  One row per subtopic below: icon-circle + subtopic name + time estimate

QUICK RECAP (right after Agenda — see recap slide cap in Section B)
  Layout     : Callout Box centred
  ONE line definition restated + ONE tiny example — no elaboration, no
  "explain for understanding" multi-slide treatment (already taught earlier)
  Badge      : "Quick Recap" top-right
  LAYOUT EXEMPTION: consecutive Quick Recap slides MAY all use Callout Box —
  the "no two consecutive same layout" rule (Sections A & G) does NOT apply
  within the recap run. Distinguish them by accent colour / icon instead.

CONTENT SLIDES (as many as the SLIDE COUNT rules in Section B require)
  Subtopics to cover (allocate slide count by PYQ FOCUS priority in Section F):
  • Control flow and loops

  This is a PRACTICE deck: do NOT add theory/worked-example slides beyond the
  Quick Recap slides above. After the recap, go straight into MIXED PRACTICE —
  additional Exam Spotlight / Code Card slides drilling the actual PYQs from
  Section F only. Do not add extra exam-style questions unless the user explicitly
  requests more practice.

COMMON MISTAKES & EXAMINER TRAPS (right after all content slides)
  Layout     : Warning Banner
  Accent     : left thick border #E74C3C (4 pt) on each bullet card
  Title      : "DON'T MAKE THESE MISTAKES" -- 44 pt Bold Red
  EXACTLY 3 bullets -- specific PYQ traps with red alert icon

PYQ PRACTICE -- THIS IS A PYQ LECTURE: focus this block on PYQ only,
in two strict steps (7 questions total):

  STEP 1 -- QUESTION-ONLY SLIDE(S) (EXACTLY 1-2 slides, Exam Spotlight layout):
    Show ONLY question text (32 pt) + marks badge (Ocean Blue) + real year badge.
    This small pool uses every actual PYQ; do not create substitute or compressed questions.
    NO answer, NO explanation, NO trap anywhere on these slides.
    Batch multiple questions per slide (stacked Exam Spotlight cards) so this
    opening block stays at 1-2 slides regardless of the 7 total questions.
    Order      : Easy -> Medium -> Hard; within each difficulty, 1M -> 2M -> 3M -> higher
               (see PYQ PRACTICE QUESTION RULE in Section F)

  STEP 2 -- ANSWER SLIDES (one dedicated slide per question, SAME order as Step 1):
    Show ON THE SLIDE itself (never hidden in speaker notes):
      * The full model answer / worked solution
      * A one-line explanation of WHY (the reasoning, not just the final answer)
      * A "Critical Trap" callout (Warning Banner / Alert Red) -- the specific
        examiner trap or common mistake tied to THIS exact question
    Layout     : Exam Spotlight for short answers, Code Card for code-based answers
  Placement  : after Common Mistakes and before Key Takeaways

KEY TAKEAWAYS (second-to-last slide)
  Layout     : 3-Icon Grid (dark #0D1B2A background -- matches title)
  3 equal columns: large icon + 1-line heading (28 pt Bold) + 1-line summary (24 pt)
  EXACTLY 3 takeaways

EXIT TICKET (last slide)
  Layout     : Callout Box centred
  EXACTLY 1 MCQ or fill-in-the-blank -- question 32 pt, options 28 pt
  Timer badge: "60 seconds" top-right (Cyan Electric)
  ANSWER + EXPLANATION ONLY IN SPEAKER NOTES

================================================
SECTION E -- ENGAGEMENT RULES (MIN 2 IN SPEAKER NOTES)
================================================

1. Quick Recap slide: real-life analogy -- NOT textbook language
2. One slide: "Did You Know?" fun fact in speaker notes
3. One code slide: "Guess the Output?" -- ask class before revealing
4. Colour-coded bullets: red = warning, green = tip/example, blue = definition
5. Common Mistakes slide: one "Examiner Trap" with specific wrong answer students typically write

================================================
SECTION F -- PYQ FOCUS (WEIGHT SLIDES BY EXAM IMPORTANCE)
================================================

Board exam appearances: 7 times (2021-2025) | Total marks tested: 13M

DECK INTENT: build this as the POLISHED, EXAM-FOCUSED version of the study
notes — cover EVERY examiner-tested concept below (not just definitions),
and lead with the CRITICAL + CONFUSING concepts, giving them the most slide time.

TOP PRIORITY -- CRITICAL & CONFUSING CONCEPTS (open the content with these):
  ! Control flow and loops — asked as MCQ/Output Prediction/Short Answer; at 1,2,5M; 7x repeated --> own recap focus + PYQ drill priority; if it has a look-alike, use a Two-Column 'X vs Y' compare slide.

SUBTOPIC PRIORITY (allocate slide count by this ranking — see SLIDE COUNT rules in Section B):
  CRITICAL --> quick recap first, then highest-priority PYQ drill first
    * Control flow and loops — 7x in exams, 13M total (years: 2025, 2024, 2023)

===========================================
QUESTION PATTERN BANK (What the board actually asks for THIS topic)
===========================================
Scope: ONLY questions for today's lecture topic are listed below.
DO NOT import questions from other topics or chapters.
These are concept-pattern summaries (what TYPE the board asks), not copies of the
actual questions — never reproduce full question text here.

### Concept: Control flow and loops
  Pattern: MCQ=2, Output Prediction=1, Short Answer=4 | Marks: 1M=4, 2M=2, 5M=1 | Total: 7 questions
  [MCQ] [1M] [Easy] × 2
    → Output/result interpretation for the current concept
  [Short Answer] [1M] [Easy]
    → True/False: nested try/except behaviour
  [Short Answer] [2M] [Easy] × 2
    → Core concept of Control flow and loops
  [Output Prediction] [1M] [Easy]
    → Output/result interpretation for the current concept
  [Short Answer] [5M] [Hard]
    → Output/result interpretation for the current concept


===========================================
IMPORTANCE ANALYSIS (allocate teaching time by this ranking)
===========================================
| Rank | Concept | Score | Times Tested | Total Marks | Recent Years | Priority |
|------|---------|-------|-------------|-------------|--------------|----------|
| 1 | Control flow and loops | 42 | 7 | 13M | 2025, 2024, 2023 | CRITICAL |

EXAMINER FINGERPRINT -- TRAPS TO COVER INTERNALLY

Use this section only for internal slide planning. Do not print this
heading or these internal labels on slides.

For this lecture, the deck must strongly cover these traps:

No static trap list exists yet for "Control flow and loops". Self-generate 4–7 traps from:
- actual question patterns for Control flow and loops
- common wrong assumptions students make about this concept
- output-tracing traps
- syntax-vs-runtime traps
- comparison traps
- order/sequence traps

* Common Mistakes slide must select the top 3 traps from this Examiner
  Fingerprint list.
* PYQ Practice slides must together cover at least 4 traps from the Examiner Fingerprint list.
* Content slides must teach the traps before practice slides test them.

ACTUAL PYQ SET FOR PRACTICE
  Source pool has 7 PYQs.
  Since the pool has 15 or fewer questions, use all 7 actual PYQs.
  Do not replace these with newly framed representative questions.
  Do not compress by dropping, replacing, paraphrasing, or hiding actual PYQs.
  All 7 actual PYQs must appear visibly in the question-only block.
  Grouping related answers on the same answer/explanation slide is allowed only
  for layout efficiency, provided every PYQ still gets:
    - final answer
    - one-line explanation
    - marking point
    - Critical Trap
  Order questions Easy -> Tough; within difficulty, order 1M -> 2M -> 3M -> 4/5M.
  Every PYQ must be visibly accounted for in the question-only block
  and in grouped answer/explanation coverage by concept pattern.
  Each PYQ needs a final answer, one-line explanation, marking point,
  and Critical Trap directly on an answer/explanation slide.
  Do not create substitute or compressed questions for this small source pool.

  Pattern 1. [1M] [Easy/MCQ] Concept: Control flow and loops | source example: 2021
  ```
  Identify the output of the following Python statements.
  x = 2
  while x < 9:
      print(x, end='')
      x = x + 1
  a) 12345678
  b) 123456789
  c) 2345678
  d) 23456789
  ```
  Pattern 2. [1M] [Easy/MCQ] Concept: Control flow and loops | source example: 2021
  ```
  Identify the output of the following Python statements.
  b = 1
  for a in range(1, 10, 2):
      b += a + 2
  print(b)
  a) 31
  b) 33
  c) 36
  d) 39
  ```
  Pattern 3. [1M] [Easy/Short Answer] Concept: Control flow and loops | source example: 2023
  ```
  State True or False:
  "In a Python program, if a break statement is given in a nested loop, it terminates the execution of all loops in one go."
  ```
  Pattern 4. [2M] [Easy/Short Answer] Concept: Control flow and loops | source example: 2024
  ```
  Differentiate between Break and Continue statements in Python.
  ```
  Pattern 5. [1M] [Easy/Output Prediction] Concept: Control flow and loops | source example: 2025
  ```
  Write the output of the following Python code:
  for k in range(7,40,6):
      print ( k + '-' )
  ```
  Pattern 6. [2M] [Easy/Short Answer] Concept: Control flow and loops | source example: 2025
  ```
  B. Explain the difference between break and continue statements in Python with a suitable example.
  ```
  Pattern 7. [5M] [Hard/Short Answer] Concept: Control flow and loops | source example: 2025
  ```
  Write the Python code for the following output (pattern):
  0
  12
  345
  6789
  ```

SLIDE WEIGHTING RULE:
  CONFUSING/CRITICAL concepts --> quick recap first, then highest-priority PYQ drill;
                                  use 'X vs Y' compare slide for look-alikes
  HIGH subtopics     --> own slide
  MEDIUM subtopics   --> 1 bullet max on a shared slide
  Every concept named in the QUESTION PATTERN BANK above MUST appear on a slide —
  a concept the board has actually tested may NEVER be dropped to save slides.

SOURCE POOL RULE:
  Because this source pool has only 7 PYQs, use all 7 actual PYQs.
  Do not drop, replace, paraphrase, or hide any actual PYQ.
  Every PYQ must appear visibly in the question-only block.
  Grouping related answers is allowed only for layout efficiency.
  Compression by omission is allowed only when source pool has more than 15 PYQs.
  If the pool has 15 or fewer PYQs, every actual PYQ must be included and accounted for.
  If a question is reproduced verbatim, show its real year and marks.
  Never fabricate a year, section, paper, or marks badge.

PYQ PRACTICE QUESTION RULE:
  Use EXACTLY 7 actual PYQs from the source pool.
  The authoritative count is the current source count (7), not a hardcoded number.
  If source PYQ count is 15 or fewer, use exactly the source count of actual PYQs.
  If source PYQ count is more than 15, fully discuss the highest-yield 15
  and compactly account for the rest.
  Create 1-2 question-only slide(s), then one answer/explanation slide per question.
  Order practice Easy -> Medium -> Hard; within each difficulty, order
  1M -> 2M -> 3M -> 4/5M.

  PYQ ANSWER VISIBILITY RULE:
  Question-only slides show only question text, real marks badge, and real year badge.
  Answer/explanation slides show the model answer, one-line explanation, and
  "Critical Trap" callout directly on the slide.

SMALL-POOL ACTUAL-QUESTION RULE:
  For this small source pool, use all actual PYQs with real year and marks.
  Do not create substitute, compressed, or newly framed questions.
  Never show fake year, fake section, or fake marks.

NO-FABRICATION RULE (board integrity -- never break this):
  Use EXACTLY 7 actual PYQs from the set above.
  Never fabricate a previous-year question, year, section, paper, or marks badge.

================================================
SECTION G -- QUALITY CHECKLIST (VERIFY BEFORE OUTPUT)
================================================

Visual Checks:
  [ ] Title font >= 44 pt on every slide
  [ ] Body font >= 28 pt on every slide
  [ ] Code font >= 24 pt inside dark card only
  [ ] No font below 24 pt anywhere
  [ ] Every slide has icon, shape, code card, or diagram
  [ ] No unnecessary repeated layout; continuation, paired worked-example, and necessary code-tracing slides may repeat layout.
  [ ] Sandwich: dark Title -> light content -> dark Key Takeaways -> light Exit Ticket
  [ ] { } bracket motif on every content slide
  [ ] NO accent lines under titles
  [ ] NO full-width colour bars or stripes
  [ ] NO cream/beige backgrounds
  [ ] Bullets left-aligned (titles centred only)
  [ ] ONE clear focal point per slide (one hero element, one accent moment)
  [ ] Objects snapped to the grid -- tops/left edges aligned, nothing free-floating
  [ ] Accent colour <= 10% of slide area; cards use 6-8% tints, not saturated fills
  [ ] Every slide's visual carries meaning (no decorative icon-circles / clip-art)
  [ ] At least 60% of each content slide is background + breathing space

Content Checks:
  [ ] CRITICAL/HIGH subtopics in Section D have dedicated slides
  [ ] MEDIUM subtopics are covered on shared slides unless they have multiple
      distinct cases
  [ ] Multi-case subtopics (list, tuple, dict, and string behaviour) have EACH case
      covered, not compressed into one slide
  [ ] Every recap slide is a one-line restatement + one tiny example (no re-teaching)
  [ ] No slide has more than 3 bullets
  [ ] No bullet longer than 10 words
  [ ] Every code example on its own Code Card slide
  [ ] Common Mistakes slide has EXACTLY 3 examiner traps (red accent)
  [ ] Exactly 7 PYQ questions are used.
  [ ] Question-only and answer/explanation coverage is complete.
  [ ] No actual PYQ is silently dropped.
  [ ] Question-only slides show no answer, no explanation, and no trap.
  [ ] Answer slides show model answer + explanation + Critical Trap directly on slide.
  [ ] Key Takeaways slide has EXACTLY 3 takeaways in 3-Icon Grid layout
  [ ] Exit Ticket has 1 question with answer ONLY in speaker notes
  [ ] All speaker notes include teacher dialogue (EXCEPT PYQ Practice answer slides (answer is ON the slide, not in notes) & Exit Ticket (answer in notes) -- Section C)
  [ ] Minimum 2 engagement techniques across speaker notes

Layout Safety Checks:
  [ ] Every slide uses 16:9 widescreen canvas
  [ ] All objects keep at least 0.35 inch margin from slide edges
  [ ] Title stays within y=0.35-1.15 inch and wraps to max 2 lines
  [ ] Body starts at y >= 1.45 inch; large cards/callouts at y >= 1.55 inch
  [ ] Badges stay in the top-right badge zone and never touch title/body
  [ ] No text, badge, icon, card, code block, or diagram overlaps another object
  [ ] No PowerPoint auto-fit has reduced required font sizes
  [ ] Continuation slides are used whenever content would otherwise crowd
  [ ] Rendered slide images have no clipped, hidden, overlapping, or tiny text

29396 chars Customise board, duration & level

Control flow and loops PYQ

Mark Lecture as Missed

Reset All Progress?