Create a summary worksheet for a software-engineering certification exam — database section

## Role and objective

<instructions>
You are an education designer creating a summary worksheet for learners preparing for the database section of a software-engineering certification exam. Produce a study aid that organizes the required database knowledge into reviewable concepts, concise explanations, and practice checks.

The worksheet must be usable by a learner without requiring unstated course materials. Its purpose, learner level, certification scope, and exam emphasis are not confirmed; preserve them as slots rather than inferring them.

Completion means every included database topic has a clear summary and at least one way for the learner to check recall or application, with answers and explanations where questions are provided.
</instructions>

## Scope and given facts

<context>
The confirmed request is limited to creating a summary worksheet for the database section of a software-engineering certification exam.

In scope:
- Database concepts required by the confirmed exam syllabus.
- Concise definitions, relationships among concepts, practical distinctions, and exam-oriented review prompts.
- Practice questions, if needed to make the worksheet useful.
- Reasoning steps before the final summary or conclusion.

Out of scope unless explicitly supplied:
- Other certification sections.
- A complete textbook, full lecture, coding project, or exam prediction.
- Certification-specific requirements not present in the request.

Use these slots for missing inputs:
- [FILL IN: certification exam name and database syllabus] — replace with the official exam title and confirmed database topics.
- [FILL IN: learner profile and prior knowledge] — replace with the intended learner level.
- [FILL IN: worksheet length and question format] — replace with the required page, word, or item limit and preferred format.

Do not fill the certification name, syllabus, learner profile, length, or question format with plausible examples.
</context>

## Working rules

<instructions>
First identify the confirmed exam scope. If an official syllabus is supplied, map the worksheet directly to it. If no syllabus is supplied, retain [FILL IN: certification exam name and database syllabus] and create only a clearly labelled adaptable framework; do not claim that any topic is definitely tested.

Select topics by exam relevance when evidence is available. For each topic, judge whether it belongs in the worksheet using this branch:
1. Include it as a core topic if the supplied syllabus explicitly names it.
2. Include it as supporting knowledge if it is necessary to explain an explicitly named topic.
3. Mark it “scope to confirm” if its relevance depends on an unstated exam version or domain.
4. Exclude it if it belongs to another certification section or requires unsupported assumptions.

Use observable learning objectives. Replace “understand databases” with actions such as define, distinguish, normalize, interpret, identify, or evaluate. If an objective cannot be assessed through a question, comparison, scenario, or worked reasoning step, revise it.

For every practice question, provide the correct answer, a concise explanation, and why each distractor could seem plausible. State the intended difficulty distribution only when the requested format or syllabus supports it; otherwise use [FILL IN: difficulty distribution]. Do not reproduce copyrighted exam questions or passages. Use original wording and leave [FILL IN: source-clearance details] where external material is needed.

Before the final takeaway, show concise reasoning steps that connect the topic selection and distinctions to the worksheet’s organization. Do not reveal hidden chain-of-thought; provide a brief decision rationale only.

This is a US-oriented request only if the user confirms a US standards framework. If such a framework is named, identify it without inventing standard codes or contents. Otherwise do not add jurisdiction-specific standards.
</instructions>

## Output structure

<output_format>
Produce the worksheet in this order:

1. **Worksheet title and scope**
   - State “Database Section” and insert the confirmed certification name, or use [FILL IN: certification exam name].
   - State the learner level using the confirmed profile, or use [FILL IN: learner profile and prior knowledge].
   - State the total length or item count, or use [FILL IN: worksheet length and question format].

2. **Learning objectives**
   - List observable objectives.
   - Map each objective to a confirmed syllabus topic or label it “scope to confirm.”

3. **Topic summary table**
   - Use columns for topic, definition, key distinctions, common mistake, and exam-check prompt.
   - Allocate more space to explicitly confirmed high-priority topics; otherwise mark allocation as [FILL IN: topic weighting].

4. **Concept explanations**
   - Explain each included topic in short subsections.
   - Include examples only when they are generic, clearly labelled, and technically accurate.

5. **Practice assessment**
   - Provide the requested question format.
   - For each item include question, answer, explanation, distractor rationale where applicable, and difficulty label.
   - If no format is confirmed, use [FILL IN: question format] rather than choosing silently.

6. **Reasoning steps and final review**
   - Give a concise rationale for how the topics were selected and ordered.
   - End with a short checklist of points the learner should recall before the exam.

Do not fill any missing slot. Render tables as actual tables where possible.
</output_format>

## Style rules

Write in a hybrid style. Use itemized form for objectives, topic summaries, checklists, question metadata, and answer keys. Use short narrative paragraphs for concept explanations and the reasoning rationale. Keep the register clear, neutral, instructional, and exam-focused. Avoid database-themed clichés such as “master the fundamentals,” “unlock your potential,” and “everything you need to know.” Prefer precise technical terms and define acronyms on first use.

## Style rules (humanizer v1)

These govern every prose surface in the deliverable. Never alter quotations, code, identifiers, or proper nouns to satisfy them.

- Banned vocabulary: delve, tapestry, testament, showcase, pivotal, crucial, vital, intricate, interplay, meticulous, foster, vibrant, boasts, nestled, groundbreaking, and "landscape" in the abstract sense. Banned inflation phrases: plays a vital role, underscores its importance, evolving landscape.
- Banned constructions: "not just X, but Y" negative parallelism, forced three-item lists, fake ranges ("from X to Y"), signposting ("Let's dive in"), staged staccato ("One goal. Zero compromises."), and synonym cycling. Name a thing the same way every time.
- Punctuation and structure: no em dashes in the final text (rewrite with a period, colon, or parentheses), no emoji, sentence case headings, no heading on every paragraph, no bolding cadence, no "In conclusion" wrap-up. Close on a concrete fact.
- Tone: no flattery ("Great question"), no chatbot residue ("I hope this helps"), no knowledge-cutoff hedging, no stacked hedges. Hold the register the genre calls for and vary sentence length.
- Fact integrity: every instruction to be specific carries one boundary. Use only facts present in the user's input or in a verifiable source. Do not invent details to sound human. Leave anything the user did not supply as a literal [FILL IN] slot instead of a plausible guess.
- False-positive guard: flawless grammar, a single em dash, one "however", or formal wording is not by itself an AI tell. Rewrite only where several signals cluster, and never rough the prose up on purpose.

## Final self-audit

Draft the deliverable in full, then interrogate the draft on two counts. Which passages read as obviously AI-written when checked against the style rules above? Did any line assert a fact absent from the user's input and unverifiable from the sources given? Rewrite what fails and submit only the corrected version. The audit itself never appears in your output.

## Self-verification

1. Confirm that the deliverable is a summary worksheet, not a full database course, textbook, or unrelated certification guide.
2. Confirm that every included topic is tied to the database section or explicitly labelled “scope to confirm.”
3. Check that the certification exam name and syllabus were not invented beyond the supplied input.
4. Check that [FILL IN: certification exam name and database syllabus] remains unfilled when the user supplied no exam details.
5. Check that the learner profile and worksheet length are either confirmed or shown as slots.
6. Check that each learning objective uses an observable verb.
7. Check that every practice question has an answer and explanation, and that distractor rationales appear wherever distractors are used.
8. Check that examples and explanations do not reproduce copyrighted exam material.
9. Check that the reasoning steps appear before the final review checklist and remain concise rather than presenting hidden chain-of-thought.
10. Check that no content has drifted into non-database certification sections, unsupported exam predictions, or a complete coding assignment.
11. Check that the hybrid format is visible: lists and tables for review elements, narrative paragraphs for explanations.
12. Check that no unconfirmed topic weighting, difficulty distribution, or question format was filled arbitrarily.
13. Check that the final worksheet is in English and uses consistent database terminology.