Defense Preparation, Dry Run, and Final Presentation

Defense Preparation, Dry Run, and Final Presentation

The capstone defense is the culminating assessment of your Data Management / Database Administration program. It gives you the opportunity to demonstrate, in a live professional setting, that you can design, build, explain, and troubleshoot a production-quality database system. The defense format—a structured presentation followed by examiner questions and a live troubleshooting drill—mirrors the skills assessed by the PostgreSQL CE, Oracle DBA CA, Microsoft DP-300, and DAMA CDMP Associate credentials you are preparing to sit.

Structure of the Defense

Your defense runs approximately 40 minutes total. The first 20 minutes are your formal slide presentation. The remaining time includes at least 10 minutes of examiner questions and, separately, a 30-minute live troubleshooting drill that may be scheduled before or after the presentation at your program's discretion.

Your slide presentation must cover seven areas in a logical sequence:

1. Business requirements – What problem does your system solve? Who are the stakeholders and what are their data needs?

2. Architecture decisions – Why did you choose the database engine, hosting model, and schema structure you used? What trade-offs did you evaluate?

3. Security design – How are roles, permissions, and encryption implemented? What attack surfaces did you address?

4. ETL pipeline logic – How is data extracted, transformed, and loaded? Where are validation rules enforced?

5. Governance artifacts – What data dictionary, lineage documentation, or data quality rules did you produce?

6. Lessons learned – What did not work as planned, and what would you do differently?

7. Next-iteration improvements – Given more time or resources, what would you add or refactor?

Keep each section concise. Practice transitions so that you cover all seven areas within 20 minutes without rushing.

The Dry Run

Before your panel defense, you will conduct a full timed rehearsal with a peer acting as evaluator. Your peer uses the same defense scoring rubric the panel will use. After the dry run, your peer provides written feedback on every rubric section. Take that feedback seriously—it is your clearest signal of where the panel will probe. Common issues include:

• Skipping the rationale for architecture decisions (a key area for DP-300 and Oracle DBA CA)
• Describing security controls without explaining why those specific controls were chosen (tested by PostgreSQL CE and DP-300)
• Presenting governance artifacts without connecting them to a data management framework (a CDMP Associate domain area)
• Speaking too quickly when demonstrating the ETL pipeline

Revise your deck and talking points based on the written feedback before the live defense.

The Live Troubleshooting Drill

The instructor will inject three faults into a copy of your database. You must diagnose and resolve each fault on-screen while narrating your reasoning aloud. Typical fault categories include:

• Constraint violations – A broken foreign key constraint that causes insert or update failures. Start by querying the information schema or system catalog to identify which constraint is violated, confirm the referential integrity issue, and apply the correct fix (either correcting the data or re-establishing the constraint).
• Backup job failure – A scheduled backup job that has not completed. Check the job log or agent log, identify the error message, confirm storage paths and permissions, and demonstrate that a valid backup can be produced.
• Misconfigured role permission – A user who cannot perform an expected operation. Query the role membership and privilege views, identify the missing grant, and apply the minimum necessary privilege to restore function without over-granting access.

Narrating your reasoning is as important as the fix itself. Evaluators are assessing your diagnostic process, not just the outcome. Resolve at least two of the three faults to meet the passing threshold.

Examiner Questions

After your presentation, the panel will ask at least 10 minutes of questions drawn from the four credential exam domains. Expect at least one question on each of these areas:

• Data modeling – Normalization, entity-relationship design, or schema evolution
• Security – Role-based access control, encryption at rest and in transit, auditing
• Backup and recovery – Recovery point objectives, recovery time objectives, backup verification
• ETL – Transformation logic, error handling, idempotency
• Data governance – Data stewardship, data quality metrics, metadata management

Answer directly and precisely. If a question touches something your system does not implement, acknowledge the gap and explain how you would address it. Panels value honesty and structured thinking over overconfidence.

Scoring and the Passing Standard

The rubric scores five sections: technical accuracy, documentation quality, communication clarity, troubleshooting performance, and response to questions. You must earn a composite score of 80% or higher across all sections and resolve at least two of the three injected faults to pass. A failed defense may be retaken according to your program's retake policy.

Professional Conduct and Safety Considerations

Although database work is office-based, standard data center and lab safety practices apply. Workstation ergonomics matter for sustained focus—adjust your chair, monitor height, and keyboard position before the session begins. Ensure that you are operating only on the designated copy of your database; never run destructive commands on a production or shared system. Follow your program's acceptable-use policy throughout the defense. Treat your credentials and any demonstration data containing personal information with the same care required by applicable data privacy principles—do not expose real personal data in your live demonstration.