🚧 Under construction — VoTechWorks is being built. A free tech program — complimentary, as our commitment to get America working.
voTechWorksGrade 13 · a vocational technology learning center, by urbanicity
newSchoolWorks.com › VoTechWorks › Technology & Design › Data Management / Database Administration › Courses
Technology & Design · course plan
⚠ Pending professional review

This course plan, its lessons and its assessments has not yet been verified by an industry-certified professional or by a certification or approval body. It is a study draft and may contain errors. Do not use it as instructions for work on a job site or on live equipment. Always follow your instructor, your supervising professional, and current official references and regulations.

VoTechWorks program approval and accreditation are still in progress. Credentials are issued only by the certifying bodies named in each program, after their own exams.

Data Management / Database Administration

12 courses · 1,350 clock hours · 6–9 mo full-time. Grading is competency-based: each course requires the written exam, a competent skills demonstration with zero safety faults, a signed log, and a passed safety audit; percentage weights only rank performance above the competency floor.

$13,190 COMPLIMENTARYprogram tuition
12courses
83lessons
1,350hours
43assessments
Development progressPlanCourses, lessons and assessments written for this tradeLessons83 of 83 lesson pages writtenPractice664 practice questionsResources120 reference entries (study list)Review0 lesson pages reviewed by a licensed professional
Study now: 83 lesson pages are open (lesson titles below are links).
TEC-DATA86-01 Universal core

Universal Core: Safety, Math, Communication & Career for Database Administration

148 hr · $1,185 COMPLIMENTARY

This foundational course equips learners with the safety knowledge, technical mathematics, communication skills, and career-readiness behaviors required to enter and succeed in a database administration role. Students earn OSHA 10-Hour General Industry certification and First Aid/CPR recognition, develop the quantitative and literacy skills specific to data environments, and build a professional portfolio entry. All competencies directly support the workplace and exam demands of the PostgreSQL CE, Oracle DBA CA, Microsoft DP-300, and DAMA CDMP Associate credentials.

Outcomes
Course text

This foundational course equips learners with the safety knowledge, technical mathematics, communication skills, and career-readiness behaviors required to enter and succeed in a database administration role. Students earn OSHA 10-Hour General Industry certification and First Aid/CPR recognition, develop the quantitative and literacy skills specific to data environments, and build a professional portfolio entry. All competencies directly support the workplace and exam demands of the PostgreSQL CE, Oracle DBA CA, Microsoft DP-300, and DAMA CDMP Associate credentials.

How the course runs. 7 blocks: Workplace Safety in Data Centers and Server Rooms (OSHA 10 Core); First Aid, CPR, and Emergency Response for Technology Workplaces; Trade Math for Database Administration; Reading Technical Documentation and Standards; Digital Tools for Database Professionals; Technical Writing and Professional Communication; Career Readiness: Credentials, Portfolio, and Professional Identity.

What competent looks like. Complete OSHA 10-Hour General Industry training and demonstrate correct hazard identification, lockout/tagout procedures, and ergonomic practices applicable to a server room and data-center environment. Perform trade-relevant mathematics including binary/hexadecimal conversions, storage-capacity calculations, and basic statistical measures used in database sizing and performance baselining. Read and interpret technical documentation such as vendor release notes, schema diagrams, man pages, and regulatory data-governance standards with demonstrated comprehension. Use standard digital productivity tools—including spreadsheets, ticketing systems, and collaborative document platforms—to organize and communicate database work. Produce and deliver professional written and oral communications including incident reports, change-request forms, and technical presentations appropriate to a DBA role. Develop a career-readiness plan that includes a current resume, a LinkedIn profile, and knowledge of credential pathways for PostgreSQL CE, Oracle DBA CA, Microsoft DP-300, and DAMA CDMP Associate.

Lessons · 7 blocks
#LessonHrTypeObjectiveActivitiesMaterialsCheck
1Workplace Safety in Data Centers and Server Rooms (OSHA 10 Core)24theoryStudents will complete all ten hours of OSHA 10-Hour General Industry content and demonstrate correct identification of electrical, ergonomic, and physical hazards present in data-center and server-room environments.
  1. Complete all OSHA 10-Hour General Industry modules (delivered by an OSHA-authorized trainer) covering hazard communication, electrical safety, personal protective equipment selection, emergency action plans, and walking/working surfaces relevant to a raised-floor server room.
  2. Participate in a table-top scenario in which a simulated server-room incident—such as a cable-management tripping hazard or an uninterruptible power supply (UPS) battery leak—requires students to identify the hazard class, select the correct PPE, and walk through the written lockout/tagout (LOTO) procedure for de-energizing a rack before maintenance.
  3. Write a one-page Hazard Identification Report for a provided server-room floor-plan image, tagging at least six distinct hazard types with the applicable OSHA General Industry standard section (general reference only) and a recommended corrective action.
OSHA 10-Hour General Industry course materials (OSHA-authorized trainer or accredited online provider), OSHA Hazard Communication Quick Card, sample LOTO procedure form, PPE selection guide, provided server-room floor-plan handout, loose-leaf binder for student safety portfolioOSHA 10 completion card issued by the authorized trainer (mandatory); Hazard Identification Report scored on a rubric requiring correct hazard class, appropriate PPE, and a plausible corrective action for at least five of six items — 83% or higher to pass.
2First Aid, CPR, and Emergency Response for Technology Workplaces10demoStudents will perform adult CPR and AED operation to the standard required for a recognized First Aid/CPR certification and describe the emergency response steps specific to electrical-shock incidents common in data-center settings.
  1. Attend a full hands-on First Aid/CPR/AED course delivered by an instructor certified through a nationally recognized provider (such as American Red Cross or American Heart Association), practicing adult CPR on a manikin until compression rate and depth meet certification criteria.
  2. Practice a two-person scenario: one student acts as a bystander who discovers a colleague who has received an electrical shock from an open server chassis, correctly sequencing scene safety (power isolation before touching the victim), calling emergency services, and initiating CPR while the second student retrieves and operates the classroom AED trainer.
  3. Debrief using a written checklist that maps each step of the electrical-shock scenario to the broader Emergency Action Plan concept from OSHA 10, reinforcing how first-aid response integrates with the site's emergency procedures.
CPR manikins (one per two students), AED trainer unit, First Aid/CPR/AED student workbook from the certifying provider, disposable face shields, exam gloves, electrical-shock scenario script, debrief checklistPassing score on the certifying provider's First Aid/CPR skills evaluation and written knowledge check (provider pass standard applies, typically 80% or higher); mandatory attendance for certification card issuance.
3Trade Math for Database Administration28practiceStudents will correctly convert between binary, octal, and hexadecimal numbering systems and perform storage-capacity, throughput, and basic descriptive-statistics calculations used in database sizing, performance analysis, and capacity planning.
  1. Complete a structured drill set covering number-base conversions (binary ↔ decimal ↔ hex), byte-unit arithmetic (kilobytes through terabytes, including IEC vs. SI prefixes), and IP-subnet calculations; check answers with a provided key and correct errors in a second-attempt column.
  2. Work through a database-sizing case study: given a fictional application's row count, average row width in bytes, expected annual growth rate, and a replication factor, calculate raw storage requirements, usable capacity after overhead, and projected three-year storage cost at a stated price-per-gigabyte—replicating the kind of sizing estimate a DBA presents to management.
  3. Use a spreadsheet (Microsoft Excel or LibreOffice Calc) to build a simple performance-baseline dashboard that calculates mean, median, and standard deviation for a provided set of query response-time samples, then formats the results as a table and a bar chart suitable for an incident report — a skill directly relevant to Oracle DBA CA performance-tuning exam objectives and DAMA CDMP data-quality metrics.
Scientific calculator, Microsoft Excel or LibreOffice Calc (installed on lab workstations), drill-set handout, database-sizing case study worksheet, provided query-response-time data CSV file, IEEE/NIST unit-prefix reference cardScored math quiz covering number-base conversions and byte arithmetic — 80% or higher to pass; completed spreadsheet dashboard submitted and checked against an answer key for correct formulas, accurate statistics, and readable chart — all three sections must be correct or corrected within the class period.
4Reading Technical Documentation and Standards20theoryStudents will extract accurate procedural steps, configuration parameters, and data-governance requirements from vendor documentation, man pages, and standards excerpts such as those referenced by the DAMA DMBOK and the Microsoft DP-300 exam.
  1. Work through an annotated reading exercise using three real document types side by side: a PostgreSQL official documentation page for a configuration parameter (e.g., the postgresql.conf shared_buffers setting), a Linux man page for a command used in DBA work (e.g., pg_dump), and an excerpt from the DAMA DMBOK2 chapter on data quality — students highlight the action verb, the parameter name, the valid value range, and any warning or note callouts in each document.
  2. Complete a comprehension quiz in which 10 short-answer questions require students to answer only from the provided documentation excerpts (no outside knowledge), simulating the careful, evidence-based reading required when following runbook procedures during a live incident.
  3. In pairs, compare two versions of a PostgreSQL release note (an older and a newer minor release) to identify deprecated parameters and behavioral changes, then write a three-sentence summary of what a DBA would need to update in an existing configuration — building the change-management literacy tested in the Oracle DBA CA and Microsoft DP-300 exams.
Printed excerpts from PostgreSQL official documentation (postgresql.org), Linux man page printouts, DAMA DMBOK2 selected chapter excerpt (instructor-provided), two PostgreSQL release notes printouts, comprehension quiz handout, highlightersComprehension quiz score of 80% or higher to pass; release-note comparison summary evaluated on a rubric requiring identification of at least two genuine changes and a clear, grammatically correct explanation — both criteria must be met.
5Digital Tools for Database Professionals20labStudents will use a ticketing or task-management system, a collaborative document editor, and a version-control platform to organize and communicate DBA work in the formats used by professional teams.
  1. Set up accounts on a version-control platform (GitHub or an equivalent) and practice the basic Git workflow—clone, edit, commit, push, pull request—by submitting a simple Markdown-formatted runbook for a database backup procedure; the instructor reviews the pull request and students respond to one comment, simulating a real code-review cycle.
  2. Enter a provided simulated incident (a fictional database outage scenario) into a ticketing system (such as a free Jira project or the school's helpdesk platform), filling in all required fields: priority, affected system, steps to reproduce, resolution steps, and time-to-resolve — practicing the documentation habits expected of an Oracle DBA CA or Microsoft DP-300 certified administrator.
  3. Create a one-page technical knowledge-base article in a collaborative editor (Google Docs or Microsoft 365) explaining how to check PostgreSQL service status on a Linux server, using proper heading hierarchy, a numbered procedure list, a code block for commands, and a notes/warnings section — the article is shared with a peer who follows it on a lab VM and reports any step that fails or is unclear.
Lab workstations with internet access, GitHub accounts (free tier), Git client (Git Bash or built-in terminal), Jira free-tier project or school helpdesk system, Google Docs or Microsoft 365, incident scenario handout, Markdown reference card, peer-review checklistPull request merged after instructor approval of correctly formatted Markdown runbook (no merge without at least one substantive revision); ticketing entry scored on a five-field completeness rubric — all five fields populated correctly to pass; peer tester must successfully complete the knowledge-base article procedure without instructor assistance — article revised if tester reports a failure.
6Technical Writing and Professional Communication22practiceStudents will write a database incident report and a formal change-request form that meet professional standards for clarity, completeness, and technical accuracy, and will deliver a structured five-minute technical briefing to a non-technical audience.
  1. Using a provided scenario (a fictional midnight database crash with supplied log excerpts), draft a complete post-incident report following a standard template with sections for: executive summary, timeline, root-cause analysis, impact statement, corrective actions taken, and preventive recommendations — applying the writing style guidance that plain language is essential in documentation reviewed by auditors and managers (a DAMA CDMP data-governance principle).
  2. Complete a formal Change-Request Form for a proposed PostgreSQL version upgrade on a production server, filling in all fields: requestor, system affected, reason for change, risk assessment, rollback plan, implementation window, and approval signatures — then exchange forms with a partner and use a provided checklist to identify any missing or vague fields before both forms are revised and resubmitted.
  3. Deliver a five-minute stand-up briefing to the class explaining the database incident from the first activity in plain language suitable for a department manager with no database background; use one visual aid (a timeline slide or a simple diagram) and respond to two instructor questions — developing the communication competency assessed in the DAMA CDMP Associate exam's professional development domain.
Incident scenario packet with fictional log excerpts, post-incident report template, Change-Request Form template, peer-review checklist, slide-creation software (PowerPoint or Google Slides), classroom projector or display, timerIncident report scored on rubric: all six sections present, root cause stated specifically, corrective actions are actionable — 80% or higher to pass; Change-Request Form must have all eight fields completed correctly after revision; oral briefing assessed on clarity, correct facts from the scenario, and a satisfactory response to both instructor questions — all three criteria must be met.
7Career Readiness: Credentials, Portfolio, and Professional Identity24fieldStudents will produce a resume, a LinkedIn profile, and a written credential-pathway plan that accurately maps the PostgreSQL CE, Oracle DBA CA, Microsoft DP-300, and DAMA CDMP Associate certifications to job roles and career stages in database administration.
  1. Research and produce a one-page Credential Pathway Map that lists the four target credentials in this program, the vendor or issuing body for each, the recommended order in which a new DBA might pursue them based on exam prerequisites and typical employer expectations, and at least two job titles for which each credential is commonly listed in real job postings — students cite at least three actual job postings (printed or screenshot) as evidence.
  2. Draft a professional resume using a clean, ATS-friendly format; the resume must include a skills section listing relevant technical skills (e.g., SQL, PostgreSQL, data modeling, backup/recovery), an education section referencing this program, and a projects section with a placeholder for the course-5 capstone — a career-services advisor or the instructor conducts a 10-minute resume review session with each student.
  3. Build or update a LinkedIn profile to include a professional headline that names the DBA credential path (e.g., 'Database Administration Student | PostgreSQL | Oracle | Microsoft DP-300'), a summary paragraph written in first person, the program education entry, and at least two skills endorsable by peers — students connect with at least three classmates and the instructor, and post a brief public learning update about one technical topic from the program.
Computers with internet access, LinkedIn accounts, word processor, at least three printed or screenshotted real job postings per student, Credential Pathway Map template, resume template (ATS-friendly), career-services rubric, instructor feedback formCredential Pathway Map must correctly identify all four credentials with their issuing bodies and include evidence from at least three real job postings — any factual error about a credential requires correction before a passing grade is awarded; resume must pass the career-services rubric with all required sections present and no fabricated credentials or experience — resubmission required if deficiencies are found; LinkedIn profile must be set to public, contain all four required elements, and show at least three connections — screenshot submitted as evidence.
Assessments
AssessmentTypeWeightPass standardMethod & rubric
OSHA and Workplace Safety Knowledge ExamWritten exam25%80% or higher; any question about lockout/tagout or electrical safety that is answered incorrectly must be remediated in a one-on-one review before the student advances.A 40-question multiple-choice and short-answer exam covering OSHA 10 General Industry content as applied to data-center and server-room environments, including hazard communication, PPE selection, electrical safety, ergonomics, and emergency action plans. Questions are drawn from the OSHA 10 topic areas and the data-center hazard scenarios practiced in class.
Accuracy · Safety · Communication · Professionalism
Trade Math and Technical Literacy ExamWritten exam25%80% or higher across both sections (math and reading comprehension); a score below 80% in either section requires targeted tutoring and a single retake within one week.A two-section, closed-book exam: Section A contains 20 calculation problems covering number-base conversions, storage-unit arithmetic, and descriptive statistics; Section B contains 15 reading-comprehension questions based on unseen excerpts from PostgreSQL documentation and a DAMA DMBOK2 passage. This exam validates the quantitative and literacy foundations required for the technical courses that follow and for the DAMA CDMP Associate exam's foundational knowledge domain.
Accuracy · Safety · Communication · Professionalism
Professional Communications PortfolioProject25%Each of the four portfolio artifacts (incident report, change-request form, knowledge-base article, and resume) must individually score 80% or higher on its rubric; any artifact below 80% must be revised and resubmitted within one week.Students submit a folder containing all written deliverables produced during lessons 5 and 6: the post-incident report, the change-request form, the Git-committed Markdown runbook, and the finalized resume. Each artifact is scored against its lesson rubric, and the portfolio as a whole is reviewed for professional consistency of tone, formatting, and factual accuracy — competencies directly assessed in the DAMA CDMP Associate professional-development domain.
Accuracy · Safety · Communication · Professionalism
Career and Safety Oral DefenseOral / panel25%Student must correctly answer at least four of five questions, including at least one safety question and at least one credential-pathway question, with no fabricated credential facts; a failed defense may be retaken once after a 48-hour preparation period.A 15-minute individual oral session in which the instructor poses five questions drawn from three areas: workplace safety procedures (OSHA and first aid), the student's credential-pathway plan and the rationale for the ordering of the four target certifications, and the student's own resume and portfolio artifacts. The student must answer from genuine knowledge without reference to notes, demonstrating the professional fluency expected of an entry-level DBA preparing to sit industry certification exams.
Accuracy · Safety · Communication · Professionalism
TEC-DATA86-02 Trade course

Relational Design & Normalization

92 hr · $1,105 COMPLIMENTARY

Students learn to design relational databases from business requirements, applying entity-relationship modeling and normalization through Boyce-Codd Normal Form to eliminate redundancy and anomalies. Emphasis is placed on translating real-world data needs into schema definitions, enforcing referential integrity through keys and constraints, and documenting designs to professional standards. Concepts map directly to the data modeling domains tested in the DAMA CDMP Associate exam and the schema-design knowledge expected in Oracle DBA CA, PostgreSQL CE, and Microsoft DP-300.

Outcomes
Course text

Students learn to design relational databases from business requirements, applying entity-relationship modeling and normalization through Boyce-Codd Normal Form to eliminate redundancy and anomalies. Emphasis is placed on translating real-world data needs into schema definitions, enforcing referential integrity through keys and constraints, and documenting designs to professional standards. Concepts map directly to the data modeling domains tested in the DAMA CDMP Associate exam and the schema-design knowledge expected in Oracle DBA CA, PostgreSQL CE, and Microsoft DP-300.

How the course runs. 8 blocks: Foundations of the Relational Model; Entity-Relationship Modeling; Mapping ERDs to Relational Schemas; Normalization: 1NF through 3NF; BCNF and Higher Normal Forms; Denormalization Trade-offs; Keys, Constraints, and Referential Integrity in SQL DDL; Data Dictionary and Design Documentation; Integrated Schema Design Project.

What competent looks like. Construct entity-relationship diagrams from written business requirements and convert them to fully attributed relational schemas. Apply 1NF through BCNF normalization rules to decompose tables, eliminate redundant data, and prevent insertion, update, and deletion anomalies. Define primary keys, foreign keys, unique constraints, check constraints, and NOT NULL constraints that enforce data integrity in a relational schema. Write and execute Data Definition Language (DDL) statements in SQL to create, alter, and drop normalized tables in a relational database engine. Evaluate a given schema for design deficiencies and produce a written justification of normalization decisions using standard data management terminology. Produce complete data model documentation—including an ERD, data dictionary, and constraint inventory—that meets professional handoff standards.

Lessons · 8 blocks
#LessonHrTypeObjectiveActivitiesMaterialsCheck
1Foundations of the Relational Model10theoryStudents will accurately describe the core concepts of the relational model—relations, tuples, attributes, domains, and keys—and explain how they differ from flat-file storage.
  1. Lecture and annotated reading: students read selected sections of a standard database textbook (e.g., Ramakrishnan & Gehrke, 'Database Management Systems') covering Codd's relational model, then annotate key terms in a shared glossary document.
  2. Compare-and-contrast exercise: students receive a flat CSV file of customer orders and a two-table relational version; they list every duplicate value, identify update anomalies in the flat file, and present findings to the class.
  3. Concept-mapping quiz: students individually draw a labeled diagram connecting the terms relation, tuple, attribute, domain, candidate key, primary key, and surrogate key, and submit it for instructor review.
Whiteboard, projector, database textbook, sample CSV order file, blank concept-map templates, spreadsheet softwareInstructor reviews concept maps; students must correctly define all seven terms and correctly identify at least two anomalies in the flat-file exercise. Pass: 70% accuracy on a 10-question vocabulary check.
2Entity-Relationship Modeling14demoStudents will create crow's-foot ERDs that correctly represent entities, attributes, and binary relationships (one-to-one, one-to-many, many-to-many) from a written business narrative.
  1. Instructor live-demo: model a library system (books, members, loans) step-by-step in draw.io using crow's-foot notation while students replicate each step on their own screens.
  2. Pair exercise: each pair receives a one-page business narrative for a small retail store and must identify all entities, their attributes, and all relationships, then draw a complete ERD in draw.io and walk the class through one relationship.
  3. Critique session: pairs swap ERDs, identify missing entities or cardinality errors using a provided checklist, and give written feedback that the original team must respond to in a revision.
draw.io (free, browser-based), printed business narratives, crow's-foot notation reference card, checklist template, projectorInstructor evaluates final revised ERD against the business narrative using a 10-point rubric (entities complete, attributes complete, cardinalities correct, naming conventions followed). Pass: 7/10.
3Mapping ERDs to Relational Schemas10demoStudents will convert a completed ERD into a relational schema by applying the standard mapping rules for all relationship types, including resolution of many-to-many relationships into junction tables.
  1. Step-by-step guided mapping: instructor converts the library ERD from Lesson 2 into a schema diagram on the board, narrating each mapping rule (one entity → one table, many-to-many → junction table, one-to-many → foreign key in the 'many' table).
  2. Mapping worksheet: students individually map the retail-store ERD they built in Lesson 2 into a schema, writing out each table name, column names, and underlined/highlighted key columns on a structured worksheet.
  3. Schema notation exercise: students rewrite their worksheet schemas using standard SQL-like notation (table_name(col1 PK, col2, col3 FK → other_table.col)) and peer-check notation correctness.
Whiteboard, mapping rules handout, structured mapping worksheet, retail-store ERD from Lesson 2, SQL notation referenceInstructor checks mapping worksheet and notation; all relationship types from the ERD must be correctly represented in the schema. Pass: correct mapping of at least 9 of 10 relationships on a schema-mapping quiz.
4Normalization: 1NF through 3NF14theoryStudents will identify violations of First, Second, and Third Normal Form in a given table and decompose it into 3NF-compliant tables without losing data or functional dependencies.
  1. Lecture with worked examples: instructor presents the definition of each normal form, demonstrates a violation, and walks through decomposition using a running 'employee-project-department' example on the projector.
  2. Normalization worksheet: students receive an un-normalized invoice table with repeating groups, partial dependencies, and transitive dependencies; they decompose it step-by-step, labeling each violation and the normal form achieved after each step.
  3. Group discussion: each student group presents one normalization step to the class and explains why the decomposition preserves the original data (lossless join) using a join example.
Normalization rules reference handout, un-normalized invoice table dataset, decomposition worksheet, projector, whiteboardInstructor scores the completed decomposition worksheet: each step labeled correctly (violation identified, NF named, correct decomposition). Pass: all three decomposition stages correct with violations correctly labeled (70% of rubric points).
5BCNF and Higher Normal Forms; Denormalization Trade-offs10theoryStudents will distinguish BCNF from 3NF, identify BCNF violations caused by overlapping candidate keys, and articulate when controlled denormalization is appropriate for performance.
  1. Worked example lecture: instructor presents a course-scheduling table that is in 3NF but not BCNF, identifies the violating functional dependency, and performs the BCNF decomposition while class checks for lossless join and dependency preservation.
  2. Case-study analysis: students read a short scenario describing a data warehouse reporting table that uses intentional denormalization for query speed; they write a half-page analysis identifying which normal forms are violated and what trade-offs the designers accepted.
  3. Structured debate: half the class argues for normalizing an e-commerce product catalog fully; the other half argues for strategic denormalization; instructor facilitates using industry examples (OLTP vs. OLAP context).
BCNF example tables handout, data warehouse case-study reading, whiteboard, timer for debateStudents submit the written case-study analysis. Instructor checks that the BCNF violation is correctly identified and the trade-off discussion is logically sound. Pass: rubric score of 70% (violation identified correctly and at least two valid trade-offs articulated).
6Keys, Constraints, and Referential Integrity in SQL DDL14labStudents will write DDL statements (CREATE TABLE, ALTER TABLE) that implement primary keys, foreign keys, unique constraints, check constraints, and NOT NULL constraints in PostgreSQL, and verify that the database engine enforces each constraint.
  1. Guided lab: instructor demonstrates creating a normalized three-table schema (customer, order, order_line) in PostgreSQL using psql, defining all constraints inline and then adding one with ALTER TABLE; students follow along in their own psql session.
  2. Constraint-testing lab: students insert rows that intentionally violate each constraint type (duplicate PK, null in NOT NULL column, orphan FK, check violation), observe the error messages, and record results in a lab log.
  3. Schema build: students translate their normalized retail-store schema from Lesson 3 into a complete set of CREATE TABLE DDL statements in PostgreSQL with all constraints and confirm all tables are created with correct structure using \\d in psql.
PostgreSQL installed on lab workstations or cloud sandbox, psql command-line client, DDL reference (PostgreSQL documentation Chapter 5), lab log templateInstructor queries information_schema.table_constraints and information_schema.columns to verify each required constraint exists. Pass: all primary keys, at least one foreign key per relationship, and at least one check constraint present; all constraint-test errors correctly recorded in lab log.
7Data Dictionary and Design Documentation10practiceStudents will produce a professional data dictionary for a multi-table schema that documents each table, column, data type, constraint, allowed values, and business definition.
  1. Instructor demonstration: show a completed data dictionary for a sample HR schema using a structured spreadsheet template (one row per column, columns for table name, column name, data type, nullable, constraints, business definition, example value); explain why each field matters for governance and handoffs.
  2. Data dictionary build: students complete a data dictionary for their retail-store PostgreSQL schema, filling in every field for every column from their DDL and the original business narrative.
  3. Peer review: partners review each other's data dictionary against the DDL and business narrative, flagging any columns missing definitions or data types inconsistent with the DDL, and return a written review; author revises before submission.
Data dictionary spreadsheet template, retail-store DDL from Lesson 6, business narrative from Lesson 2, PostgreSQL \d output for referenceInstructor evaluates the final data dictionary: every column documented, data types match DDL, business definitions are in plain English and accurate to the narrative. Pass: 90% of columns fully and accurately documented (rubric).
8Integrated Schema Design Project10labStudents will independently design, normalize, implement, and document a relational database schema from a new business requirements narrative, demonstrating end-to-end mastery of all course skills.
  1. Requirements analysis: students receive a two-page business requirements narrative for a veterinary clinic management system; they independently identify entities, attributes, and relationships and draw a crow's-foot ERD in draw.io.
  2. Schema build and normalization: students map the ERD to a relational schema, verify normalization to at least 3NF (documenting each normal form check), write complete PostgreSQL DDL with all constraints, and execute it in a clean PostgreSQL database.
  3. Defense preparation: students prepare a five-minute oral presentation with their ERD, schema diagram, normalization justification, and data dictionary excerpt, then present to the instructor and two peers who use a structured evaluation rubric.
Veterinary clinic business requirements narrative, draw.io, PostgreSQL lab environment, data dictionary template, oral defense rubric, projectorInstructor evaluates ERD completeness, normalization correctness (must reach at least 3NF with documented justification), DDL execution without errors, and quality of data dictionary. Oral defense must correctly answer two instructor questions about design decisions. Pass: 75% of total rubric points; DDL must execute without errors.
Assessments
AssessmentTypeWeightPass standardMethod & rubric
Relational Design Knowledge ExamWritten exam25%70% correct (28 of 40 questions)A 40-question closed-book exam covering relational model concepts, ER modeling rules, mapping rules, normalization definitions and procedures through BCNF, constraint types, and referential integrity. Questions are multiple-choice and short-answer; the exam is timed at 80 minutes and maps to the DAMA CDMP Associate data modeling domain and the schema-knowledge sections of Oracle DBA CA and PostgreSQL CE.
Standard met · Safety · Time · Quality/finish · Documentation
Schema Design Skills DemonstrationSkills demonstration45%75% of rubric points; DDL must execute without errors in PostgreSQLStudents receive a previously unseen one-page business requirements narrative and have 90 minutes to produce an ERD, a normalized relational schema with normalization justification to at least 3NF, and working CREATE TABLE DDL with all required constraints executed in PostgreSQL. The instructor evaluates the artifact immediately using a structured 20-point rubric.
Standard met · Safety · Time · Quality/finish · Documentation
Lab Log PortfolioLog15%All six required lab entries present and accurate; 80% of rubric pointsStudents submit their cumulative lab log maintained across Lessons 6 and 7, containing records of every constraint test (including the error message received, constraint type, and what the test proved), the DDL for their retail-store schema, and the final veterinary clinic DDL execution transcript. Entries must be complete, accurate, and written in clear technical prose.
Standard met · Safety · Time · Quality/finish · Documentation
Workstation and Data Safety CheckSafety audit15%Pass/Fail — all critical items must be met; no critical items may be missedInstructor observes and scores each student on: correct ergonomic workstation setup (monitor height, keyboard position, lighting per OSHA computer workstation guidelines), proper cable management to eliminate trip hazards in the lab, correct procedure for saving and backing up work before ending a lab session, and knowledge of the lab's emergency exit and first-aid kit location. Any critical safety item missed results in an automatic fail and remediation before the student continues lab work.
Standard met · Safety · Time · Quality/finish · Documentation
TEC-DATA86-03 Trade course

PostgreSQL Administration

91 hr · $1,090 COMPLIMENTARY

Students install, configure, and administer PostgreSQL database servers in single-instance and replicated environments, applying industry-standard practices for object management, performance tuning, and user access control. Hands-on labs mirror real DBA workflows and map directly to EnterpriseDB PostgreSQL CE exam domains. This course builds the technical foundation required for all subsequent backup/recovery and security courses in the program.

Outcomes
Course text

Students install, configure, and administer PostgreSQL database servers in single-instance and replicated environments, applying industry-standard practices for object management, performance tuning, and user access control. Hands-on labs mirror real DBA workflows and map directly to EnterpriseDB PostgreSQL CE exam domains. This course builds the technical foundation required for all subsequent backup/recovery and security courses in the program.

How the course runs. 8 blocks: Server-Room Safety, PostgreSQL Architecture, and Installation on Linux; Core Configuration: postgresql.conf and pg_hba.conf; Database Objects: Databases, Schemas, Tables, Sequences, and Views; SQL in PostgreSQL: Queries, Joins, CTEs, and Window Functions; Indexing Strategy and Query Plan Analysis with EXPLAIN ANALYZE; User Management, Roles, and Object Privileges; Streaming Replication Setup and Failover; Routine Maintenance: VACUUM, ANALYZE, pg_dump, and Monitoring.

What competent looks like. Install and configure a PostgreSQL server instance on Linux, setting correct file-system permissions and verifying service startup with pg_ctl and systemd. Create and manage databases, schemas, tables, indexes, views, and sequences using both psql and pgAdmin, applying naming conventions and storage parameters. Write and optimize SQL queries in PostgreSQL, using EXPLAIN ANALYZE to interpret query plans and select appropriate index types (B-tree, Hash, GIN, BRIN). Configure postgresql.conf and pg_hba.conf parameters for memory, connections, logging, and client authentication, documenting each change with a justification. Set up streaming replication between a primary and standby server, verify replication lag using pg_stat_replication, and perform a controlled failover. Apply safe physical workspace practices in a server-room environment, including proper cable management, equipment handling, and recognition of electrical and ergonomic hazards.

Lessons · 8 blocks
#LessonHrTypeObjectiveActivitiesMaterialsCheck
1Server-Room Safety, PostgreSQL Architecture, and Installation on Linux12labStudents install PostgreSQL on a Linux server VM, verify the service is running, and identify physical and electrical hazards in a server-room environment.
  1. Complete a server-room safety walkthrough checklist covering electrical panel locations, raised-floor trip hazards, proper lifting technique for equipment, and recognition of when PPE (ESD wrist strap, safety shoes) is required; record findings in a signed safety log.
  2. Use the PostgreSQL global development group (PGDG) repository to install a current stable PostgreSQL release on a Rocky Linux or Ubuntu VM, then start, stop, and reload the service using both pg_ctl and systemctl, capturing terminal output as evidence.
  3. Draw a labeled architecture diagram showing the PostgreSQL process model (postmaster, backend worker, WAL writer, checkpointer, autovacuum launcher) and the major on-disk directory structure ($PGDATA, pg_wal, pg_base), then explain each component to a partner.
Linux VM (VirtualBox or cloud sandbox), PGDG repository docs, postgresql.org installation guide, ESD wrist straps, server-room safety checklist handout, PostgreSQL 16 Documentation Chapter 18 (Server Setup and Operation)Instructor verifies service is active (systemctl status), correct data-directory ownership (postgres user), and completed safety checklist with all fields signed; pass = service running AND checklist 100% complete.
2Core Configuration: postgresql.conf and pg_hba.conf10theoryStudents adjust key server parameters in postgresql.conf and write client authentication rules in pg_hba.conf, explaining the effect of each change.
  1. Read PostgreSQL Documentation Chapter 20 (Client Authentication) and Chapter 19 (Server Configuration); annotate a printed excerpt identifying the ten most commonly tuned parameters (shared_buffers, work_mem, max_connections, wal_level, etc.) and the authentication methods available in pg_hba.conf.
  2. Using a provided scenario card (e.g., 'production server with 64 GB RAM, 200 concurrent users'), calculate recommended values for shared_buffers (roughly 25% of RAM as a starting point per community guidance) and work_mem, enter them in postgresql.conf, reload the server, and confirm changes with SHOW statements.
  3. Write three pg_hba.conf rules covering local ident, md5, and scram-sha-256 authentication for different client CIDRs; attempt connections as test users to verify each rule fires correctly, logging results in a configuration journal.
PostgreSQL 16 Documentation Chapters 19–20, pgtune.leopard.in.ua reference (for instructor demonstration only), psql client, configuration journal templateInstructor reviews configuration journal for correct parameter syntax, valid pg_hba.conf rules, and SHOW output screenshots; pass = all three authentication scenarios work as intended AND journal entries explain reasoning.
3Database Objects: Databases, Schemas, Tables, Sequences, and Views12labStudents create a multi-schema database with tables, sequences, views, and constraints using both psql DDL commands and the pgAdmin GUI.
  1. Using psql, create a database named inventory_db, add two schemas (warehouse and sales), and build at least six tables with primary keys, foreign keys, NOT NULL constraints, and a CHECK constraint; export the DDL with pg_dump --schema-only and review it.
  2. Use pgAdmin 4 to inspect the object tree for inventory_db, modify a table by adding a generated column, create a view joining two tables across schemas, and take annotated screenshots of each step for a lab report.
  3. Create a sequence manually, associate it with a column using OWNED BY, then demonstrate the difference between SERIAL, BIGSERIAL, and GENERATED ALWAYS AS IDENTITY to a partner using a prepared script, explaining which PostgreSQL versions introduced each approach.
PostgreSQL 16 server VM, pgAdmin 4, psql, PostgreSQL Documentation Chapter 5 (DDL), lab report template, sample dataset (CSV files for import)Instructor runs a provided verification script that queries pg_tables, pg_views, and information_schema.columns to confirm correct object creation; pass = all objects present with correct constraints AND lab report submitted.
4SQL in PostgreSQL: Queries, Joins, CTEs, and Window Functions11practiceStudents write complex queries using joins, CTEs, and window functions against a multi-table PostgreSQL database, producing correct result sets.
  1. Complete a structured query exercise set of 15 problems of increasing difficulty against the inventory_db dataset, covering INNER/LEFT/FULL OUTER joins, correlated subqueries, and aggregates with GROUPING SETS; self-check answers against a provided answer key.
  2. Rewrite two of the subquery problems using Common Table Expressions (WITH clauses) and a third using a recursive CTE to generate a product category hierarchy; compare readability and explain to the class why each form was chosen.
  3. Write three analytical queries using window functions (ROW_NUMBER, RANK, LAG) to identify top-selling products by region and month; verify results are identical to equivalent non-window approaches using a provided validation query.
PostgreSQL 16 VM with inventory_db, psql, DBeaver (optional GUI), PostgreSQL Documentation Chapter 7 (Queries), query exercise booklet, answer key (instructor copy)Instructor spot-checks five randomly selected exercises for correct output using a diff against the answer key; pass = at least 80% of the 15 exercises produce correct result sets.
5Indexing Strategy and Query Plan Analysis with EXPLAIN ANALYZE11demoStudents select appropriate index types for given query patterns and use EXPLAIN ANALYZE output to measure and document query performance improvements.
  1. Instructor demonstrates reading an EXPLAIN ANALYZE plan for a sequential scan vs. an index scan on a 500,000-row table; students annotate a printed plan identifying cost, actual rows, and buffers, then replicate the demo on their own VMs.
  2. Given four query scenarios (equality search on a low-cardinality column, full-text search, range scan on a date column, JSONB containment query), students create B-tree, GIN, BRIN, and GIN indexes respectively, run EXPLAIN ANALYZE before and after each index, and record the planning and execution time reduction in an index performance table.
  3. Students identify and drop two redundant indexes on a provided schema using pg_stat_user_indexes (idx_scan = 0 heuristic), document the decision in a written justification, and verify the table statistics are current using ANALYZE before making the decision.
PostgreSQL 16 VM, pgbench (for data generation), EXPLAIN ANALYZE output printer-friendly format, index performance table template, PostgreSQL Documentation Chapter 11 (Indexes) and Chapter 14 (Performance Tips)Instructor reviews index performance table for all four scenarios and checks that EXPLAIN plans are attached; pass = documented planning-time or execution-time improvement for each index AND written justification for dropped indexes is logically sound.
6User Management, Roles, and Object Privileges10labStudents create roles and users, assign object privileges using GRANT/REVOKE, and verify access control behavior by testing connections as different database users.
  1. Create a role hierarchy with three roles (readonly_role, data_entry_role, dba_role) and four users; assign roles using GRANT role TO user, then test each user's privileges with SET ROLE and attempt SELECT, INSERT, UPDATE, and DELETE on protected tables, logging results.
  2. Use pg_roles, pg_user, information_schema.role_table_grants, and has_table_privilege() to audit current privileges; produce a privilege matrix spreadsheet mapping each user to allowed operations on each table.
  3. Demonstrate and explain the principle of least privilege by reconfiguring a scenario where a data_entry user has been inadvertently granted superuser; revoke excess privileges, re-test, and document the before/after states.
PostgreSQL 16 VM, psql, privilege matrix spreadsheet template, PostgreSQL Documentation Chapter 21 (Database Roles) and Chapter 5 Section 7 (Privileges), DAMA DMBOK2 Chapter on Data Security (reference)Instructor runs a privilege audit script against the student's database and compares to the submitted privilege matrix; pass = matrix is accurate AND all four users have only their intended permissions confirmed by live testing.
7Streaming Replication Setup and Failover13labStudents configure streaming replication between a primary and a hot-standby PostgreSQL server, verify replication lag, and perform a controlled promote-standby failover.
  1. On a two-VM lab network, configure the primary server with wal_level = replica, create a replication role, add a pg_hba.conf entry for the standby, and use pg_basebackup to create the initial standby data directory; start the standby with a postgresql.conf primary_conninfo entry and confirm replication is active via pg_stat_replication on the primary.
  2. Simulate replication lag by pausing the standby (pg_wal_replay_pause()), generating 10,000 rows of data on the primary with a provided INSERT script, then resuming replay (pg_wal_replay_resume()) and measuring catch-up time; record write_lag, flush_lag, and replay_lag from pg_stat_replication.
  3. Perform a controlled failover: stop the primary, run pg_ctl promote on the standby, verify the standby becomes read-write, then reconnect a psql client to the new primary and confirm data written before the failure is present; write a one-page failover runbook documenting each step.
Two Linux VMs on the same virtual network, PostgreSQL 16 on both, pg_basebackup, pg_stat_replication view, failover runbook template, PostgreSQL Documentation Chapter 26 (High Availability)Instructor inspects pg_stat_replication output (captured screenshot) during replication and confirms the promoted standby is writable with no data loss for committed transactions; pass = replication confirmed AND failover runbook includes all steps in correct order.
8Routine Maintenance: VACUUM, ANALYZE, pg_dump, and Monitoring12practiceStudents perform and schedule routine PostgreSQL maintenance tasks including manual and autovacuum tuning, logical backups with pg_dump, and server health monitoring using built-in views.
  1. Run VACUUM VERBOSE and VACUUM ANALYZE on a table with significant dead tuples (generated by a provided UPDATE/DELETE script); compare pg_stat_user_tables dead_tup counts before and after, then adjust autovacuum_vacuum_scale_factor and autovacuum_vacuum_cost_delay for that table using a storage-parameter ALTER TABLE statement.
  2. Use pg_dump in three formats (plain SQL, custom, directory) to back up inventory_db; restore the custom-format backup to a new database named inventory_restore using pg_restore, and verify object counts match using a provided verification query.
  3. Query pg_stat_activity, pg_stat_bgwriter, pg_stat_database, and pg_locks to produce a one-page server health report for a simulated busy server state (generated by pgbench -c 20 in a separate terminal); identify any idle-in-transaction sessions and explain how long_query_time logging would be configured to catch slow queries.
PostgreSQL 16 VM, pgbench, pg_dump/pg_restore, pg_stat_* system catalog views, health report template, PostgreSQL Documentation Chapters 24 (Routine Database Maintenance) and 25 (Backup and Restore)Instructor verifies restored database object counts match original using the verification query and reviews the health report for accurate interpretation of at least four monitoring views; pass = zero object-count discrepancy in restore AND health report correctly identifies at least three server metrics.
Assessments
AssessmentTypeWeightPass standardMethod & rubric
PostgreSQL Administration Written ExamWritten exam25%75% or higher (scored by item; partial credit not awarded)A 50-question closed-book exam covering PostgreSQL architecture, configuration parameters, SQL syntax, index types, replication concepts, role/privilege model, and routine maintenance; questions are mapped to EnterpriseDB PostgreSQL CE exam domains to provide targeted preparation. Students have 90 minutes; results are returned with a domain-by-domain breakdown so gaps can be addressed in Lesson 5 and Lesson 6 review.
Standard met · Safety · Time · Quality/finish · Documentation
Live Administration Skills DemonstrationSkills demonstration45%Instructor-scored rubric: 18 of 24 points required; no safety violation permittedIn a 45-minute proctored session, students receive a scenario card and must complete three tasks on a fresh VM: install PostgreSQL and configure pg_hba.conf to meet stated authentication requirements, create a specified schema with tables and privileges, and produce an EXPLAIN ANALYZE plan for a provided query and propose one indexing improvement with a written justification. Each task is scored on correctness (0–3), efficiency (0–3), and documentation quality (0–2).
Standard met · Safety · Time · Quality/finish · Documentation
Lab Log PortfolioLog15%All 8 lesson lab logs submitted; average score of 80% across the lab-log rubricStudents maintain a cumulative digital lab log (a shared Google Doc or Markdown file in a class Git repository) with timestamped entries for every hands-on activity, including terminal output, screenshots, configuration file excerpts, and a brief reflection on what succeeded and what required troubleshooting. The instructor scores each entry on completeness, technical accuracy, and reflection quality using a 10-point rubric.
Standard met · Safety · Time · Quality/finish · Documentation
Server-Room and Physical Safety CheckSafety audit15%100% on all critical safety items; any critical item failure requires immediate remediation and re-check before the student may continue lab workThe instructor conducts an observed safety walkthrough and brief oral check at the beginning of Lesson 1 and again at the midpoint of the course; the checklist covers correct use of ESD protection when handling server hardware, proper cable management to prevent trip hazards, correct lifting posture for equipment, and the student's ability to locate emergency power-off and first-aid resources in the lab space. Non-critical findings are recorded for coaching; critical findings (e.g., student unable to identify emergency shutoff) halt lab access until corrected.
Standard met · Safety · Time · Quality/finish · Documentation
TEC-DATA86-04 Trade course

Database Backup and Recovery

91 hr · $1,090 COMPLIMENTARY

Students learn to design, implement, test, and document backup and recovery strategies for PostgreSQL, Oracle, and SQL Server databases in physical and cloud environments. Emphasis is placed on achieving defined recovery time objectives (RTO) and recovery point objectives (RPO) through scheduled full, incremental, and differential backups, point-in-time recovery, and continuous archiving. Credential exam areas for PostgreSQL CE, Oracle DBA CA, Microsoft DP-300, and DAMA CDMP Associate are addressed throughout.

Outcomes
Course text

Students learn to design, implement, test, and document backup and recovery strategies for PostgreSQL, Oracle, and SQL Server databases in physical and cloud environments. Emphasis is placed on achieving defined recovery time objectives (RTO) and recovery point objectives (RPO) through scheduled full, incremental, and differential backups, point-in-time recovery, and continuous archiving. Credential exam areas for PostgreSQL CE, Oracle DBA CA, Microsoft DP-300, and DAMA CDMP Associate are addressed throughout.

How the course runs. 8 blocks: Backup Fundamentals: RTO, RPO, and Backup Types; PostgreSQL Logical Backups with pg_dump and pg_dumpall; PostgreSQL Physical Backups: pg_basebackup and WAL Archiving; Oracle RMAN Backups and Recovery; SQL Server Backups and Azure Backup for Azure SQL (DP-300 Focus); Backup Automation with Cron, SQL Server Agent, and Shell Scripts; Disaster Recovery Planning, Retention Policies, and Data-Center Safety; Integrated Backup and Recovery Capstone Lab: Full Scenario Test.

What competent looks like. Design a backup strategy that meets stated RTO and RPO requirements for at least two database platforms (PostgreSQL and one of Oracle or SQL Server). Execute and verify full, incremental, differential, and transaction-log backups using native tools (pg_dump, pg_basebackup, RMAN, and SQL Server backup T-SQL or Azure Backup). Perform point-in-time recovery (PITR) from archived write-ahead logs or redo logs and confirm database consistency after restore. Automate backup jobs using cron or SQL Server Agent and validate completion through job logs and checksum verification. Document a disaster-recovery plan including backup schedule, retention policy, off-site storage procedure, and tested restore runbook. Apply safe data-center work practices including proper handling of removable media, cable management, and recognition of electrical hazards in server rooms.

Lessons · 8 blocks
#LessonHrTypeObjectiveActivitiesMaterialsCheck
1Backup Fundamentals: RTO, RPO, and Backup Types10theoryStudents will define RTO, RPO, full, incremental, differential, and transaction-log backup types and match each to a realistic business scenario.
  1. Read and annotate an excerpt from the PostgreSQL documentation section on continuous archiving and the Oracle Database Backup and Recovery User's Guide introduction; identify every backup type mentioned and write a one-sentence definition for each.
  2. Given three scenario cards (e-commerce site, hospital scheduling system, small nonprofit), calculate the maximum tolerable data loss and outage duration, then recommend and justify a backup type and frequency for each.
  3. Participate in a class debate: pairs of students argue for and against incremental-forever backup strategies versus nightly full backups, citing trade-offs in restore complexity and storage cost.
PostgreSQL documentation (postgresql.org) — Chapter on Continuous Archiving; Oracle Database Backup and Recovery User's Guide (docs.oracle.com); Microsoft Learn DP-300 study path — backup and restore module; whiteboard; scenario card setFive-question written quiz on definitions and scenario matching; students must score 80% or higher to proceed.
2PostgreSQL Logical Backups with pg_dump and pg_dumpall12labStudents will use pg_dump and pg_dumpall to create plain-text and custom-format backups of a multi-schema database and restore individual objects using pg_restore.
  1. Run pg_dump with -Fc (custom format), -Ft (tar format), and plain SQL against a provided sample database; compare file sizes, inspect the content of the plain-SQL file, and record results in a lab log.
  2. Use pg_restore with --list and --use-list flags to selectively restore a single schema and a single table into a fresh database cluster; verify row counts match the source using SELECT COUNT(*).
  3. Deliberately corrupt a table by dropping it, then time and document a full restore from each backup format, noting which format restored fastest and which allowed the most granular recovery.
Lab workstations running PostgreSQL 15 or later; psql, pg_dump, pg_restore installed; sample Northwind or DVD-rental database restored; PostgreSQL documentation Chapter 26 (Backup and Restore); lab log templateInstructor reviews completed lab log showing commands, output, row-count verification, and timing data; all three backup formats must be demonstrated with correct restore; lab log scored on a provided rubric with 80% as passing.
3PostgreSQL Physical Backups: pg_basebackup and WAL Archiving14labStudents will configure WAL archiving, take a base backup with pg_basebackup, and perform a point-in-time recovery to a target timestamp using a recovery configuration file.
  1. Edit postgresql.conf to set wal_level = replica, archive_mode = on, and archive_command pointing to a local archive directory; reload the server and confirm the first WAL segment is copied by inspecting the archive directory.
  2. Run pg_basebackup -Ft -z -P -Xs to stream and compress a base backup; record the backup start LSN from the backup_label file and simulate ongoing transactions by inserting rows into a test table every 30 seconds using a provided shell loop.
  3. Stop the server, remove the data directory, restore from the base backup, write a recovery signal file and postgresql.conf recovery_target_time set to a specific timestamp between two known insert batches, start the server, and verify only the expected rows are present.
Lab workstations running PostgreSQL 15 or later; bash shell; pg_basebackup; postgresql.conf and pg_hba.conf; PostgreSQL documentation on WAL archiving and PITR (Sections 26.3–26.4); lab log templateStudent demonstrates a live PITR to an instructor-specified timestamp in under 10 minutes during a lab check; recovered row count must exactly match expected value; 100% of required steps must appear in lab log.
4Oracle RMAN Backups and Recovery12demoStudents will execute RMAN full and incremental backup scripts, register the database in a recovery catalog, and restore a datafile to recover from a simulated media failure.
  1. Watch and annotate an instructor-led demonstration of connecting RMAN to a target database, running BACKUP DATABASE PLUS ARCHIVELOG, and verifying the backup with LIST BACKUP SUMMARY; then reproduce the same sequence independently on a lab instance.
  2. Write and run an RMAN incremental level 0 backup script followed the next day by a level 1 cumulative backup; use REPORT SCHEMA and CROSSCHECK BACKUP to confirm backup validity and document the output.
  3. Simulate a datafile media failure by taking a datafile offline and removing it from the OS; use RMAN to RESTORE DATAFILE and RECOVER DATAFILE, then bring it online and open the database; record every RMAN command and its output in the lab log.
Oracle Database Express Edition (XE) or Oracle Database 19c lab instance; RMAN command-line client; Oracle Database Backup and Recovery User's Guide (docs.oracle.com); lab log template; instructor-prepared demo scriptInstructor evaluates lab log for correct RMAN command syntax, successful backup verification output, and demonstrated datafile restore; student must complete the restore exercise independently with a passing rubric score of 80%.
5SQL Server Backups and Azure Backup for Azure SQL (DP-300 Focus)12labStudents will perform full, differential, and transaction-log backups of a SQL Server database using T-SQL and configure automated backups for an Azure SQL Database, mapping each task to the DP-300 exam objective area.
  1. Use T-SQL BACKUP DATABASE and BACKUP LOG statements to create a full backup, then a differential backup, then a transaction-log backup; store each to a named backup device and verify with RESTORE VERIFYONLY; annotate each statement with the corresponding DP-300 exam topic.
  2. Restore the database to a point in time using RESTORE DATABASE WITH STOPAT and a transaction-log backup; confirm through a SELECT query that data inserted after the target time is absent.
  3. In the Azure portal or using Azure CLI, review the automated backup settings for a provided Azure SQL Database (backup frequency, short-term retention, long-term retention options); document findings in a comparison table alongside on-premises SQL Server backup options.
SQL Server Express or Developer Edition on lab workstation; SQL Server Management Studio (SSMS) or Azure Data Studio; Azure free-tier or student subscription; Microsoft Learn DP-300 study path; T-SQL reference (learn.microsoft.com); lab log templateLab log reviewed by instructor for correct T-SQL syntax, VERIFYONLY confirmation, successful PITR restore, and the Azure comparison table; 80% rubric score required.
6Backup Automation with Cron, SQL Server Agent, and Shell Scripts10practiceStudents will write and schedule automated backup scripts using cron for PostgreSQL and Linux-based Oracle, and SQL Server Agent jobs for SQL Server, including logging and email-alert placeholders.
  1. Write a bash script that calls pg_dump with a timestamped filename, checks the exit code, writes a success or failure message to a log file, and deletes backup files older than a configurable retention period using find -mtime; schedule it with crontab -e and verify it runs at the correct time.
  2. Create a SQL Server Agent job with three steps: full backup on Sunday, differential backup Monday–Saturday, and transaction-log backup every 15 minutes; configure a job history and review the job activity monitor after two scheduled runs.
  3. Peer-review a classmate's backup script against a provided checklist covering: timestamped filenames, exit-code checking, log writing, retention cleanup, and commented code; give written feedback and revise your own script based on feedback received.
Linux lab workstation with cron; PostgreSQL 15+; SQL Server Developer Edition with SQL Server Agent enabled; bash reference; Microsoft SQL Server Agent documentation; peer-review checklistInstructor runs each student's cron job live, inspects the resulting log file, and confirms old-file deletion works; SQL Server Agent job history must show at least one successful run; 80% on peer-review checklist required.
7Disaster Recovery Planning, Retention Policies, and Data-Center Safety12theoryStudents will draft a written disaster-recovery plan that includes a backup schedule, retention policy, off-site or cloud storage procedure, restore runbook, and server-room safety practices aligned with OSHA general industry standards.
  1. Using a provided DR plan template, students complete all sections for an assigned scenario database: backup schedule table, retention policy (daily/weekly/monthly/annual), off-site transfer method (cloud bucket or tape rotation), and a step-by-step restore runbook with estimated restore times.
  2. Identify server-room physical hazards (electrical panel access, cable trip hazards, raised-floor removal, heavy rack components) and match each to the appropriate OSHA general industry control (administrative, engineering, or PPE); complete a hazard-identification worksheet.
  3. Tabletop exercise: instructor announces a simulated disaster (ransomware encrypted the primary server at 2:00 a.m.); student teams walk through their runbook aloud, identify gaps, and revise the plan; a second team critiques each plan for completeness and realistic timing.
DR plan template (instructor-prepared); OSHA General Industry standards overview; DAMA DMBOK2 Chapter on Data Storage and Operations; scenario descriptions; hazard-identification worksheetCompleted DR plan scored on instructor rubric (schedule completeness, retention logic, runbook step-by-step clarity, safety section accuracy); 80% required; safety worksheet must be 100% complete.
8Integrated Backup and Recovery Capstone Lab: Full Scenario Test9labStudents will independently design and execute a complete backup-and-recovery cycle for a multi-platform environment (PostgreSQL and one additional platform), verify all restores, and present a documented restore runbook.
  1. Receive an instructor-assigned scenario packet specifying the database platform mix, RTO, RPO, and a simulated failure type (dropped table, corrupted datafile, or deleted transaction logs); plan and document the backup approach before touching the keyboard.
  2. Execute the backup strategy, introduce the assigned failure, and perform the recovery independently within the time limit specified in the scenario packet; document every command and decision in a structured incident log.
  3. Present the completed incident log and restore runbook to the instructor and two peers in a 10-minute debrief; answer three instructor questions about why specific recovery choices were made and what would change if the RTO were halved.
Lab workstation with PostgreSQL 15+ and one of Oracle XE or SQL Server Developer; all tools from previous lessons; incident log template; restore runbook template; scenario packet (instructor-prepared)Instructor evaluates whether recovery meets the scenario's stated RTO and RPO, whether all commands are correctly documented, and whether the student can explain decisions under questioning; 80% on combined rubric (execution 60%, documentation 25%, debrief 15%) is required to pass.
Assessments
AssessmentTypeWeightPass standardMethod & rubric
Backup and Recovery Knowledge ExamWritten exam25%80% correct (32 of 40 questions)A 40-question written exam covering backup type definitions, RTO/RPO concepts, PITR theory, RMAN terminology, SQL Server backup syntax, WAL archiving configuration, retention policy design, and data-center safety rules; questions are drawn from PostgreSQL CE, Oracle DBA CA, DP-300, and DAMA CDMP Associate exam domains. Students have 60 minutes and may not use notes or references.
Standard met · Safety · Time · Quality/finish · Documentation
Live Recovery Skills DemonstrationSkills demonstration45%Instructor rubric score of 80% or higher; recovery must succeed within the stated RTOThe instructor assigns a previously unseen failure scenario (platform and failure type disclosed at the start); the student has 90 minutes to recover the database to a verified consistent state, narrating decisions aloud. The rubric evaluates correct tool selection, command accuracy, verification steps, and ability to explain recovery choices.
Standard met · Safety · Time · Quality/finish · Documentation
Cumulative Lab Log PortfolioLog15%80% average score across all lab log rubrics; no individual lesson lab log may score below 70%Students submit a compiled portfolio of all lab logs from Lessons 2 through 8; each log must include the objective, all commands used with output, row-count or checksum verification, timing data, and a reflection on what would be done differently; the portfolio demonstrates documented, reproducible practice aligned with DAMA data operations and PostgreSQL CE exam expectations.
Standard met · Safety · Time · Quality/finish · Documentation
Server-Room Safety Walkthrough CheckSafety audit15%100% of critical safety items marked satisfactory; any critical item failed requires immediate remediation and re-checkUsing a provided checklist derived from OSHA General Industry standards, the instructor observes each student conducting a simulated server-room safety inspection: the student must correctly identify electrical hazard controls, cable management issues, proper lifting technique for rack equipment, and emergency shutdown location; all critical items must be marked satisfactory with no unsatisfactory ratings allowed on a final submission.
Standard met · Safety · Time · Quality/finish · Documentation
TEC-DATA86-05 Trade course

Database Security & Role Management

91 hr · $1,090 COMPLIMENTARY

Learners implement defense-in-depth security for relational database systems, covering authentication, authorization, role-based access control (RBAC), auditing, encryption, and regulatory compliance requirements. Hands-on labs use PostgreSQL and align with Oracle and Microsoft DP-300 security domain objectives. This course prepares learners to harden production databases against internal and external threats while maintaining auditable access controls.

Outcomes
Course text

Learners implement defense-in-depth security for relational database systems, covering authentication, authorization, role-based access control (RBAC), auditing, encryption, and regulatory compliance requirements. Hands-on labs use PostgreSQL and align with Oracle and Microsoft DP-300 security domain objectives. This course prepares learners to harden production databases against internal and external threats while maintaining auditable access controls.

How the course runs. 8 blocks: Database Threat Landscape & Physical/Environmental Safety; Authentication: pg_hba.conf, Password Policies & Scram-SHA-256; Role-Based Access Control: Privileges, Roles & Least Privilege; SSL/TLS Encryption in Transit & Certificate Management; Encryption at Rest: TDE Concepts, pgcrypto & Column Encryption; Auditing: pg_audit, Log Analysis & Incident Reporting; Regulatory Compliance: Data Security Policy & DAMA CDMP Alignment; Integrated Security Lab: Harden a Production-Like Database.

What competent looks like. Configure authentication methods (password, md5, scram-sha-256, peer, and certificate-based) in PostgreSQL pg_hba.conf and equivalent Oracle/SQL Server mechanisms. Design and implement a role hierarchy using least-privilege principles, granting and revoking object-level privileges for users, roles, and groups in PostgreSQL, Oracle, and Azure SQL. Enable and query database audit logs to detect unauthorized access attempts and produce a written incident summary. Apply transparent data encryption (TDE) and column-level encryption concepts, and configure SSL/TLS connections to a database server. Map organizational data-access policies to technical controls and document compliance with a data governance framework (DAMA CDMP Associate domain: Data Security). Apply physical and environmental safety practices when working in server rooms, including lockout/tagout awareness and proper handling of powered networking equipment.

Lessons · 8 blocks
#LessonHrTypeObjectiveActivitiesMaterialsCheck
1Database Threat Landscape & Physical/Environmental Safety9theoryLearners identify the most common database attack vectors, classify data sensitivity levels, and describe physical safety procedures required in data center environments.
  1. Read and annotate the OSHA Electrical Safety general industry standard guidance and a CIS Benchmark executive summary; learners list five physical hazards found in server rooms (live cables, rack stability, airflow hazards, emergency power-off locations, slip risks) and write a two-paragraph safety plan.
  2. Group discussion: map the STRIDE threat model (Spoofing, Tampering, Repudiation, Information Disclosure, Denial of Service, Elevation of Privilege) to realistic database scenarios; each group presents one scenario with a recommended control.
  3. Individual worksheet: classify ten sample data fields (SSN, first name, salary, product SKU, credit card number, etc.) by sensitivity tier using a provided data classification rubric aligned with DAMA CDMP data-security concepts.
OSHA electrical safety guidance (osha.gov), CIS PostgreSQL Benchmark (cisecurity.org), DAMA DMBOK2 Chapter 7 excerpt (Data Security), whiteboard, printed STRIDE worksheetLearner correctly classifies at least 8 of 10 data fields and identifies all five physical hazards on the safety worksheet; instructor reviews and initials each sheet before the next lesson.
2Authentication: pg_hba.conf, Password Policies & Scram-SHA-25612labLearners configure PostgreSQL client authentication using multiple methods (trust, md5, scram-sha-256, peer) by editing pg_hba.conf and verify that only authorized connections succeed.
  1. Instructor demo: show a default pg_hba.conf, explain record format (type, database, user, address, method), then learners edit a practice file to allow scram-sha-256 for a named application user and reject all others; reload PostgreSQL with pg_ctlcluster and test with psql.
  2. Lab exercise: create three database users with different authentication requirements (local peer for a DBA, scram-sha-256 over TCP for an app account, and a deliberately rejected remote login); use \\conninfo and pg_hba_file_rules view to verify configuration.
  3. Compare and contrast activity: learners read the Oracle Database Security Guide section on password profiles and the Microsoft DP-300 study guide section on Azure SQL authentication (Entra ID vs. SQL auth); fill in a three-column comparison table (PostgreSQL / Oracle / Azure SQL) for each authentication concept.
PostgreSQL 16 documentation (postgresql.org/docs), Oracle Database Security Guide (docs.oracle.com), Microsoft DP-300 Study Guide, Linux VMs with PostgreSQL 16 installed (one per learner or pair), pg_hba.conf template handoutLearner demonstrates a working pg_hba.conf where: (1) a local DBA connects via peer, (2) an app user connects via scram-sha-256, and (3) an anonymous remote connection is refused; all three outcomes verified by instructor observation. Pass = all three verified correctly.
3Role-Based Access Control: Privileges, Roles & Least Privilege14labLearners design and implement a multi-tier RBAC schema in PostgreSQL using CREATE ROLE, GRANT, REVOKE, and row-level security (RLS) to enforce least-privilege access for at least three organizational roles.
  1. Design activity: given a scenario (a hospital records database with roles: data_entry_clerk, nurse_supervisor, auditor, dba_admin), learners draw an entity-relationship-style privilege diagram showing which role inherits from which and which objects each role can SELECT/INSERT/UPDATE/DELETE.
  2. Hands-on lab: learners implement their design in PostgreSQL — create a sample schema with three tables, create the four roles, grant appropriate privileges, enable RLS on the patient table so nurses see only their ward's rows, and test by switching session role with SET ROLE.
  3. Peer review: pairs swap scripts and attempt to perform an unauthorized action (e.g., a data_entry_clerk deleting a record); they document the error message returned and write a one-paragraph explanation of why it confirms the policy is enforced.
PostgreSQL 16 documentation (GRANT, CREATE ROLE, Row Security Policies chapters), sample hospital schema SQL script (provided), Linux VMs, psql clientInstructor-run test script performs five privilege checks against the learner's database; learner must block all three unauthorized operations and permit all two authorized ones. Pass = 5 of 5 checks correct.
4SSL/TLS Encryption in Transit & Certificate Management10demoLearners configure PostgreSQL to require SSL connections using a self-signed certificate, verify encryption is active, and explain the role of certificates in client authentication.
  1. Instructor-led demo: generate a self-signed CA and server certificate using OpenSSL; copy server.crt and server.key to the PostgreSQL data directory with correct file permissions (0600 owned by postgres); set ssl = on in postgresql.conf and reload; show psql connecting with sslmode=require.
  2. Guided practice: learners replicate the demo on their own VM, then use the psql \\conninfo command and openssl s_client to confirm the TLS handshake succeeds; they also deliberately set sslmode=disable and confirm the connection is refused when pg_hba.conf requires hostssl.
  3. Short research and discussion: learners read the DP-300 objective on Azure SQL transparent data encryption (TDE) and compare it to the in-transit encryption just configured — they write three bullet points distinguishing encryption in transit from encryption at rest.
OpenSSL command-line tool, PostgreSQL 16 SSL documentation, Microsoft DP-300 TDE reference material, Linux VMs, instructor demo slide deckLearner produces a terminal screenshot showing sslmode=require in \conninfo and a failed unencrypted connection attempt; instructor verifies outputs. Pass = both conditions demonstrated.
5Encryption at Rest: TDE Concepts, pgcrypto & Column Encryption10labLearners apply column-level encryption to sensitive fields in PostgreSQL using the pgcrypto extension and describe how Oracle TDE and Azure SQL TDE protect data files at rest.
  1. Lab setup: learners install the pgcrypto extension, create an employees table with an encrypted ssn column, and write INSERT and SELECT statements using pgp_sym_encrypt and pgp_sym_decrypt with a passphrase; they confirm that a raw table scan (pg_filedump or strings on the data file) does not reveal plaintext SSN values.
  2. Concept mapping: learners complete a diagram worksheet mapping the pgcrypto approach (application-level) vs. Oracle TDE tablespace encryption vs. Azure SQL service-managed TDE, identifying where the encryption boundary lies in each case and who holds the key.
  3. Written scenario response: given a breach scenario where a hard drive is stolen from a server, learners write a paragraph explaining which encrypted columns or TDE configurations would protect the data and why, referencing their diagram.
PostgreSQL pgcrypto documentation, Oracle TDE documentation excerpt (docs.oracle.com), Microsoft DP-300 study guide (encryption at rest section), Linux VMs, pgcrypto extension, sample schema SQLLearner runs instructor-provided SELECT against their table; pgp_sym_decrypt must return the original SSN for authorized query and raw file inspection must show ciphertext only. Pass = both conditions met plus correct written scenario response (instructor rubric: 3 of 3 key points addressed).
6Auditing: pg_audit, Log Analysis & Incident Reporting12labLearners enable session and object auditing using the pgaudit extension, reproduce a simulated unauthorized access attempt, query audit logs, and write a structured incident summary report.
  1. Lab: install and configure the pgaudit extension; set pgaudit.log = 'role, ddl, write' in postgresql.conf; create an audit_test user, run a series of authorized and unauthorized SQL commands as that user, then query the PostgreSQL log file to locate and extract the audit records for those commands.
  2. Log-analysis exercise: instructor provides a sanitized 200-line PostgreSQL log excerpt containing embedded simulated attack patterns (repeated failed logins, privilege escalation attempt, unusual after-hours SELECT on sensitive table); learners highlight events of interest, classify each by STRIDE category, and rank by severity.
  3. Incident report writing: learners compose a one-page structured incident summary using a provided template (date/time, affected objects, account involved, evidence from log, recommended remediation); peer-reviewed before submission.
pgaudit extension and documentation (github.com/pgaudit/pgaudit), PostgreSQL 16 logging documentation, sample log file (provided), incident report template, word processorLearner submits log excerpt with all simulated attack events highlighted and correctly classified (pass = 4 of 5 events identified) plus incident report scored by instructor rubric requiring correct evidence citation, severity classification, and at least two actionable remediation steps.
7Regulatory Compliance: Data Security Policy & DAMA CDMP Alignment12theoryLearners connect database security controls implemented in previous lessons to regulatory frameworks (HIPAA, PCI-DSS, SOC 2 at a general level) and to the DAMA CDMP Data Security knowledge area, producing a security-policy document for a sample organization.
  1. Case study reading and annotation: learners read a two-page fictional organizational security policy (provided) and annotate each control with the corresponding PostgreSQL technical mechanism (e.g., 'all PII must be encrypted at rest' → pgcrypto or TDE) and the DAMA CDMP activity it satisfies.
  2. Policy writing workshop: in pairs, learners draft a one-page Database Security Policy for a fictitious retail company that must meet PCI-DSS general requirements for cardholder data (no specific code sections required — focus on concepts: access control, encryption, audit logs, separation of duties); instructor circulates and provides feedback.
  3. Class discussion: learners present one policy decision they made, the technical control that enforces it, and how an auditor would verify compliance; instructor provides corrections and reinforcement.
DAMA DMBOK2 Chapter 7 (Data Security) summary handout, sample organizational security policy (provided), PCI-DSS requirement summary (pcisecuritystandards.org), HIPAA security rule overview (hhs.gov), word processorPolicy document scored by instructor rubric: must address access control, encryption at rest and in transit, audit logging, and separation of duties with at least one specific PostgreSQL mechanism named for each; pass = all four areas addressed with correct mechanisms.
8Integrated Security Lab: Harden a Production-Like Database12labLearners independently apply all course security controls — authentication, RBAC, SSL, encryption, and auditing — to a preconfigured insecure PostgreSQL instance, producing a hardened database and a completed CIS Benchmark checklist.
  1. Learners receive an intentionally misconfigured PostgreSQL VM (trust authentication for all, no SSL, no audit logging, overprivileged roles, plaintext sensitive column) and a CIS PostgreSQL Benchmark checklist; they work through each checklist item, applying the fix and documenting the before/after configuration change.
  2. Penetration simulation: instructor (or a designated peer) attempts five scripted attacks against the hardened instance (unauthenticated remote connection, SQL injection probe on a test endpoint, direct file read of pg_hba.conf as a low-privilege OS user, privilege escalation via SET ROLE, unencrypted connection attempt); learner must show that all five are blocked or logged.
  3. Learner writes a two-page Hardening Summary Report listing each change made, the CIS checklist item it satisfies, and evidence (command output or log snippet) confirming the control is active.
Linux VM with intentionally misconfigured PostgreSQL 16 (provided by instructor), CIS PostgreSQL Benchmark (cisecurity.org), pgaudit, OpenSSL, pgcrypto, Hardening Summary Report templateAll five penetration simulation attacks must be blocked or captured in audit log (pass = 5 of 5); CIS checklist must have at least 90% of applicable items checked with evidence; Hardening Summary Report must reference each major control implemented. Instructor signs off checklist.
Assessments
AssessmentTypeWeightPass standardMethod & rubric
Security Concepts Knowledge ExamWritten exam25%75% or higher (38 of 50 points)A 50-question written exam covering database threat models, authentication methods, privilege types, encryption concepts (in transit and at rest), audit logging purposes, and regulatory compliance frameworks aligned to PostgreSQL CE, Oracle DBA CA, Microsoft DP-300 security domain, and DAMA CDMP Data Security knowledge area. Questions include multiple choice, matching, and short answer; learners have 90 minutes.
Standard met · Safety · Time · Quality/finish · Documentation
Role & Security Configuration Skills DemonstrationSkills demonstration45%Instructor checklist: all 6 required items demonstrated correctly within 45 minutesLearner receives a blank PostgreSQL 16 instance and a written scenario (fictional company with three roles and two sensitive tables); they must configure scram-sha-256 authentication, create the required role hierarchy with correct GRANT statements, enable SSL, implement one pgcrypto encrypted column, enable pgaudit, and demonstrate that an unauthorized role cannot access a restricted table — all observed and checked off by the instructor in real time.
Standard met · Safety · Time · Quality/finish · Documentation
Lab Log PortfolioLog15%At least 6 of 8 lab entries complete with correct outputs and written reflections; no missing safety entriesLearners maintain a running lab log (digital document) for all eight lessons, recording commands used, outputs observed, errors encountered and resolved, and a two-to-three sentence reflection on how each control addresses a specific threat; the safety entries from Lesson 1 must be present and complete for the portfolio to be eligible for a passing score.
Standard met · Safety · Time · Quality/finish · Documentation
Physical & Environmental Safety CheckSafety audit15%100% on all safety-critical items (no partial credit for safety items); overall checklist pass = 8 of 10 itemsInstructor-observed walkthrough in the lab server room or simulated data-center space: learner must correctly identify emergency power-off location, demonstrate proper cable management, describe lockout/tagout applicability before touching powered network equipment, identify at least two slip/trip hazards, and explain what PPE (safety glasses, ESD wrist strap) is required and when; any missed safety-critical item (lockout/tagout, emergency shutoff) requires immediate remediation before the learner may continue lab work.
Standard met · Safety · Time · Quality/finish · Documentation
TEC-DATA86-06 Trade course

ETL Pipelines: Extract, Transform, and Load for Database Administration

91 hr · $1,090 COMPLIMENTARY

Students design, build, and operate ETL pipelines that move data reliably between source systems and relational databases, with emphasis on PostgreSQL and cloud-compatible workflows. Topics cover extraction from flat files, APIs, and relational sources; transformation logic including cleaning, type casting, and business-rule application; and load strategies including truncate-reload, upsert, and incremental patterns. Students connect ETL practice to data governance, quality, and the credential exam areas covered by DAMA CDMP, Oracle DBA CA, and Microsoft DP-300.

Outcomes
Course text

Students design, build, and operate ETL pipelines that move data reliably between source systems and relational databases, with emphasis on PostgreSQL and cloud-compatible workflows. Topics cover extraction from flat files, APIs, and relational sources; transformation logic including cleaning, type casting, and business-rule application; and load strategies including truncate-reload, upsert, and incremental patterns. Students connect ETL practice to data governance, quality, and the credential exam areas covered by DAMA CDMP, Oracle DBA CA, and Microsoft DP-300.

How the course runs. 8 blocks: ETL Concepts, Architecture, and Trade Vocabulary; Extracting Data from Flat Files and Databases; Transformation Logic: Cleaning, Casting, and Business Rules; Load Strategies: Truncate-Reload, Upsert, and Incremental Load; Error Handling, Logging, and Pipeline Restart; Pipeline Orchestration with a Scheduler; ETL Security, Data Privacy, and Governance Alignment; End-to-End Pipeline Build and Peer Review.

What competent looks like. Design a multi-stage ETL pipeline architecture that identifies data sources, transformation rules, and target load strategy from a written specification. Extract data from CSV flat files, JSON REST APIs, and a PostgreSQL source database using Python scripts and command-line tools with zero data loss. Apply transformation logic — including deduplication, null handling, data-type conversion, and business-rule validation — to produce a clean staging dataset that meets a defined acceptance threshold. Execute truncate-reload, upsert (INSERT … ON CONFLICT), and date-range incremental load patterns against a PostgreSQL target database and verify row counts and checksums. Implement error logging, row-level rejection, and pipeline restart capability so that a failed run can be diagnosed and resumed without duplicating or losing records. Evaluate a peer's pipeline design against data-quality and security criteria drawn from DAMA CDMP and Microsoft DP-300 exam objectives and produce a written review.

Lessons · 8 blocks
#LessonHrTypeObjectiveActivitiesMaterialsCheck
1ETL Concepts, Architecture, and Trade Vocabulary7theoryStudents will explain the three ETL stages, distinguish ETL from ELT, and map pipeline components to real database administration tasks.
  1. Read and annotate an industry pipeline architecture diagram; label each component as extract, transform, or load and write a one-sentence purpose for each.
  2. Compare three real-world ETL tool categories — hand-coded scripts, open-source orchestrators, and cloud-managed services — by completing a feature matrix table.
  3. Participate in a guided discussion on how DAMA CDMP data-integration knowledge areas and Microsoft DP-300 'implement a data storage solution' objective relate to ETL design choices.
Whiteboard, ETL architecture poster, DAMA DMBOK2 Chapter 8 excerpt (data integration and interoperability), Microsoft DP-300 exam skills outline (official Microsoft Learn), instructor-prepared slide deck10-question written quiz on ETL vocabulary, stage order, and ETL-vs-ELT distinctions; pass = 70% or higher
2Extracting Data from Flat Files and Databases11labStudents will write Python scripts using the csv and psycopg2 modules to extract data from CSV files and a PostgreSQL source database into a local staging area with verified row counts.
  1. Use the csv.DictReader class to extract a 10,000-row CSV sales file, print a row count, and write the raw rows to a new staging CSV; compare input and output row counts to confirm completeness.
  2. Connect to an instructor-provisioned PostgreSQL source database with psycopg2, execute a SELECT query against two joined tables, fetch all results, and write them to a JSON-lines staging file.
  3. Call a public JSON REST API endpoint (instructor-specified, returning sample employee or product data) using the Python requests library, parse the response, and append records to the same staging area, logging the HTTP status code and record count.
Student laptops, Python 3 (standard library + pip), psycopg2 library, requests library, PostgreSQL 15 source database (instructor VM), sample CSV and API endpoint provided by instructor, PostgreSQL documentation (postgresql.org)Lab submission: working Python scripts plus a plain-text log showing correct row counts for all three sources; pass = scripts execute without unhandled exceptions and all row counts match instructor answer key within 0 rows
3Transformation Logic: Cleaning, Casting, and Business Rules12.5labStudents will apply a set of specified transformation rules — null substitution, data-type casting, deduplication, and a business-rule filter — to a staging dataset and produce a clean output file that passes automated validation.
  1. Receive a dirty staging CSV containing nulls, mixed date formats, duplicate primary keys, and out-of-range numeric values; write a Python transformation script that applies each rule and logs every rejected row to a separate error file with a reason code.
  2. Use pandas (or plain Python dicts, instructor's choice by lab cohort) to cast columns to correct data types, standardize all dates to ISO 8601 (YYYY-MM-DD), and substitute a configured default value for nulls in required fields.
  3. Run the instructor-provided validation script against the clean output file and iterate on the transformation script until the validation script reports zero schema violations and a rejection rate at or below the instructor-specified threshold.
Student laptops, Python 3, pandas library, instructor-prepared dirty CSV dataset, instructor-provided validation Python script, data dictionary specifying target schema and business rules, DAMA DMBOK2 Chapter 13 excerpt (data quality)Clean output file passes the instructor validation script with zero schema errors and a row-rejection rate at or below 5%; error log correctly documents every rejected row with a reason code; pass = both criteria met
4Load Strategies: Truncate-Reload, Upsert, and Incremental Load12.5labStudents will implement three distinct load patterns against a PostgreSQL target database and verify data integrity using row counts, checksums, and a duplicate-check query after each load.
  1. Implement a truncate-reload load for a daily-snapshot dimension table: TRUNCATE the target table inside a transaction, COPY the clean file in, verify row count, and COMMIT; then intentionally rerun and confirm idempotent behavior.
  2. Implement an upsert load using INSERT … ON CONFLICT (target_pk) DO UPDATE SET … for a customer master table; load an initial batch, then load a delta batch containing new rows and changed rows, and query the table to confirm updated values and no duplicates.
  3. Implement a date-range incremental load for a large fact table: query the target for the MAX load date, extract only source rows with a record_date greater than that value, and append them; validate with a COUNT and a SUM checksum against the source.
Student laptops, PostgreSQL 15 target database (student schema on instructor VM), psycopg2, instructor-prepared clean staging files for each pattern, PostgreSQL COPY documentation, DP-300 study guide section on data loading patternsPost-load SQL queries (provided by instructor) return row counts and checksums that match expected values for all three patterns; pass = all three patterns pass with zero discrepancy
5Error Handling, Logging, and Pipeline Restart11practiceStudents will add structured error handling and a checkpoint restart mechanism to an existing ETL script so that a simulated mid-run failure can be diagnosed and the pipeline restarted without data duplication or loss.
  1. Instrument an existing ETL script with Python's logging module at INFO and ERROR levels: log pipeline start time, row counts after each stage, any row-level rejection, and pipeline end time to a dated log file.
  2. Add a try/except block around the load stage that catches psycopg2.DatabaseError, rolls back the transaction, writes the error message and last successfully processed batch ID to a checkpoint file, and exits with a non-zero return code.
  3. Simulate a failure by having the instructor kill the database connection mid-load; then modify the pipeline startup logic to read the checkpoint file and resume from the last committed batch; run the full pipeline again and confirm final row count is correct with no duplicates.
Student laptops, Python 3 logging module, psycopg2, PostgreSQL 15, instructor-prepared base ETL script (intentionally missing error handling), checkpoint file template, pipeline run log templateDemonstration to instructor: student triggers the simulated failure, shows the checkpoint file contents, restarts the pipeline, and queries the database to prove correct final row count and no duplicates; pass = correct final count with no duplicates confirmed by instructor query
6Pipeline Orchestration with a Scheduler9demoStudents will schedule an end-to-end ETL pipeline using cron (Linux) or Task Scheduler (Windows) and confirm that the pipeline runs unattended at a specified interval and sends an email-style notification on success or failure.
  1. Instructor demonstrates configuring a cron job on a Linux VM to run an ETL Python script nightly; students replicate the configuration and verify the cron entry with crontab -l.
  2. Extend the ETL script to send a completion notification by writing a summary record (status, row count, run timestamp) to a notifications table in PostgreSQL, simulating the pattern used by commercial orchestrators.
  3. Review the orchestration screen of an open-source tool (Apache Airflow or similar) via a live instructor demo: identify DAG structure, task dependencies, retry settings, and logging output; map these features to the manual patterns built in earlier lessons.
Linux VM with cron, PostgreSQL 15, Python 3, instructor-prepared Airflow demo environment (read-only access), Airflow documentation (airflow.apache.org), cron syntax referenceStudent shows a cron job entry, a test run log file, and a populated notifications table row; instructor verifies the scheduled run executed correctly; pass = all three artifacts present and correct
7ETL Security, Data Privacy, and Governance Alignment10theoryStudents will identify at least four security and privacy risks in ETL pipelines and map each risk to a control drawn from PostgreSQL role-based access, connection encryption, and DAMA CDMP data governance principles.
  1. Analyze an instructor-prepared case study of a pipeline that stores database credentials in plain-text script files; identify the vulnerabilities, then rewrite the credential-handling section to use environment variables or a config file outside the source tree.
  2. Review PostgreSQL's ssl connection parameter and pg_hba.conf role-based entries; configure a test pipeline connection to require SSL and a named application role with SELECT-only privileges on source tables.
  3. Map four pipeline risks (credential exposure, unencrypted transport, excessive privilege, no audit trail) to DAMA CDMP governance controls and Microsoft DP-300 'implement database security' objectives; complete a risk-control matrix worksheet and discuss in pairs.
Student laptops, PostgreSQL 15 with SSL configured on instructor VM, pg_hba.conf documentation, DAMA DMBOK2 Chapter 11 excerpt (data security), Microsoft DP-300 skills outline, instructor-prepared case study and risk-control matrix worksheetCompleted risk-control matrix with at least four risks each mapped to a specific PostgreSQL or governance control; instructor reviews for accuracy; pass = all four risks correctly mapped with no invented controls
8End-to-End Pipeline Build and Peer Review18labStudents will independently build a complete, documented ETL pipeline from a new data source to a PostgreSQL target database and conduct a structured peer review using a rubric drawn from DAMA CDMP and DP-300 exam criteria.
  1. Receive a new pipeline specification from the instructor (a different source schema, transformation rules, and target table from earlier labs); design the pipeline in a one-page architecture diagram, then code and test the full extract, transform, and load in sequence.
  2. Write pipeline documentation including: data source description, transformation rule table, load strategy chosen and rationale, error handling approach, and a run log from a successful test execution; submit code and documentation together.
  3. Exchange code and documentation with a peer; complete the instructor-provided peer-review rubric covering correctness, error handling, security practice, and documentation quality; write a one-page written review and discuss findings with the peer before submitting both documents.
Student laptops, Python 3, psycopg2, PostgreSQL 15, instructor-prepared pipeline specification, peer-review rubric (maps to DAMA CDMP data integration and DP-300 objectives), architecture diagram templateInstructor evaluates pipeline code (runs correctly against instructor test data), documentation (all required sections present and accurate), and peer-review (substantive and rubric-criteria-based); pass = pipeline produces correct output on instructor test data AND documentation and peer-review both scored as satisfactory by instructor
Assessments
AssessmentTypeWeightPass standardMethod & rubric
ETL Concepts and Design Knowledge ExamWritten exam25%70% or higher (28 of 40 points)A 40-question written exam covering ETL architecture, stage definitions, load pattern selection, error-handling strategies, and the mapping of ETL controls to DAMA CDMP data integration and Microsoft DP-300 exam objectives. Questions include multiple choice, matching, and short written responses requiring students to justify a design choice.
Standard met · Safety · Time · Quality/finish · Documentation
Pipeline Build Skills DemonstrationSkills demonstration45%Instructor marks all four checkpoints as Pass; any Fail checkpoint requires a single remediation attempt within one weekThe student receives an unseen pipeline specification and has a timed session to produce a working Python ETL script; the instructor evaluates four checkpoints live: successful extraction with correct row count, clean transformation output with error log, correct load verified by SQL query, and presence of structured logging and error handling.
Standard met · Safety · Time · Quality/finish · Documentation
Lab Notebook and Run Log PortfolioLog15%At least 6 of 8 lessons' lab logs submitted and scored satisfactory; any missing or unsatisfactory log must be corrected and resubmittedStudents maintain a running lab log documenting each lab session: the task objective, commands and code snippets used, observed outputs and row counts, errors encountered and how they were resolved, and a reflection sentence connecting the lab to a credential exam objective. The portfolio is reviewed at course midpoint and again at course end.
Standard met · Safety · Time · Quality/finish · Documentation
ETL Security and Workplace Safety CheckSafety audit15%All mandatory items marked Pass; a single Fail on any mandatory item requires immediate correction before the student may continue unsupervised lab workInstructor uses a checklist to verify that the student's pipeline never stores credentials in plain-text code, uses an SSL-required connection to PostgreSQL, applies a least-privilege database role, and logs errors without writing sensitive data values to the log file; the checklist also confirms the student can locate the lab emergency procedures and identify the correct response to an electrical hazard at a workstation (OSHA general industry electrical safety, consistent with OSHA 10 training from Course 1).
Standard met · Safety · Time · Quality/finish · Documentation
TEC-DATA86-07 Trade course

Data Governance & Quality

91 hr · $1,090 COMPLIMENTARY

Students learn to design and operate data governance frameworks, define data stewardship roles, and apply data-quality techniques including profiling, cleansing, and monitoring within relational and cloud environments. The course maps directly to the DAMA CDMP Associate exam domains and supports the data-management competencies tested in Oracle DBA CA and Microsoft DP-300. Learners leave able to implement governance policies, measure data quality, and document lineage and metadata in a production-like PostgreSQL or Azure SQL environment.

Outcomes
Course text

Students learn to design and operate data governance frameworks, define data stewardship roles, and apply data-quality techniques including profiling, cleansing, and monitoring within relational and cloud environments. The course maps directly to the DAMA CDMP Associate exam domains and supports the data-management competencies tested in Oracle DBA CA and Microsoft DP-300. Learners leave able to implement governance policies, measure data quality, and document lineage and metadata in a production-like PostgreSQL or Azure SQL environment.

How the course runs. 8 blocks: Foundations of Data Governance and the DAMA DMBOK; Data Policies, Standards, and the Data Dictionary; Data Profiling: Measuring Quality Dimensions; Data Cleansing and Standardization Techniques; Metadata Management and Data Lineage; Master Data Management and Duplicate Resolution; Data Quality Monitoring, Audit Logging, and Compliance Documentation; Governance Framework Integration: Capstone Preparation and Credential Mapping.

What competent looks like. Define and document a data governance framework including roles, policies, and a data dictionary aligned to DAMA DMBOK domains. Profile a dataset using SQL and a profiling tool to identify completeness, uniqueness, validity, consistency, and accuracy failures. Design and implement data-quality rules as database constraints, CHECK logic, and automated pipeline checks in PostgreSQL. Build and maintain a metadata repository and data lineage map for a multi-source data flow. Apply master data management (MDM) concepts to identify and resolve duplicate and conflicting records across source systems. Demonstrate safe, professional data-handling practices including access controls, audit logging, and compliance documentation aligned to applicable data-privacy regulations.

Lessons · 8 blocks
#LessonHrTypeObjectiveActivitiesMaterialsCheck
1Foundations of Data Governance and the DAMA DMBOK10theoryStudents will explain the eleven DAMA DMBOK knowledge areas, the governance wheel, and the roles of data steward, data owner, and data custodian in an organization.
  1. Read and annotate Chapter 1 of the DAMA DMBOK (second edition) and create a one-page summary of each knowledge area.
  2. In small groups, role-play a governance committee meeting: assign steward, owner, and custodian roles and draft a sample data issue escalation procedure.
  3. Complete a mapping exercise that links each DMBOK knowledge area to a real job task performed by a database administrator or data analyst.
DAMA DMBOK 2nd edition (physical or e-book), whiteboard, role-assignment cards, blank governance framework template (instructor-provided)Students submit a completed DMBOK knowledge-area map with at least one concrete job-task example per area; instructor scores against a rubric requiring correct placement for at least 9 of 11 areas to pass.
2Data Policies, Standards, and the Data Dictionary11demoStudents will draft a data governance policy document and build a data dictionary for a sample operational database using a spreadsheet and a PostgreSQL information_schema query.
  1. Instructor demonstrates a live query of PostgreSQL information_schema.columns and information_schema.table_constraints to auto-generate a first-draft data dictionary; students replicate the query on the class training database.
  2. Students extend the auto-generated dictionary by adding business definitions, data owners, allowable values, and sensitivity classification for each column in a provided 15-table schema.
  3. Pairs of students peer-review each other's dictionaries against a provided checklist and document at least three gaps or inconsistencies.
PostgreSQL 15 training instance, DBeaver CE, Microsoft Excel or LibreOffice Calc, instructor-provided governance policy template, DAMA DMBOK referenceCompleted data dictionary covers all 15 tables with business definition, owner, data type, and sensitivity classification filled in; peer-review checklist confirms completeness; instructor verifies SQL queries execute without error — 100% of required columns populated to pass.
3Data Profiling: Measuring Quality Dimensions12labStudents will use SQL aggregate queries and an open-source profiling tool to measure the six DAMA data-quality dimensions (completeness, uniqueness, timeliness, validity, accuracy, consistency) against a realistic dirty dataset.
  1. Load a provided 50,000-row CSV of synthetic customer and order data into a PostgreSQL staging schema and write SQL queries measuring NULL rates, duplicate key counts, format violations, and out-of-range values for each dimension.
  2. Run the Great Expectations open-source library (Python) against the same staging table to generate an automated expectation suite and HTML report; compare findings with manual SQL results.
  3. Document all findings in a data-quality assessment report template, scoring each dimension on a 0–100 scale and prioritizing the top five issues by business impact.
PostgreSQL 15, Python 3.x, Great Expectations library, DBeaver CE, provided dirty CSV dataset, data-quality report template, DAMA DMBOK quality dimensions reference cardSQL scripts execute without error, profiling report identifies at least 8 distinct quality issues across at least 4 dimensions, and dimension scores are justified with row counts; instructor verifies report accuracy — at least 6 of 8 issues must match instructor key to pass.
4Data Cleansing and Standardization Techniques11labStudents will write SQL and Python routines to correct, standardize, and reject data-quality violations identified in the profiling lab, applying transformations in a staging-to-target ETL pattern.
  1. Using the dirty dataset from Lesson 3, write a series of SQL UPDATE, DELETE, and INSERT … SELECT statements that fix NULL substitutions, trim whitespace, standardize phone and date formats, and flag records that cannot be corrected.
  2. Build a Python script using pandas that applies regular-expression-based standardization rules to address and email fields, then reloads the cleaned records into a PostgreSQL target table.
  3. Re-run the Great Expectations suite on the cleaned target table, document the improvement in dimension scores, and write a one-page summary of any records rejected and why.
PostgreSQL 15, Python 3.x with pandas and psycopg2, DBeaver CE, Great Expectations, earlier profiling report, instructor-provided correction rules referenceTarget table passes at least 90% of expectation suite assertions; rejected-records table is populated with a rejection_reason column; improvement delta is calculated and documented — both code and report must meet threshold to pass.
5Metadata Management and Data Lineage11demoStudents will build a metadata repository table in PostgreSQL and draw a data-lineage diagram for a three-source ETL pipeline, demonstrating understanding of technical and business metadata.
  1. Instructor demonstrates Apache Atlas (community edition) or a lightweight open-source metadata tool; students catalog at least two source datasets and one target dataset, tagging business terms and sensitivity classifications.
  2. Students create a custom metadata_repository table in PostgreSQL with columns for source system, table name, column name, transformation applied, and target location, then populate it to reflect the ETL pipeline built in the ETL Pipelines course.
  3. Using draw.io (free, browser-based), each student draws a data-lineage diagram showing source → transformation → target for the pipeline, annotating each edge with transformation type.
PostgreSQL 15, draw.io (diagrams.net), Apache Atlas community edition or instructor-provided metadata tool, DBeaver CE, DAMA DMBOK metadata chapter referenceMetadata repository table contains correct entries for all pipeline stages; lineage diagram accounts for all three sources and the target without missing edges; instructor verifies against pipeline documentation — repository must be 100% complete and diagram must have zero missing nodes to pass.
6Master Data Management and Duplicate Resolution12practiceStudents will apply MDM concepts to identify, score, and resolve duplicate customer records across two source systems using deterministic and probabilistic matching techniques in SQL.
  1. Load two provided customer extract tables (each ~5,000 rows) into PostgreSQL; write SQL using string functions, Levenshtein distance (pg_trgm extension), and blocking keys to generate a candidate-pairs match table.
  2. Apply a weighted scoring rubric (name, address, phone, email) to each candidate pair and classify pairs as Match, Possible Match, or Non-Match; manually review and adjudicate a 50-row sample.
  3. Merge confirmed duplicates into a golden-record target table using a survivor-rule policy (most recently updated record wins for each attribute) and document the merge logic in the data dictionary.
PostgreSQL 15 with pg_trgm extension, DBeaver CE, provided synthetic dual-source customer CSVs, MDM scoring rubric template, DAMA DMBOK MDM chapterMatch table generated by SQL with no syntax errors; scoring rubric applied to all candidate pairs; golden-record table has zero duplicate keys; merge logic is documented — all four criteria must be met to pass.
7Data Quality Monitoring, Audit Logging, and Compliance Documentation12labStudents will implement an ongoing data-quality monitoring process using PostgreSQL triggers and scheduled queries, set up an audit log table, and produce a compliance summary document referencing applicable data-privacy principles.
  1. Write a PostgreSQL trigger function that inserts a record into an audit_log table on every INSERT, UPDATE, and DELETE on a nominated target table, capturing user, timestamp, operation, and changed values.
  2. Create a scheduled SQL script (using pg_cron or an OS cron job) that runs daily quality checks (NULL counts, range checks) against the target table and writes results to a data_quality_log table with a pass/fail flag.
  3. Draft a one-page compliance summary document explaining how the audit log and quality controls support general data-privacy principles (data minimization, purpose limitation, access control) without referencing specific law numbers, and present findings to the class in a five-minute verbal summary.
PostgreSQL 15 with pg_cron extension, DBeaver CE, Linux terminal (Ubuntu 22.04 VM), cron scheduling reference, data-privacy principles handout (instructor-prepared), compliance document templateTrigger fires correctly on all three DML operations and audit_log records are accurate; scheduled job runs and populates quality_log; compliance document references at least three privacy principles with correct explanations — all three deliverables must be complete and accurate to pass.
8Governance Framework Integration: Capstone Preparation and Credential Mapping12practiceStudents will assemble all governance artifacts from the course into a unified governance framework package and identify which DAMA CDMP, DP-300, and Oracle DBA CA exam domains each artifact addresses.
  1. Compile the data dictionary, data-quality report, lineage diagram, MDM golden-record documentation, and audit-log design from prior lessons into a single organized governance package, adding an executive summary and a table of contents.
  2. Complete a credential-mapping worksheet that lists each artifact against the specific DAMA CDMP Associate exam domain (e.g., Data Quality, Metadata Management, Master Data Management) and the relevant Microsoft DP-300 or Oracle exam objective it supports.
  3. Deliver a ten-minute structured walkthrough of the governance package to a small peer group, responding to at least two questions; peers score the presenter on clarity and completeness using a provided rubric.
All artifacts from Lessons 1–7, credential-mapping worksheet (instructor-provided), DAMA CDMP Associate exam domain outline, Microsoft DP-300 exam skills outline, Oracle DBA exam objectives list, presentation rubricGovernance package contains all seven required artifacts with no missing sections; credential-mapping worksheet correctly links at least 10 of 14 artifact-to-domain pairings; peer rubric scores average at least 3 out of 4 on clarity and completeness — all three criteria must be met to pass.
Assessments
AssessmentTypeWeightPass standardMethod & rubric
Data Governance & Quality Knowledge ExamWritten exam25%70% or higher (minimum 28 of 40 questions correct)A 40-question closed-book written exam covering DAMA DMBOK knowledge areas, data-quality dimensions, MDM concepts, metadata types, audit and compliance principles, and governance roles; questions are mapped directly to DAMA CDMP Associate exam domains and to relevant DP-300 and Oracle DBA CA objectives. Students have 60 minutes to complete the exam.
Standard met · Safety · Time · Quality/finish · Documentation
Data Profiling and Cleansing Skills DemonstrationSkills demonstration45%Instructor checklist: all five required steps demonstrated correctly; at least 90% of expectation suite assertions pass on the cleaned datasetEach student receives a previously unseen 10,000-row dirty dataset and has 90 minutes to profile it with SQL and Great Expectations, document at least six quality issues, apply cleansing transformations, and demonstrate the improvement in a re-run of the expectation suite while the instructor observes and asks two oral clarifying questions.
Standard met · Safety · Time · Quality/finish · Documentation
Governance Artifact Lab LogLog15%All seven artifacts present, complete, and internally consistent; instructor scores rubric at 80% or higher across completeness, accuracy, and professional presentation criteriaStudents submit the complete governance framework package assembled in Lesson 8, including data dictionary, quality assessment report, lineage diagram, MDM golden-record documentation, audit-log design, compliance summary, and credential-mapping worksheet; the package is evaluated for technical accuracy, internal consistency across artifacts, and professional formatting.
Standard met · Safety · Time · Quality/finish · Documentation
Safe Data-Handling and Access-Control Safety CheckSafety audit15%All critical items on the safety checklist marked correct; zero critical failures permittedInstructor uses a structured checklist to verify that each student's lab environment demonstrates correct role-based access control (no superuser connections for application accounts), audit logging enabled and tested, sensitive columns masked or restricted, and that the student can verbally explain why each control supports data-privacy and organizational security policy — any critical item failed requires remediation and recheck before the student advances.
Standard met · Safety · Time · Quality/finish · Documentation
TEC-DATA86-08 Trade course

Cloud Storage for Database Administrators

91 hr · $1,090 COMPLIMENTARY

This course teaches database administrators how to deploy, configure, manage, and secure relational and non-relational databases on major cloud platforms including AWS, Microsoft Azure, and Google Cloud. Students work with managed database services, cloud object storage, networking controls, cost management tools, and disaster-recovery configurations. Lessons map directly to Microsoft DP-300 exam domains and DAMA CDMP data management competencies.

Outcomes
Course text

This course teaches database administrators how to deploy, configure, manage, and secure relational and non-relational databases on major cloud platforms including AWS, Microsoft Azure, and Google Cloud. Students work with managed database services, cloud object storage, networking controls, cost management tools, and disaster-recovery configurations. Lessons map directly to Microsoft DP-300 exam domains and DAMA CDMP data management competencies.

How the course runs. 8 blocks: Cloud Fundamentals and Shared-Responsibility Model for DBAs; Managed Relational Database Services: Deploy and Connect; Cloud Object Storage and File-Based Data Movement; Network Security: VPCs, Private Endpoints, and Firewall Rules; Cloud Backup, Point-in-Time Restore, and Geo-Replication; Identity, Access Management, and Encryption for Cloud Databases; Performance Monitoring and Cost Management; Cloud DBA Capstone Lab: Deploy, Secure, and Recover a Multi-Tier Cloud Database.

What competent looks like. Deploy and configure managed relational database services (AWS RDS, Azure SQL Database, Google Cloud SQL) using both the cloud console and command-line interfaces. Design and implement cloud storage architectures—including object storage buckets, block storage volumes, and managed database tiers—appropriate to performance, availability, and cost requirements. Apply network security controls including VPCs, private endpoints, firewall rules, and role-based access to protect cloud-hosted databases from unauthorized access. Configure automated backups, point-in-time restore, geo-replication, and failover groups to meet defined recovery time and recovery point objectives. Monitor cloud database performance using platform-native tools, interpret metrics and alerts, and tune configuration parameters to maintain service-level targets. Estimate and control cloud database costs using pricing calculators, reserved-instance planning, and rightsizing analysis.

Lessons · 8 blocks
#LessonHrTypeObjectiveActivitiesMaterialsCheck
1Cloud Fundamentals and Shared-Responsibility Model for DBAs10theoryStudents will explain the shared-responsibility security model for IaaS, PaaS, and DBaaS tiers and identify which security controls the DBA must own on each major cloud platform.
  1. Read and annotate the AWS, Azure, and Google Cloud shared-responsibility documentation; complete a side-by-side comparison table showing which controls belong to the provider versus the customer at each service tier.
  2. Use the free tiers of AWS, Azure, and Google Cloud to navigate the consoles, create non-production accounts, and locate the managed database service menus—instructor demonstrates, students replicate step by step.
  3. Case-study discussion: given a fictional data breach scenario involving a misconfigured cloud database, students identify which shared-responsibility boundary was violated and write a one-page root-cause summary.
AWS Free Tier account, Azure free account, Google Cloud free account; cloud provider shared-responsibility whitepapers (publicly available); Microsoft DP-300 study guide (Microsoft Press); DAMA DMBOK2 Chapter 6 (Data Storage and Operations)10-question written quiz on shared-responsibility model, cloud service tiers, and DBA-owned controls; pass mark 70%.
2Managed Relational Database Services: Deploy and Connect14labStudents will provision a managed PostgreSQL or SQL Server instance on at least two cloud platforms, configure connection strings, and verify connectivity from a client workstation.
  1. Lab: provision an AWS RDS PostgreSQL instance using the AWS Console; configure subnet group, parameter group, and security group; connect with psql from a local VM and run a supplied schema script.
  2. Lab: provision an Azure SQL Database (General Purpose tier) using the Azure Portal and the Azure CLI (az sql db create); configure server firewall rules and Azure Active Directory admin; connect with Azure Data Studio.
  3. Pair exercise: one student documents each provisioning step as a numbered run-book, the other follows the run-book on Google Cloud SQL for PostgreSQL; pairs swap roles and peer-review each other's run-books for accuracy and completeness.
AWS Console and AWS CLI v2; Azure Portal and Azure CLI; Google Cloud Console and gcloud CLI; psql client; Azure Data Studio; lab VMs (Windows or Linux); Microsoft DP-300 Official Practice Tests; EnterpriseDB PostgreSQL documentationInstructor verifies live connection to each provisioned instance and reviews the run-book for all required configuration steps; pass requires successful connection on both platforms and a complete, accurate run-book.
3Cloud Object Storage and File-Based Data Movement10labStudents will create and configure cloud object storage buckets (S3, Azure Blob, GCS), apply access policies, and use storage as a staging area for database imports and exports.
  1. Lab: create an Amazon S3 bucket with versioning and server-side encryption enabled; upload a CSV data file; use AWS RDS import from S3 to load data into a PostgreSQL table; verify row counts.
  2. Lab: create an Azure Blob Storage container with private access; generate a Shared Access Signature (SAS) token with a limited TTL; export a database backup from Azure SQL Database to the container and confirm the file appears.
  3. Guided discussion and written exercise: compare S3, Azure Blob, and Google Cloud Storage pricing tiers (Standard, Infrequent Access, Archive equivalents); students complete a cost-estimation worksheet using publicly available pricing pages for a defined workload scenario.
AWS S3 console and AWS CLI; Azure Blob Storage and Azure CLI; Google Cloud Storage console; sample CSV dataset (provided); cloud pricing calculators (publicly available); spreadsheet applicationLab report showing screenshots of bucket configuration (encryption, access policy, versioning) and successful data load with row-count verification; pass requires correct encryption and access settings plus matching row counts.
4Network Security: VPCs, Private Endpoints, and Firewall Rules12labStudents will design and implement a secure network topology that places a managed database in a private subnet accessible only through defined private endpoints and security groups.
  1. Lab: in AWS, create a custom VPC with public and private subnets; place an RDS instance in the private subnet; configure a security group that allows inbound port 5432 only from an application-tier security group; verify no public internet access to the database.
  2. Lab: in Azure, configure a virtual network (VNet) and enable the Azure SQL Database private endpoint; disable public access; confirm that connection attempts from outside the VNet are refused while a VM inside the VNet connects successfully.
  3. Threat-modeling exercise: given a network diagram with three common misconfigurations (publicly accessible database, overly permissive inbound rules, unencrypted transit), students identify each flaw, explain the risk, and document the corrected configuration in writing.
AWS VPC console and AWS CLI; Azure VNet and private endpoint documentation; Wireshark (for transit inspection demo); network diagram templates; NIST SP 800-53 (network controls reference, publicly available); Microsoft DP-300 exam objective listInstructor tests connectivity from an external IP (expected: refused) and from a VM in the approved subnet (expected: successful); written threat-model document graded on identifying all three flaws with correct remediation; pass requires both network tests to pass and all three flaws identified.
5Cloud Backup, Point-in-Time Restore, and Geo-Replication14labStudents will configure automated backup policies and geo-redundant replication on a managed cloud database, then execute and verify a point-in-time restore to a specific timestamp.
  1. Lab: on AWS RDS PostgreSQL, enable automated backups with a defined retention period; enable Multi-AZ deployment for high availability; simulate data loss by deleting a table; perform a point-in-time restore to a snapshot before the deletion and verify table presence.
  2. Lab: on Azure SQL Database, configure active geo-replication to a secondary region using the Azure Portal; simulate a failover using the manual failover command; verify the secondary becomes primary and check connection strings update.
  3. Written RTO/RPO planning exercise: given a business scenario with defined recovery time objective and recovery point objective requirements, students select and justify the appropriate AWS or Azure backup/replication configuration, citing specific service settings.
AWS RDS console; Azure SQL Database geo-replication documentation; Azure Portal; lab timer (to measure actual restore duration against RTO); Microsoft DP-300 study guide chapters on business continuity; DAMA DMBOK2 Chapter 6Instructor confirms restored instance contains the previously deleted table; failover demo shows successful promotion of secondary; written RTO/RPO exercise reviewed for correct service selection and justification; pass requires all three verified.
6Identity, Access Management, and Encryption for Cloud Databases10demoStudents will implement least-privilege IAM roles for database access, enable encryption at rest and in transit, and audit access events using cloud-native logging tools.
  1. Instructor-led demo followed by student replication: create an AWS IAM role with a least-privilege policy allowing read-only RDS access; assign the role to an EC2 instance; confirm the instance can read but cannot modify the database using that role.
  2. Lab: enable Azure SQL Database Transparent Data Encryption with a customer-managed key stored in Azure Key Vault; verify the key vault access policy allows only the database service principal; confirm TDE status in the portal.
  3. Log-review exercise: enable AWS CloudTrail or Azure Monitor diagnostic logs for a database instance; generate several connection and query events; download the log file and identify the timestamp, user, and action for each event in a structured worksheet.
AWS IAM console; AWS CloudTrail; Azure Key Vault; Azure Monitor; Azure SQL Database portal; Microsoft DP-300 exam objective list (security domain); DAMA CDMP exam body of knowledge (data security chapter)Role-access test: student demonstrates the read-only role cannot execute a DROP TABLE (expected error) but can execute SELECT; TDE status shown as enabled with customer key; log worksheet complete with all required fields; pass mark 80% on worksheet.
7Performance Monitoring and Cost Management11practiceStudents will interpret cloud database performance metrics, set threshold-based alerts, and produce a rightsizing recommendation that reduces estimated monthly cost without violating performance targets.
  1. Guided practice: use Amazon CloudWatch metrics (CPU utilization, FreeStorageSpace, DatabaseConnections) for a running RDS instance; create a CloudWatch alarm that sends an email when CPU exceeds a defined threshold for five consecutive minutes; document each step.
  2. Practice: use Azure Monitor and the Query Performance Insight blade for Azure SQL Database to identify the top three queries by CPU consumption; for each query, record the execution plan, identify the missing or unused index, and write the CREATE INDEX statement.
  3. Cost-optimization worksheet: given a Cloud provider cost report (simulated spreadsheet provided by instructor), students identify over-provisioned instances, calculate potential savings from moving to a lower compute tier or reserved pricing, and present a one-page written recommendation with numeric justification using the platform pricing calculator.
AWS CloudWatch console; Azure Monitor and Query Performance Insight; simulated cost report spreadsheet (instructor-provided); AWS and Azure pricing calculators (publicly available); Microsoft DP-300 study guide (monitoring and optimization chapters)CloudWatch alarm demonstrated as active with correct threshold; at least two valid CREATE INDEX statements confirmed by instructor review; cost worksheet shows correct arithmetic and a recommendation with numeric savings estimate; pass requires all three elements present and correct.
8Cloud DBA Capstone Lab: Deploy, Secure, and Recover a Multi-Tier Cloud Database10labStudents will independently plan, deploy, secure, back up, and recover a managed cloud database environment to a written specification, producing a complete run-book and a brief oral explanation of their decisions.
  1. Individual build: student receives a written scenario specifying a database platform, storage size, RTO, RPO, network topology, and access requirements; student provisions the full environment (managed DB, private network, IAM roles, encryption, automated backup, and monitoring alert) on one cloud platform within the allotted time.
  2. Recovery drill: instructor deletes a designated table from the student's running instance without warning; student must detect the loss using monitoring logs and execute a point-in-time restore, documenting each step taken and the actual recovery time achieved.
  3. Run-book completion and oral explanation: student submits the completed run-book covering all build steps and the recovery drill; student answers three instructor questions about configuration choices, explaining why specific settings meet the scenario's requirements.
Cloud platform accounts (AWS or Azure per student choice); all CLI tools and consoles used throughout the course; run-book template (instructor-provided); Microsoft DP-300 exam objective checklist (used as self-review before submission); DAMA DMBOK2 referenceAll specified services deployed and verified by instructor; recovery drill completed with table restored and actual recovery time within the scenario's RTO; run-book contains all required sections; oral questions answered correctly; pass requires all deployment checks passed, RTO met, and at least two of three oral questions answered correctly.
Assessments
AssessmentTypeWeightPass standardMethod & rubric
Cloud Concepts and Services Written ExamWritten exam25%70% correct (28 of 40 questions)A 40-question closed-book exam covering shared-responsibility model, cloud service tiers, managed database service options, storage classes, IAM principles, encryption methods, and backup/replication concepts across AWS, Azure, and Google Cloud. Questions are written to mirror the style of Microsoft DP-300 and DAMA CDMP Associate exam items.
Standard met · Safety · Time · Quality/finish · Documentation
Live Cloud Database Deployment Skills DemonstrationSkills demonstration45%All five required configuration checkpoints verified by instructor; no critical security misconfiguration presentEach student independently provisions a managed PostgreSQL or SQL Server instance on an assigned cloud platform, configures a private network, applies least-privilege IAM, enables encryption at rest and in transit, and sets up an automated backup—all within a 90-minute window. The instructor checks each checkpoint using the cloud console and CLI commands.
Standard met · Safety · Time · Quality/finish · Documentation
Lab Log PortfolioLog15%At least 6 of 7 lab entries complete with screenshots, correct configuration details, and a written reflection; no missing safety or access-control stepsStudents maintain a cumulative lab log throughout the course, submitting a structured entry for each lab lesson that includes the objective, steps taken, screenshots of key configurations, actual results versus expected results, and a one-paragraph reflection on what would change in a production environment. The portfolio is reviewed at the end of the course.
Standard met · Safety · Time · Quality/finish · Documentation
Cloud Security and Access Control Safety CheckSafety audit15%Zero critical findings; all five security checklist items confirmed; any minor finding corrected on the spotUsing a standardized five-item checklist (public access disabled, encryption at rest enabled, encryption in transit enforced, least-privilege IAM applied, audit logging active), the instructor audits the student's capstone lab environment. This check mirrors the security hardening objectives tested in the Microsoft DP-300 exam and reinforces data stewardship principles from the DAMA CDMP body of knowledge.
Standard met · Safety · Time · Quality/finish · Documentation
TEC-DATA86-09 Trade course

Bash Automation for Database Administration

91 hr · $1,090 COMPLIMENTARY

Students learn to write, test, and deploy Bash shell scripts that automate routine PostgreSQL, Oracle, and cloud database administration tasks including backups, health checks, log parsing, ETL triggers, and scheduled maintenance jobs. Emphasis is placed on scripting best practices, error handling, and secure credential management so that automation artifacts are reliable, auditable, and safe to run in production environments. Lesson outcomes map directly to scripting and operational-automation competencies tested in the EDB PostgreSQL CE, Oracle DBA CA, and Microsoft DP-300 credential exams.

Outcomes
Course text

Students learn to write, test, and deploy Bash shell scripts that automate routine PostgreSQL, Oracle, and cloud database administration tasks including backups, health checks, log parsing, ETL triggers, and scheduled maintenance jobs. Emphasis is placed on scripting best practices, error handling, and secure credential management so that automation artifacts are reliable, auditable, and safe to run in production environments. Lesson outcomes map directly to scripting and operational-automation competencies tested in the EDB PostgreSQL CE, Oracle DBA CA, and Microsoft DP-300 credential exams.

How the course runs. 8 blocks: Linux Shell Foundations and the DBA Command Line; Script Structure, Variables, and Control Flow; Error Handling, Exit Codes, and Logging; Automating PostgreSQL Backup and Restore; Cron, systemd Timers, and Job Scheduling; Log Parsing and Report Generation with grep, awk, and sed; Secure Credential Management and Script Hardening; Git Version Control for DBA Automation Libraries.

What competent looks like. Write syntactically correct Bash scripts that automate at least five routine DBA tasks, including backup initiation, log rotation, health polling, and alert dispatch, achieving zero syntax errors on bash --norc -n linting. Implement robust error handling with exit codes, trap statements, and conditional logic so that scripts detect failures, log diagnostic messages, and send email or webhook alerts without manual intervention. Schedule and manage Bash-driven cron jobs and systemd timer units on a Linux server, documenting each job's schedule, purpose, owner, and expected output in a runbook. Apply secure credential-management techniques—including environment variables, .pgpass files, Oracle wallets, and secrets-file permissions—to prevent plaintext passwords in script source code. Parse and summarize structured log files using grep, awk, and sed, producing human-readable reports that satisfy data-governance audit trail requirements covered in the DAMA CDMP Associate exam domain. Demonstrate professional version control discipline by committing all scripts to a Git repository with meaningful commit messages, a README, and a changelog before handing off automation to an operations team.

Lessons · 8 blocks
#LessonHrTypeObjectiveActivitiesMaterialsCheck
1Linux Shell Foundations and the DBA Command Line10theoryStudents will identify and correctly use fundamental Bash constructs—variables, quoting rules, command substitution, pipelines, and redirections—as the building blocks of all subsequent DBA automation.
  1. Read sections 1–4 of the GNU Bash Reference Manual (freely available at gnu.org); annotate five constructs not encountered before and share annotations in a whole-class discussion.
  2. Complete 20 progressive command-line exercises on a CentOS or Ubuntu VM—navigating the filesystem, inspecting processes with ps and top, managing files, and chaining commands with pipes—recording each command and its output in a lab journal.
  3. As an exit activity, write a one-page 'DBA command cheat sheet' that maps ten common administrative tasks (e.g., list running Postgres connections) to their shell commands, which the instructor reviews for accuracy.
Linux VM (VirtualBox or cloud instance), GNU Bash Reference Manual (gnu.org), terminal emulator, lab journal templateInstructor reviews lab journal entries; student must answer correctly at least 8 of 10 spot-check questions on quoting rules, pipe behavior, and redirect syntax to pass this lesson checkpoint.
2Script Structure, Variables, and Control Flow12demoStudents will construct well-structured Bash scripts that use shebang lines, comments, named variables, positional parameters, if/elif/else logic, and for/while loops to carry out a branching DBA workflow.
  1. Instructor live-codes a script that accepts a database name as a positional parameter, checks whether that database exists using psql -lqt, and echoes a pass/fail message; students follow along, then modify the script to also check for a minimum connection count.
  2. Students write an original 30-line script that loops through a text file of five server hostnames, pings each, and writes 'UP' or 'DOWN' with a timestamp to a status log file; peer-pairs review each other's scripts against a six-point checklist (shebang, comments, quoting, exit code, loop, log).
  3. Run bash --norc -n on each script to check syntax, fix any errors reported, and document the before/after diff in the lab journal.
Linux VM, psql client, text editor (VS Code or vim), bash manual pages, peer-review checklist handoutScript must pass bash --norc -n with zero errors, correctly branch on all three test conditions, and receive at least 5 of 6 on the peer checklist; instructor spot-checks one script per pair.
3Error Handling, Exit Codes, and Logging11demoStudents will add robust error detection to scripts using set -euo pipefail, trap ERR handlers, meaningful exit codes, and timestamped log output routed to syslog and a flat file.
  1. Instructor demonstrates how a script without error handling silently skips a failed pg_dump; students observe the corrupt backup and then add set -euo pipefail plus a trap 'echo ERROR at line $LINENO' ERR to reproduce the failure safely and capture it in the log.
  2. Students refactor a provided 'broken' 50-line backup script by adding trap, exit-code checks on every command, and a log_msg() function that prepends ISO-8601 timestamps; they test failure scenarios by intentionally pointing the script at a nonexistent database.
  3. Students write a one-page incident-response note describing how the enhanced logging would help an on-call DBA diagnose a 2 a.m. backup failure, tying the explanation to Oracle DBA CA operational-monitoring exam objectives.
Linux VM, pg_dump, PostgreSQL 15 documentation (Section on server administration), sample broken script provided by instructor, syslog viewer (journalctl)Refactored script must log a timestamped error message and exit with a non-zero code when given a bad database name; instructor injects three failure conditions and the script must catch all three to pass.
4Automating PostgreSQL Backup and Restore12labStudents will write and validate a production-quality Bash script that performs scheduled PostgreSQL logical backups using pg_dump, manages backup retention, and executes a test restore into a staging database.
  1. Students build a backup script that accepts environment variables for PGHOST, PGPORT, PGDATABASE, and PGPASSFILE; uses pg_dump with a timestamped filename; compresses output with gzip; and deletes files older than a configurable RETENTION_DAYS value using find -mtime.
  2. Students run a simulated restore by piping the compressed dump through gunzip into psql against a staging database named restore_test, then run a row-count query to verify data integrity, documenting pass/fail in the lab journal—directly addressing EDB PostgreSQL CE backup/recovery exam objectives.
  3. Students configure .pgpass with correct 0600 permissions and confirm that running the script produces no password prompt, then write a paragraph explaining why plaintext passwords in scripts violate both security policy and DAMA CDMP data-governance principles.
Linux VM, PostgreSQL 15, pg_dump, psql, gzip, .pgpass file, lab journal, EDB PostgreSQL CE exam guideScript must complete a full backup-and-restore cycle with zero errors, the restored row count must match the source, .pgpass must be 0600 permissions, and the lab journal entry must be complete; all three conditions required to pass.
5Cron, systemd Timers, and Job Scheduling10practiceStudents will schedule Bash DBA scripts using both crontab and systemd timer units, verify execution at the correct interval, and document each scheduled job in a formatted runbook entry.
  1. Students add their backup script from Lesson 4 to the system crontab to run nightly at 2:00 a.m., then use cron log entries (grep CRON /var/log/syslog or journalctl -u cron) to confirm successful execution after a test run triggered with a near-term time offset.
  2. Students create a systemd .service and .timer unit pair that runs a database health-check script every 15 minutes, enable the timer with systemctl enable --now, and use systemctl list-timers to verify scheduling—mapping to DP-300 Azure automation and monitoring exam topics.
  3. Students complete a runbook template for both scheduled jobs, documenting schedule expression, script path, owner, expected log location, and escalation contact; instructor reviews for completeness.
Linux VM with systemd, crontab, journalctl, runbook template (Word/Markdown), Microsoft DP-300 exam skills outlineCron job must appear in cron log with a success exit code; systemd timer must show ACTIVE in list-timers output; runbook entries must include all five required fields to pass.
6Log Parsing and Report Generation with grep, awk, and sed12labStudents will parse PostgreSQL and Oracle alert log files using grep, awk, and sed to extract error counts, slow-query events, and connection statistics, then format results into a plain-text summary report suitable for a data-governance audit.
  1. Given a 10,000-line simulated PostgreSQL log file, students use grep with extended regex to extract all lines containing ERROR or FATAL, pipe to awk to count occurrences by hour, and redirect to a report file; they compare output with a provided answer key.
  2. Students write a sed one-liner that redacts IP addresses in a log file (replacing each IPv4 address with [REDACTED]) to demonstrate privacy-by-design handling aligned with DAMA CDMP data-quality and governance exam domains.
  3. Students build a 40-line awk script that parses pg_stat_statements output dumped to CSV, computes average execution time per query type, and prints a top-10 slowest-query table—then add this script as a weekly cron job.
Linux VM, sample PostgreSQL log file (instructor-provided), pg_stat_statements CSV export, awk manual (man awk), DAMA CDMP Body of Knowledge chapter on data qualityError-count report must match the answer key within ±2 counts; IP-redaction sed command must redact all 50 test IPs with zero false negatives; awk top-10 table must sort correctly; all three checked to pass.
7Secure Credential Management and Script Hardening12practiceStudents will apply layered credential-management techniques—environment files, .pgpass, Oracle wallets, restricted file permissions, and secrets scanning—to eliminate plaintext passwords from all scripts in their automation library.
  1. Students audit the five scripts written in previous lessons using a simple grep -rn 'password\\|PASSWORD\\|PGPASSWORD' scan; for any hit, they refactor to load credentials from a sourced .env file with 0600 permissions or from the system keyring, then re-run the scan to confirm zero hits.
  2. Students configure a PostgreSQL scram-sha-256 connection using certificate authentication on the VM, update their backup script to use the cert, and document the pg_hba.conf changes—connecting Oracle DBA CA and DP-300 security exam objectives to the hands-on task.
  3. Students complete an OSHA-aligned security checklist (covering physical server access controls, screen-lock policy, and least-privilege account practices for service accounts) and discuss how digital security controls for scripts parallel physical lockout/tagout principles taught in Course 1.
Linux VM, OpenSSL, .pgpass, pg_hba.conf, .env file template, grep, OSHA 10 lockout/tagout analogy handout, Oracle DBA CA exam guide section on securitygrep scan of all five scripts must return zero plaintext-password hits; pg_hba.conf must use scram-sha-256 or cert method; OSHA checklist must be fully completed with no blank items to pass.
8Git Version Control for DBA Automation Libraries12practiceStudents will initialize a Git repository, commit all course scripts with descriptive messages and a README, manage branches for script versions, and demonstrate a pull-request-style review workflow appropriate for a professional DBA team.
  1. Students initialize a local Git repo, add all scripts written in Lessons 1–7, write a README.md that describes each script's purpose, usage, dependencies, and cron schedule, and push to a GitHub or GitLab account; the instructor reviews the repository link for completeness.
  2. Students create a feature branch named hotfix/backup-retention, modify the RETENTION_DAYS default value, commit with a message following the Conventional Commits format (e.g., 'fix(backup): increase default retention to 30 days'), and merge back to main via a pull request with a written description.
  3. Students write a CHANGELOG.md with entries for each script update made during the course, then role-play a five-minute hand-off meeting where they walk a 'new team member' (a classmate) through the repo structure, demonstrating the career-readiness communication skills from Course 1.
Linux VM, Git, GitHub or GitLab account, VS Code with GitLens extension, Conventional Commits specification (conventionalcommits.org), README templateRepository must contain all five core scripts, a README with all required sections, at least one merged feature branch, and a CHANGELOG with at least three dated entries; instructor clones the repo and verifies all files run without modification to pass.
Assessments
AssessmentTypeWeightPass standardMethod & rubric
Bash Automation Knowledge ExamWritten exam25%70% or higher (42 of 60 points)A 60-question written exam covering Bash syntax, control flow, error-handling constructs, cron and systemd scheduling syntax, log-parsing tools (grep, awk, sed), and secure credential-management principles. Questions are drawn from EDB PostgreSQL CE, Oracle DBA CA, and Microsoft DP-300 scripting and automation exam objectives; students must score at least 70% to demonstrate readiness for those credential exams.
Standard met · Safety · Time · Quality/finish · Documentation
Live Scripting Skills DemonstrationSkills demonstration45%Pass on all four evaluated tasks; any single failure requires a re-demo within five business daysIn a 45-minute proctored session, the student receives a new scenario (database name, server list, retention policy) and must write from scratch, without notes: a backup script with error handling, a cron entry, a log-parsing one-liner, and a .pgpass configured correctly; the instructor evaluates correctness, security, and code clarity using a four-point rubric.
Standard met · Safety · Time · Quality/finish · Documentation
Lab Journal and Script Portfolio LogLog15%All eight lesson lab-journal entries present and complete; script portfolio contains all five required scripts passing bash --norc -n with zero errorsStudents submit their lab journal (digital or handwritten, scanned) containing entries for all eight lessons plus their Git repository URL; the instructor verifies that each entry includes the task performed, commands used, output observed, and any errors encountered and resolved, confirming a continuous record of skill development aligned with DAMA CDMP audit-trail documentation standards.
Standard met · Safety · Time · Quality/finish · Documentation
Script Security and Safe-Practices Safety CheckSafety audit15%Zero critical findings; all checklist items marked compliantUsing a structured 20-item checklist, the instructor audits the student's complete script library for critical safety and security items: no plaintext passwords, correct file permissions (0600 on credential files), set -euo pipefail present in every script, all cron jobs logged, no world-writable script files, and service accounts following least-privilege principle; this check mirrors the OSHA lockout/tagout discipline taught in Course 1 applied to the digital-operations context, and any critical finding must be corrected and re-checked before the student may advance to the Capstone.
Standard met · Safety · Time · Quality/finish · Documentation
TEC-DATA86-10 Capstone

Capstone Project: Integrated Database Administration System Build

162 hr · $1,620 COMPLIMENTARY

Students design, build, secure, automate, and document a production-grade relational database system that integrates skills from every prior course in the program. The capstone culminates in a formal technical defense before a panel of instructors and an industry reviewer, demonstrating job-entry competency across all credential exam domains.

Outcomes
Course text

Students design, build, secure, automate, and document a production-grade relational database system that integrates skills from every prior course in the program. The capstone culminates in a formal technical defense before a panel of instructors and an industry reviewer, demonstrating job-entry competency across all credential exam domains.

How the course runs. 4 blocks: Project Scoping, Requirements Analysis, and Architecture Planning; Database Build: Schema, Security, Backup, and ETL Implementation; Documentation, Governance Artifacts, and Runbook Completion; Defense Preparation, Dry Run, and Final Presentation.

What competent looks like. Design and implement a normalized, multi-table PostgreSQL database that meets documented business requirements and passes a structured code and schema review. Configure role-based access control, encrypted connections, and an automated backup/recovery schedule that satisfies a written security and continuity policy. Build and schedule an ETL pipeline that ingests, transforms, and loads data from at least two heterogeneous sources into the target database with logged error handling. Apply data governance principles including a data dictionary, data quality checks, and lineage documentation that conform to DAMA DMBOK framework areas. Produce a complete professional technical package—ERD, data flow diagram, runbook, and change log—using industry-standard documentation conventions. Defend design decisions, troubleshoot live scenarios, and respond to examiner questions demonstrating knowledge aligned to PostgreSQL CE, Oracle DBA CA, DP-300, and CDMP Associate exam domains.

Lessons · 4 blocks
#LessonHrTypeObjectiveActivitiesMaterialsCheck
1Project Scoping, Requirements Analysis, and Architecture Planning30practiceStudents produce a signed-off project charter, entity-relationship diagram, and architecture diagram that fully define scope, data sources, security boundaries, and cloud or on-premises hosting before any build work begins.
  1. Complete a structured stakeholder-interview worksheet using a supplied business scenario (a regional nonprofit managing donor, grant, and program data), then draft a one-page requirements specification identifying at minimum six entities, two external data sources, three user roles, and one regulatory constraint.
  2. Draw a crow's-foot ERD to 3NF using draw.io or pgModeler, annotating each entity with primary keys, foreign keys, data types, and nullability; peer-review a classmate's ERD against a provided rubric and document at least two findings.
  3. Present the draft charter and ERD to the instructor in a 15-minute desk review; revise based on written feedback and obtain instructor sign-off before proceeding to the build phase.
Instructor-issued business scenario brief, pgModeler or draw.io (free tier), ERD rubric checklist, DAMA DMBOK 2nd edition (Chapter 5 – Data Modeling), project charter template, PostgreSQL 15 documentationInstructor sign-off on charter and ERD; rubric score of 80% or higher on completeness, normalization correctness, and clarity before the student is cleared to proceed to Lesson 2.
2Database Build: Schema, Security, Backup, and ETL Implementation72labStudents implement the approved schema in PostgreSQL, configure role-based access and TLS connections, schedule automated pg_dump backups with a tested restore procedure, and build an ETL pipeline using Python or pgAgent that loads and transforms data from two sources into the live database.
  1. Write and execute DDL scripts to create all tables, constraints, indexes, and sequences; populate the database with a minimum of 500 realistic rows using a combination of supplied CSV imports and Python-generated synthetic data, verifying referential integrity with a set of provided SQL assertion queries.
  2. Create at least three PostgreSQL roles (read-only analyst, data-entry operator, DBA) with column-level and row-level privileges where appropriate; configure pg_hba.conf for password authentication over TLS, document the security configuration in a written security policy memo, and perform a penetration check by attempting forbidden operations from each role account.
  3. Build a Python or pgAgent ETL pipeline that extracts records from a CSV flat file and a SQLite source database, applies documented transformation rules (type casting, deduplication, null handling), loads results into the PostgreSQL target with transaction logging, and runs on a cron or pgAgent schedule; validate with a before-and-after row count and error log review.
PostgreSQL 15 on a local VM or cloud sandbox (AWS RDS free tier or Azure Database for PostgreSQL), Python 3 with psycopg2 and pandas, pgAdmin 4, OpenSSL for certificate generation, pg_dump / pg_restore, supplied CSV and SQLite source files, CIS PostgreSQL Benchmark (current version), pgAgent documentationAutomated test suite (instructor-provided SQL scripts) must pass at least 18 of 20 integrity and security checks; restore drill must recover the database to a point-in-time within the prior 24 hours with zero data loss; ETL pipeline must complete without unhandled exceptions and load records within a 5% tolerance of the expected row count.
3Documentation, Governance Artifacts, and Runbook Completion36practiceStudents produce a complete technical documentation package—including a data dictionary, data quality rule log, lineage diagram, operational runbook, and change log—sufficient for a new DBA to operate and maintain the system without additional guidance.
  1. Complete a data dictionary spreadsheet for every table and column, recording business name, technical name, data type, allowed values or domain, source system, steward, and any applicable regulatory classification (e.g., PII); cross-reference each column against the ERD.
  2. Write a minimum of eight data quality rules (e.g., NOT NULL enforcement, referential integrity, range checks, format validation) in both plain English and as SQL CHECK constraints or trigger logic; run a data quality audit query against the live database and document findings in a defect log with resolution status.
  3. Assemble the operational runbook covering daily startup/shutdown procedures, backup verification steps, user provisioning workflow, incident response checklist, and a disaster recovery contact tree; include the lineage diagram showing data flow from each source through transformation to target tables, and maintain a change log recording every schema or configuration modification made during the build phase.
DAMA DMBOK 2nd edition (Chapters 6, 13), data dictionary template (instructor-provided), draw.io for lineage diagram, Microsoft Word or Google Docs, runbook template (instructor-provided), PostgreSQL system catalog reference (pg_class, information_schema)Documentation package reviewed against a 25-item rubric; all eight data quality rules must be syntactically correct and execute without error; runbook must be judged complete and navigable by a peer acting as a new DBA in a 10-minute walkthrough exercise; minimum rubric score of 80%.
4Defense Preparation, Dry Run, and Final Presentation24fieldStudents rehearse and deliver a formal 30-minute technical defense of their capstone system before a panel, responding to live troubleshooting scenarios and examiner questions that map to PostgreSQL CE, Oracle DBA CA, DP-300, and CDMP Associate exam competency areas.
  1. Prepare a structured 20-minute slide presentation covering business requirements, architecture decisions, security design, ETL pipeline logic, governance artifacts, lessons learned, and next-iteration improvements; conduct a timed dry run with a peer serving as evaluator using the defense scoring rubric, then revise the presentation based on written peer feedback.
  2. Complete a 30-minute live troubleshooting drill in which the instructor introduces three injected faults (e.g., a broken foreign key constraint, a failed backup job, a misconfigured role permission) into a copy of the student's database; the student must diagnose and resolve each fault on-screen while narrating their reasoning aloud.
  3. Deliver the final defense to a panel of at least two evaluators (one instructor and one industry or advisory board reviewer); after the presentation, respond to a minimum of 10 minutes of examiner questions drawn from the credential exam domain areas, including at least one question each on data modeling, security, backup/recovery, ETL, and data governance.
Defense scoring rubric (instructor-provided), slide deck tool (PowerPoint or Google Slides), live PostgreSQL environment with instructor access for fault injection, examiner question bank mapped to PostgreSQL CE / Oracle DBA CA / DP-300 / CDMP Associate domains, projection equipment, defense feedback formPanel scores each section of the defense rubric (technical accuracy, documentation quality, communication clarity, troubleshooting performance, response to questions); student must achieve a composite score of 80% or higher across all rubric sections and resolve at least 2 of 3 injected faults correctly to pass the defense.
Assessments
AssessmentTypeWeightPass standardMethod & rubric
Capstone System Build and Documentation PackageProject60%80% or higher on the project rubric, with no critical failures (schema errors that violate 3NF, restore drill failure, or unresolved security misconfiguration that allows privilege escalation) left unremediatedThe evaluator reviews the complete deliverable set—DDL scripts, running database, ETL pipeline, backup/restore evidence, security configuration, data dictionary, data quality log, lineage diagram, and runbook—against a 50-point weighted rubric covering correctness, completeness, security posture, and professional documentation quality. This assessment maps directly to all four credential exam domains: schema design (PostgreSQL CE, Oracle DBA CA), cloud and managed database configuration (DP-300), and data governance artifacts (CDMP Associate).
Meets specification · Within estimate · Workmanship · Safety · Documentation
Professional Portfolio SubmissionPortfolio20%All seven required artifacts submitted; minimum score of 80% on the portfolio rubric assessing organization, accuracy, and professional presentationStudents compile and submit a professional portfolio containing seven artifacts in a single organized PDF or shared drive folder: the signed project charter, final ERD, security policy memo, ETL pipeline code with inline comments, data dictionary, operational runbook with change log, and a one-page personal reflection on skill growth and credential readiness. The portfolio is intended as a job-search artifact demonstrating competency to prospective employers and aligns with the professional documentation standards emphasized in the DAMA CDMP Associate and DP-300 credential areas.
Completeness · Organization · Evidence quality
Technical Defense Oral ExaminationOral / panel20%Composite panel score of 80% or higher across all rubric sections; resolution of at least 2 of 3 injected database faults during the live troubleshooting segmentA panel of at least two evaluators assesses the student's 30-minute live defense covering system architecture, security design, ETL logic, governance approach, and lessons learned, followed by a minimum 10-minute examiner Q&A session drawing questions from the PostgreSQL CE, Oracle DBA CA, DP-300, and CDMP Associate exam competency areas. Scoring rubric sections include technical accuracy (30%), communication and professionalism (20%), documentation quality (20%), live troubleshooting (20%), and response to examiner questions (10%).
Explains decisions · Answers technical questions · Professional communication
TEC-DATA86-11 Externship / clinical

Externship / Worksite Placement

243 hr · $970 COMPLIMENTARY

Students complete 243 supervised hours at an employer site performing real database administration, data management, and ETL tasks under the direction of a credentialed industry mentor. Work is structured across an orientation phase, core DBA duties, a mentor-assigned project, and a professional reflection, mirroring the full scope of the PostgreSQL CE, Oracle DBA CA, Microsoft DP-300, and DAMA CDMP Associate exam domains in a live production environment. Employer evaluations and a structured field log document competency attainment against program outcomes.

Outcomes
Course text

Students complete 243 supervised hours at an employer site performing real database administration, data management, and ETL tasks under the direction of a credentialed industry mentor. Work is structured across an orientation phase, core DBA duties, a mentor-assigned project, and a professional reflection, mirroring the full scope of the PostgreSQL CE, Oracle DBA CA, Microsoft DP-300, and DAMA CDMP Associate exam domains in a live production environment. Employer evaluations and a structured field log document competency attainment against program outcomes.

How the course runs. 4 blocks: Site Orientation, Security Compliance & Safety Review; Core DBA Duties Under Supervision; Mentor-Assigned Applied Project; Final Evaluation & Professional Reflection.

What competent looks like. Perform assigned database administration tasks—including backup/recovery checks, user role management, and query tuning—safely and correctly in a live or near-production environment under mentor supervision. Apply data governance and quality principles on real organizational data assets, demonstrating practices aligned with DAMA CDMP Associate exam domains. Execute or assist with at least one ETL or cloud-storage workflow using employer-approved tools, documenting steps and outcomes in a structured field log. Demonstrate professional workplace behavior including punctuality, communication, and compliance with site security and acceptable-use policies. Receive a passing employer evaluation score on all rated competency dimensions at the conclusion of the placement. Produce a written professional reflection that connects worksite experiences to certification exam domains and identifies areas for continued development.

Lessons · 4 blocks
#LessonHrTypeObjectiveActivitiesMaterialsCheck
1Site Orientation, Security Compliance & Safety Review24fieldThe student completes all employer onboarding requirements, reviews site-specific data security and acceptable-use policies, and identifies physical and digital safety procedures relevant to the worksite before performing any independent tasks.
  1. Complete employer onboarding checklist: badge/access provisioning, network account setup, NDA or confidentiality agreement review, and tour of server room or data center with mentor noting physical safety controls such as restricted access, fire suppression systems, and cable management hazards.
  2. Review and annotate the employer's acceptable-use policy, data classification policy, and incident-reporting procedure, then meet with mentor to confirm understanding and ask clarifying questions; record key policy points in field log.
  3. Shadow a senior DBA or data engineer for two full shifts, logging every task observed (backup job monitoring, ticket response, schema change approval) and mapping each task to a corresponding program course and certification exam domain in the field log.
Employer onboarding packet, site acceptable-use and data classification policies, field log workbook (paper or digital), OSHA 10 card (student-issued from Course 1), program competency mapping guideMentor signs orientation checklist confirming all access controls are in place and student can correctly explain the site's incident-reporting procedure; field log entries for both shadow shifts are complete and show at least one exam-domain mapping per observed task. Pass: all checklist items signed and field log reviewed as satisfactory by mentor.
2Core DBA Duties Under Supervision108fieldThe student independently executes assigned, recurring database administration tasks—including scheduled backup verification, user/role provisioning, index maintenance, and performance monitoring—under daily mentor oversight, logging each task and its outcome.
  1. Each scheduled workday, perform assigned tasks from the employer's DBA task queue (examples: verify overnight backup completion and integrity, create or revoke user roles per ticket, run VACUUM/ANALYZE or equivalent maintenance on PostgreSQL or the site's RDBMS, review slow-query logs and flag candidates for tuning) and record task name, commands used, result, and time in the field log.
  2. Attend or participate in at least two team meetings (sprint standup, change-control board, or data governance committee) and submit a one-paragraph field log summary per meeting describing decisions made and how they relate to DAMA CDMP, DP-300, or Oracle DBA CA exam domains.
  3. Respond to at least three mentor-assigned trouble tickets (simulated or real low-risk incidents such as a failed scheduled job, a locked account, or a disk-space alert), document the diagnosis and resolution steps taken, and have the mentor review and sign off each ticket resolution in the field log.
Employer RDBMS environment (PostgreSQL, Oracle, SQL Server, or cloud equivalent), ticketing system access, field log workbook, program competency mapping guide, employer runbook or SOP documentationField log shows a minimum of 108 hours of dated, task-level entries; mentor mid-placement evaluation rates the student at 'Meets Expectations' or higher on accuracy, professionalism, and safety compliance on the employer rubric (minimum passing score: 70% on each rated dimension).
3Mentor-Assigned Applied Project81fieldThe student plans, executes, and documents a focused applied project assigned by the employer mentor—such as automating a backup report, migrating a schema, building a small ETL pipeline, or auditing user permissions—and delivers a brief written project summary.
  1. In consultation with the mentor, define project scope with a written one-page plan stating the business problem, tools to be used, steps, success criteria, and connection to at least one certification exam domain; obtain mentor approval before beginning work.
  2. Execute the project across the allocated hours, committing work to a version-controlled repository or employer-approved documentation system, and maintain a daily progress note (3–5 sentences) in the field log describing what was accomplished, any obstacles encountered, and how they were resolved.
  3. Present a 10–15 minute verbal summary of the completed project to the mentor (and optionally additional team members), covering the problem statement, approach, outcome, and lessons learned; submit a written project summary (1–2 pages) that the mentor reviews and signs.
Employer RDBMS and automation environment, version control system (Git or employer equivalent), field log workbook, project plan template (provided by program), employer runbook or SOP documentationMentor signs the project plan before work begins; written project summary is submitted and mentor rates project quality at 'Meets Expectations' or higher on the employer rubric; field log shows daily progress notes for all project hours. Pass: mentor sign-off on summary and rubric score of 70% or higher.
4Final Evaluation & Professional Reflection30fieldThe student completes the employer's final competency evaluation, consolidates and submits the complete field log, and writes a structured professional reflection mapping worksite experiences to certification exam domains and identifying personal development priorities.
  1. Schedule and complete the employer's end-of-placement evaluation meeting with the mentor, during which the mentor rates the student on all rubric dimensions (technical skill, reliability, communication, safety/security compliance, and professional conduct); the student receives verbal feedback and signs the completed rubric.
  2. Compile and submit the full field log to the program coordinator, ensuring all entries are dated, all mentor sign-offs are present, and total hours are accurately tallied to confirm the 243-hour requirement is met.
  3. Write a 2–3 page structured professional reflection addressing: (a) three specific tasks or incidents experienced at the site and how each maps to a PostgreSQL CE, Oracle DBA CA, DP-300, or DAMA CDMP exam domain; (b) one area of strength demonstrated during the placement; (c) one skill gap identified and a concrete plan to address it before certification exams.
Employer final evaluation rubric, complete field log workbook, program hour-verification form, reflection prompt guide (provided by program)Employer rubric is fully completed and signed by mentor with an overall score of 70% or higher across all dimensions; field log totals 243 verified hours with mentor signatures; professional reflection is submitted and program coordinator confirms all three required reflection elements are addressed with sufficient specificity. Pass: all three conditions met.
Assessments
AssessmentTypeWeightPass standardMethod & rubric
Employer Competency Evaluation (Skills Demonstration)Skills demonstration70%A score of 70% or higher on each rated dimension of the employer evaluation rubric, signed by the supervising mentor at the conclusion of the placement.The employer mentor completes a structured rubric rating the student's demonstrated technical skills (backup/recovery, user management, query work, ETL or automation tasks), reliability, communication, adherence to site security policies, and professional conduct across the full placement. This live-environment skills demonstration directly reflects the hands-on competency areas assessed by the PostgreSQL CE, Oracle DBA CA, DP-300, and DAMA CDMP credentials.
Competency · Safety · Attendance · Conduct · Initiative
Field Log Portfolio (Lab Log)Log30%All 243 hours documented with dated, task-level entries; all required mentor sign-offs present; program coordinator review rated as Complete and Satisfactory.The student submits the complete field log as a professional portfolio artifact containing daily task records, meeting summaries, trouble-ticket documentation, project progress notes, and certification exam-domain mappings accumulated across all four placement phases. The program coordinator audits the log for completeness, specificity of entries, and accuracy of hour totals; a log that is missing entries, lacks mentor signatures, or contains hours that cannot be verified does not pass and requires remediation before the credential can be awarded.
Complete · Verified
TEC-DATA86-12 Exam prep

Certification Exam Preparation: PostgreSQL CE, Oracle DBA CA, Microsoft DP-300, and DAMA CDMP Associate

68 hr · $680 COMPLIMENTARY

This course systematically reviews every domain tested on the PostgreSQL CE (EDB), Oracle DBA CA, Microsoft DP-300, and DAMA CDMP Associate exams, using targeted content review, worked practice questions, and timed full-length mock exams. Students identify personal weak areas through diagnostic scoring, then close gaps through focused drills before sitting their chosen credential exam. Exam registration logistics, test-day strategy, and professional portfolio completion are also covered.

Outcomes
Course text

This course systematically reviews every domain tested on the PostgreSQL CE (EDB), Oracle DBA CA, Microsoft DP-300, and DAMA CDMP Associate exams, using targeted content review, worked practice questions, and timed full-length mock exams. Students identify personal weak areas through diagnostic scoring, then close gaps through focused drills before sitting their chosen credential exam. Exam registration logistics, test-day strategy, and professional portfolio completion are also covered.

How the course runs. 4 blocks: Diagnostic Assessment and Exam Domain Mapping; PostgreSQL CE and Oracle DBA CA Domain Review; Microsoft DP-300 and DAMA CDMP Associate Domain Review; Full-Length Timed Mock Examinations and Exam Readiness Certification.

What competent looks like. Map personal knowledge gaps to specific exam domains across all four credentials using diagnostic practice tests and adjust a study plan accordingly. Demonstrate command of PostgreSQL CE exam topics including installation, configuration, performance tuning, high availability, and security as defined by EnterpriseDB's published exam objectives. Answer Oracle DBA CA exam-level questions covering Oracle database architecture, instance management, storage structures, backup and recovery with RMAN, and user security. Solve Microsoft DP-300 exam scenarios involving deploying, securing, monitoring, and optimizing Azure SQL, Azure SQL Managed Instance, and SQL Server on Azure Virtual Machines. Respond correctly to DAMA CDMP Associate exam questions spanning data governance, data quality, data modeling, master data management, and related DAMA-DMBOK2 knowledge areas. Complete timed, full-length mock exams for each credential under realistic conditions and score at or above each credential's published passing threshold before the program ends.

Lessons · 4 blocks
#LessonHrTypeObjectiveActivitiesMaterialsCheck
1Diagnostic Assessment and Exam Domain Mapping10practiceStudents complete a scored diagnostic practice test for each of the four credentials and produce a written gap-analysis study plan that prioritizes their lowest-scoring domains.
  1. Take a timed 30-to-40-question diagnostic practice test for each credential (PostgreSQL CE, Oracle DBA CA, DP-300, DAMA CDMP Associate) using published exam objective outlines from EnterpriseDB, Oracle, Microsoft Learn, and DAMA International as the domain framework.
  2. Score each diagnostic immediately, then color-code results against official domain weightings to identify which topic areas fall below 70% correct, and discuss score patterns with the instructor.
  3. Draft a personalized study plan that lists each credential's exam domains in priority order from weakest to strongest, assigns review hours from the remaining lessons, and records target score benchmarks for each mock exam.
Diagnostic practice-question banks aligned to each credential's published objectives; official exam blueprint PDFs from EnterpriseDB, Oracle University, Microsoft Learn, and DAMA International; spreadsheet or printed domain-scoring template; student personal study-plan worksheetStudent submits a completed gap-analysis study plan that correctly names every domain for each credential, highlights domains below 70% on the diagnostic, and assigns specific review priorities; instructor verifies all four diagnostics were attempted under timed conditions — pass requires submission of all four scored diagnostics and an approved study plan.
2PostgreSQL CE and Oracle DBA CA Domain Review18theoryStudents review and accurately explain the high-weight exam domains for the PostgreSQL CE (EDB) and Oracle DBA CA credentials, working through representative exam-style questions for each domain.
  1. Work through instructor-led review sessions covering PostgreSQL CE domains: server installation and configuration parameters, authentication methods (pg_hba.conf), VACUUM and autovacuum, query planning and EXPLAIN output, logical and streaming replication, pg_dump and pg_basebackup backup strategies, and role-based access control — completing 15-to-20 practice questions per domain with answer explanations.
  2. Work through Oracle DBA CA review covering Oracle instance and database architecture (SGA, PGA, background processes), tablespace and datafile management, undo and redo log management, RMAN backup and recovery commands, Oracle user privileges and roles, and Data Guard concepts — completing 15-to-20 practice questions per domain with answer explanations.
  3. Pair with a classmate to quiz each other using flashcard sets built from incorrect answers on the diagnostic; each pair writes three original exam-style questions per credential and shares them with the class for group discussion.
EnterpriseDB PostgreSQL CE exam guide and sample questions (official or instructor-curated); Oracle Database Concepts documentation; Oracle Database Backup and Recovery User's Guide; RMAN command reference; flashcard software (Anki or printed cards); instructor-prepared domain review slide decks; PostgreSQL 16 documentation (postgresql.org)Domain knowledge quiz of 40 questions (20 PostgreSQL CE, 20 Oracle DBA CA) drawn from covered material; students must score at least 75% overall and no lower than 70% on any single credential's subset to demonstrate balanced readiness — results are recorded on the student's progress tracker.
3Microsoft DP-300 and DAMA CDMP Associate Domain Review20theoryStudents review and accurately explain the high-weight exam domains for the Microsoft DP-300 and DAMA CDMP Associate credentials, practicing scenario-based and concept-based questions that match each exam's published format.
  1. Work through DP-300 domain review using Microsoft Learn modules as the framework: planning and implementing database deployments on Azure (Azure SQL Database, Managed Instance, SQL Server on Azure VM), configuring and managing security (Microsoft Entra authentication, transparent data encryption, dynamic data masking, auditing), monitoring and optimizing operational resources (Query Store, wait statistics, index maintenance, Intelligent Query Processing), and configuring high availability and disaster recovery (geo-replication, failover groups, automated backup and point-in-time restore) — completing 15-to-20 scenario-based practice questions per domain with explanations.
  2. Work through DAMA CDMP Associate review organized around DAMA-DMBOK2 knowledge areas at the level tested on the Associate exam: data governance (roles, policies, stewardship), data quality (dimensions of quality, profiling, remediation), data modeling and design (conceptual, logical, physical), reference and master data management, data warehousing and business intelligence concepts, and metadata management — completing 15-to-20 concept-based questions per knowledge area.
  3. Students individually complete a timed 50-question mixed practice set that samples all four credentials' domains proportionally, then review every incorrect answer by locating the source passage in the official reference (Microsoft Learn page, DAMA-DMBOK2 chapter, PostgreSQL docs page, or Oracle docs page) and writing a one-sentence explanation in their own words.
Microsoft Learn DP-300 learning path (learn.microsoft.com); Microsoft DP-300 exam skills outline (official, current version); Azure portal student access or Azure free-tier account; DAMA-DMBOK2: Data Management Body of Knowledge, 2nd edition; DAMA CDMP Associate exam content outline (dama.org); instructor-prepared scenario-based question sets; student answer-explanation notebookDomain knowledge quiz of 50 questions (25 DP-300 scenario-based, 25 DAMA CDMP Associate concept-based) drawn from covered material; students must score at least 75% overall and no lower than 70% on either credential's subset — scores below threshold in any area require completion of a targeted 30-minute instructor-guided remediation drill on the failing domain before moving to the mock exam lesson.
4Full-Length Timed Mock Examinations and Exam Readiness Certification20practiceStudents sit full-length, timed mock exams that replicate the format and domain weighting of each chosen credential exam, score at or above the credential's published passing threshold, and complete all remaining exam registration and portfolio tasks.
  1. Sit two complete timed mock exams on separate days: each mock covers all domains of the student's primary target credential at the published question count and time limit (using the most current official exam guide for question count and time); exams are administered under closed-note, no-assistance conditions using a locked-browser quiz platform or printed mock booklet, and scored immediately after the allotted time expires.
  2. Conduct a structured debrief after each mock exam: students compare scores against the credential's published passing score, identify any domain still below passing level, complete a focused 45-minute drill on each under-performing domain using targeted practice questions, then discuss test-taking strategies (time management, process-of-elimination, flagging uncertain items for review) with the instructor.
  3. Complete all pre-exam logistics: confirm identity documents required at the testing center or for online proctoring, register for the credential exam through the official vendor portal (EnterpriseDB, Oracle University, Microsoft/Certiport, or DAMA International), verify testing accommodation requests if applicable, assemble the final professional portfolio (resume, externship employer evaluation, capstone documentation) for submission, and complete a brief exit interview with the instructor confirming readiness.
Full-length mock exam question banks for each credential (instructor-curated or licensed from a recognized test-prep provider, aligned to current official exam objectives); locked-browser quiz software or printed mock exam booklets; timer; official exam registration portals (entrepdb.com, oracle.com/education, microsoft.com/en-us/learning, dama.org); student professional portfolio folder; externship employer evaluation form; instructor readiness checklistStudents must achieve a score at or above each credential's currently published passing threshold on at least one full-length mock exam for their primary target credential before the course is marked complete; students who do not reach the threshold on the first mock receive targeted remediation and must re-attempt the mock; final course pass requires: mock exam score at or above passing threshold, confirmed exam registration, and submitted professional portfolio — all three requirements must be met.
Assessments
AssessmentTypeWeightPass standardMethod & rubric
Full-Length Timed Mock Certification ExamsMock certification exam100%Score at or above the currently published passing threshold for the student's primary target credential on at least one full-length timed mock exam administered under closed-note, proctored conditions; students who do not pass the first mock must complete targeted domain remediation and pass a second mock attempt before the program end date.Each student sits full-length, timed mock exams that replicate the format, domain weighting, and time constraints of the actual credential exam for their primary target credential (PostgreSQL CE, Oracle DBA CA, Microsoft DP-300, or DAMA CDMP Associate); exams are scored immediately and results are documented on the student's progress record alongside confirmed exam registration status and a completed professional portfolio, all three of which are required for program completion.
Score · Time management
Program completion

External credential: DAMA CDMP Associate; Microsoft DP-300; Oracle DBA CA; PostgreSQL CE (EDB)

Students sit the EnterpriseDB PostgreSQL CE exam (administered by EnterpriseDB), the Oracle Database Administration Certified Associate exam (administered by Oracle), the Microsoft DP-300 Administering Microsoft Azure SQL Solutions exam (administered by Microsoft through Pearson VUE), and the DAMA CDMP Associate exam (administered by DAMA International). Pass standard: Credential issued by the body.

Back to Data Management / Database Administration · How the school gets authority to award these credentials