Presentation Delivery and Audience Engagement

Introduction

A technically accurate presentation can still fail if the speaker is difficult to hear, appears uncertain, moves too quickly, or cannot respond constructively to questions. Presentation delivery is therefore not an ornamental skill added after content development; it is the process through which knowledge becomes understandable, credible, and useful to an audience.

For full stack developers, delivery skills are essential in sprint reviews, client demonstrations, technical interviews, architecture discussions, incident briefings, project pitches, and team meetings. Developers frequently explain invisible systems: application logic, APIs, databases, deployment pipelines, security controls, and user experience decisions. Effective delivery makes these systems visible through language, structure, demonstration, and interaction.

This chapter examines the practical and theoretical foundations of confident delivery. It focuses on voice, pacing, posture, demonstrations, storytelling, audience participation, question handling, rehearsal, anxiety management, and technical failure. The goal is not to produce theatrical performers. It is to develop professionals who can communicate accurately and persuasively under realistic conditions.

Learning Objectives

By the end of this chapter, students should be able to:

1. Explain how vocal, physical, and verbal behaviours affect audience understanding.
2. Use pacing, pauses, emphasis, and signposting to improve clarity.
3. Design and deliver an effective software demonstration.
4. Apply storytelling structures to technical presentations.
5. Diagnose audience needs and select suitable engagement techniques.
6. Answer questions accurately without becoming defensive or misleading.
7. Use rehearsal methods to improve performance and reduce uncertainty.
8. Manage presentation anxiety ethically and practically.
9. Respond to technical failures while preserving audience trust.
10. Evaluate delivery using evidence rather than impression alone.

1. Delivery as Meaning-Making

Presentation delivery is the coordinated use of verbal language, vocal expression, physical behaviour, visual support, and interaction. These elements influence one another. A well-designed slide does not compensate for an inaudible voice, and energetic delivery does not compensate for inaccurate claims.

A useful model is the delivery system:

Message → Delivery behaviours → Audience processing → Feedback → Adjustment

The audience does not simply receive information. Members interpret, compare, question, and selectively remember it. Their processing is affected by prior knowledge, attention, expectations, status relationships, culture, accessibility needs, and the perceived credibility of the presenter.

Delivery should therefore answer four questions:

• What must the audience understand?
• Why does it matter to them?
• What evidence or demonstration supports it?
• What should they think, decide, or do next?

Audience-centred design

Audience analysis should occur before rehearsal. A technical audience may understand terms such as REST, containerisation, or schema migration, whereas a client or executive audience may need those concepts translated into effects on cost, risk, speed, or user experience. The same content may require different vocabulary, examples, demonstrations, and levels of detail.

A practical audience profile includes:

Audience-centred delivery does not mean telling people only what they want to hear. It means presenting accurate information in a form that enables them to understand and use it.

2. Vocal Delivery

The voice is a primary channel of meaning. Vocal delivery includes volume, pitch, rate, articulation, pronunciation, pauses, and emphasis.

Volume and projection

Volume should be sufficient for every listener without creating discomfort. Projection is not the same as shouting. It involves breath support, clear articulation, and directing sound toward the audience. In online presentations, microphone position, room noise, and audio compression also influence intelligibility.

Before beginning, test the microphone from the actual speaking position. Avoid speaking directly into a sensitive microphone, and use headphones or a second device when possible to detect distortion.

Pitch and vocal variety

Pitch variation helps distinguish important ideas and prevents a monotonous delivery. Excessive variation, however, can sound artificial. A lower or more measured pitch may communicate seriousness, while a modest rise can signal a question or transition. Vocal variety should serve meaning rather than imitate a performance style.

Rate and cognitive load

Speaking too quickly increases the processing burden on listeners, especially when the subject contains unfamiliar terms. Speaking too slowly can reduce energy and make relationships between ideas harder to follow. Complex concepts deserve slower explanation, examples, and pauses; familiar transition material can move more quickly.

A speaker should not aim for a single ideal speed. The appropriate rate changes according to content difficulty, audience expertise, language, room acoustics, and emotional importance.

Pauses

A pause can separate sections, highlight a conclusion, allow an audience to interpret a diagram, or create space before answering a question. Silence is not necessarily evidence of poor preparation. Deliberate pauses often communicate control.

Useful pauses include:

• Transition pause: before moving to a new section.
• Emphasis pause: before or after a key claim.
• Processing pause: after a complex explanation or demonstration.
• Response pause: before answering a difficult question.

Articulation and signposting

Technical presentations contain abbreviations, product names, code, and specialised vocabulary. Define unfamiliar terms on first use and pronounce important names consistently. Signposting makes structure audible: “First, we will examine the problem. Next, I will demonstrate the solution. Finally, we will consider its limitations.”

3. Pacing and Attention Management

Pacing is broader than speaking rate. It includes the rhythm of explanation, movement between slides, demonstrations, questions, pauses, and changes in activity.

A presentation can be understood as alternating periods of input and processing. When information is dense, the speaker should create processing opportunities through a question, brief recap, visual focus, example, or pause. These interventions reduce passive listening.

A useful micro-structure is:

1. State the point.
2. Explain or show it.
3. Give an example.
4. Check or reinforce understanding.
5. Transition to the next point.

For example: “The system uses caching to reduce repeated database queries. In practice, a product catalogue request can be served from memory rather than recomputed each time. The result is lower response time, although stale data becomes a risk. We will now examine how the design controls that risk.”

Avoid filling every silence with “um,” “okay,” or “so.” A short pause is usually more professional than a stream of fillers. Recording a rehearsal can reveal habitual fillers that the speaker cannot notice while presenting.

4. Posture, Eye Contact, and Movement

Nonverbal delivery affects attention and perceived confidence, but there is no universal body-language formula. Cultural norms, disability, neurodiversity, physical space, and online conditions must be respected.

Posture

A stable, balanced posture supports breathing and makes gestures easier. Keep the shoulders relaxed, avoid locking the knees, and face the audience rather than the screen. Sitting can be appropriate online or in a meeting; the essential requirement is visible attentiveness and clear framing.

Eye contact and visual attention

Eye contact should be distributed across the audience rather than fixed on one person. In a large room, look at different regions. In a video conference, alternate between the camera and the participant gallery according to the communicative purpose. Reading continuously from notes or slides weakens connection and often causes a downward-facing voice.

Gesture

Gestures can illustrate size, sequence, contrast, direction, or emphasis. They should be visible, purposeful, and consistent with the message. Repetitive movements—clicking a pen, rocking, touching hair, or pacing without purpose—can distract attention. The solution is not to become rigid; it is to replace unconscious movement with intentional movement.

Movement

Move when the purpose changes: for example, when shifting from problem to solution or from explanation to demonstration. Avoid walking while delivering a precise definition or while the audience is reading a complex diagram. In online settings, movement should be limited by camera framing and lighting.

5. Demonstrating Software and Technical Systems

A demonstration is not a tour of every feature. It is evidence that supports a claim. A strong demonstration has a user goal, a scenario, a sequence, and a success condition.

Demonstration planning

Before presenting, identify:

• The user or stakeholder involved.
• The problem being addressed.
• The starting state.
• The minimum sequence needed to show value.
• The expected result.
• The risks and likely failure points.

For instance, rather than clicking through an entire web application, demonstrate how a support agent finds a customer, updates a ticket, and receives confirmation. This sequence connects interface behaviour to a meaningful work outcome.

Narrating action and significance

Explain both what is happening and why it matters. “I am submitting the form” describes action; “Client-side validation catches the missing email before a network request is sent” explains significance. Avoid narrating every mouse movement. Describe decisions, system responses, and user benefits.

Demonstration reliability

Use a prepared data set, a stable environment, and a backup recording or screenshot sequence. Remove unnecessary notifications, personal information, browser tabs, API keys, and confidential records. Never expose passwords, tokens, customer data, or production credentials during a demonstration.

A demonstration should also state boundaries. If a feature is simulated, say so. If the environment is a prototype, do not imply production readiness. Accuracy builds more trust than exaggerated confidence.

6. Storytelling for Technical Communication

Storytelling is not the invention of facts. It is the organisation of facts into a meaningful sequence. Technical audiences often remember a problem, decision, consequence, and lesson more easily than a list of features.

A practical technical story contains:

1. Context: Who is affected and under what conditions?
2. Tension: What problem, risk, constraint, or failed assumption exists?
3. Decision: What alternatives were considered?
4. Action: What was designed or implemented?
5. Evidence: What changed, and how is the claim supported?
6. Reflection: What remains uncertain or should happen next?

For example, a presentation about database indexing might begin with a user complaint about slow search, explain the observed query pattern, describe alternative indexing strategies, demonstrate the selected index, and conclude with the trade-off in storage and write performance.

Stories should not conceal limitations. A credible technical narrative includes setbacks and constraints. The purpose is to create causal understanding, not emotional manipulation.

7. Audience Engagement

Engagement means meaningful cognitive or communicative involvement, not merely entertainment. The audience may engage by predicting an outcome, interpreting evidence, asking questions, comparing alternatives, or making a decision.

Engagement techniques

• Opening question: reveals relevance or activates prior knowledge.
• Prediction: asks what the system will do before a demonstration.
• Poll: gathers views or checks understanding.
• Think-pair-share: allows individuals to formulate an answer before discussion.
• Checkpoint: asks the audience to identify the main risk or next step.
• Worked example: makes an abstract principle concrete.
• Choice point: invites comparison between design alternatives.

Select techniques according to purpose. A poll is useful when responses will affect the discussion; it is not useful as decoration. Questions should be answerable within the available time and should not embarrass participants.

Managing participation

Set expectations at the beginning: questions may be taken throughout, at section breaks, or at the end. For large or online groups, use chat moderation, a visible queue, or a designated question facilitator. Repeat questions so all participants can hear them and so the speaker can confirm interpretation.

Engagement must also be inclusive. Do not equate silence with agreement, or rapid verbal participation with understanding. Provide multiple ways to contribute, including written questions and anonymous polling when appropriate.

8. Handling Questions Professionally

Question handling tests knowledge, listening, judgement, and interpersonal control. The objective is not to answer instantly; it is to provide a useful and truthful response.

A reliable response sequence is:

1. Listen without interrupting.
2. Pause and identify the question’s scope.
3. Paraphrase if ambiguity exists.
4. Answer the central point directly.
5. Provide evidence, an example, or a qualification.
6. State the next step if the issue cannot be resolved immediately.

Useful response forms include:

• “The short answer is …”
• “There are two parts to that question …”
• “I do not have verified data for that point, so I do not want to speculate.”
• “That behaviour depends on the deployment configuration.”
• “I will confirm the exact figure and send it after the session.”

Do not evade a valid challenge by attacking the questioner. Do not invent an answer to appear competent. Distinguish facts, assumptions, estimates, and opinions. If a question reveals a flaw, acknowledge it and explain the corrective action.

9. Rehearsal and Performance Improvement

Rehearsal is a process of testing communication, not memorising every sentence. Over-memorisation can make a speaker panic when one word is forgotten. Instead, memorise the opening, central message, transitions, demonstration checkpoints, and conclusion. Use brief prompts for supporting details.

Rehearsal stages

Content rehearsal: Verify accuracy, sequence, timing, examples, and evidence.

Delivery rehearsal: Practise voice, posture, gestures, eye contact, and transitions.

Technical rehearsal: Test display, audio, network access, software state, links, permissions, and backup materials.

Audience rehearsal: Present to a colleague who resembles the target audience and request specific feedback.

A useful feedback framework is:

• What was clear?
• Where did attention decline?
• Which claim lacked evidence?
• What should be shortened?
• What question remained unanswered?

Recordings can provide objective evidence, but they should be reviewed selectively. Examine opening clarity, pace, fillers, slide dependence, audible transitions, and response to questions. Avoid judging appearance through vague self-criticism; focus on observable behaviours.

Timing

If a presentation must fit a fixed duration, rehearse with a margin. A speaker who plans exactly to the limit has no capacity for questions, technical delays, or audience interaction. Prepare an optional section that can be omitted and identify the essential argument that must remain.

10. Anxiety and Confidence

Presentation anxiety is common and does not necessarily indicate poor competence. Anxiety can arise from evaluation, uncertainty, status differences, perfectionism, unfamiliar technology, or previous negative experiences. Confidence should be understood as prepared willingness to act despite uncertainty, not the complete absence of nervousness.

Practical strategies include:

• Prepare the first minute thoroughly.
• Arrive early enough to inspect the environment.
• Use slow breathing and grounded posture before speaking.
• Replace catastrophic predictions with specific preparation tasks.
• Focus attention on audience benefit rather than self-monitoring.
• Use notes that prompt ideas rather than full paragraphs.
• Practise the difficult section more than the familiar section.
• Build gradual exposure through low-risk speaking opportunities.

Anxiety management should not become a demand for emotional concealment. Institutions should provide accessible environments, reasonable preparation time, and alternatives where disability or health conditions require them. Medication or clinical treatment should be discussed with qualified professionals, not treated as a presentation technique.

11. Managing Technical Failure

Technical failure is a communication event as well as an operational event. The audience evaluates how the speaker responds.

Prepare a failure plan with three levels:

1. Primary path: the intended live presentation or demonstration.
2. Secondary path: local copies, screenshots, recorded demonstrations, or a static prototype.
3. Narrative path: an explanation of the expected workflow, evidence, limitations, and next step if no visual system is available.

When failure occurs, pause rather than clicking repeatedly. State the situation briefly: “The live environment is not responding, so I will switch to the recorded workflow.” Protect confidential information and do not expose credentials while troubleshooting. If the failure changes the validity of a claim, say so.

A useful recovery sequence is:

Acknowledge → Stabilise → Substitute → Continue → Follow up

Do not blame colleagues, the venue, or the audience. Technical explanations should be proportional to the problem. The audience generally needs to know what happened, what evidence remains valid, and what will happen next.

12. Ethics, Accessibility, and Professional Responsibility

Presentation delivery involves power. Speakers may control access to information, influence decisions, and shape perceptions of risk. Ethical delivery requires accuracy, transparency, respect, and accountability.

Important responsibilities include:

• Distinguish measured results from expectations.
• Disclose relevant limitations, conflicts of interest, and security risks.
• Obtain permission before showing user data or confidential screens.
• Avoid discriminatory examples, stereotypes, and humiliating participation practices.
• Provide captions, readable contrast, meaningful headings, and descriptions of important visuals.
• Do not use artificial intelligence to fabricate evidence, testimonials, or performance results.
• Check AI-generated demonstrations, scripts, and explanations because fluent output may contain errors or insecure practices.

Accessibility is not merely a compliance exercise. Captions help people in noisy environments; clear structure helps all listeners; descriptive explanations benefit those who cannot see a screen. Design for diverse participation from the beginning.

Applied Case: Illustrative Full Stack Product Demonstration

Background

A student development team has built “CampusFix,” a web application through which university students report maintenance problems. The team must present the application to facilities managers, who care about response time, duplicate reports, workload, and data privacy.

Problem

The initial rehearsal is unsuccessful. One presenter reads from slides, the live demo begins with an empty database, technical terms are unexplained, and a manager asks how the system prevents unauthorised access. The team answers with a vague statement that security was “considered.”

Analysis

The problem is not primarily the software. The delivery lacks audience relevance, narrative sequence, evidence, and contingency planning. The audience needs to understand the operational workflow and the associated risks, not the order in which the developers wrote components.

Approach and solution

The team redesigns the presentation around a single scenario: a student reports a broken light, a facilities coordinator assigns the work, and the student receives an update. The presentation begins with the operational problem, then explains the user roles and demonstrates the workflow using prepared but fictional records.

The team replaces implementation jargon with functional explanations, while retaining technical detail in an optional section. It explains authentication, authorisation, input validation, and audit logging accurately. It states that the prototype has not undergone a formal penetration test. A local backup video and screenshots are prepared, and all demonstration data are synthetic.

During rehearsal, one member plays the facilities manager and asks questions about duplicate reports, notification failure, and retention of personal data. The presenters prepare direct answers and identify questions requiring follow-up.

Outcome

The revised presentation is shorter but more informative. Managers can identify the value of the workflow, understand the security boundary, and distinguish current capability from future work. When the live notification service fails during the final presentation, the team acknowledges the issue, shows the prepared evidence, and explains the recovery design without claiming that the live feature worked.

Learning points

1. Demonstrations should represent stakeholder tasks, not software menus.
2. Technical credibility depends on acknowledging limits.
3. Prepared alternatives reduce the communication impact of technical failure.
4. Rehearsal should include hostile, confused, and practical questions.
5. Audience engagement improves when participants can see consequences in their own context.

Challenges and Limitations

No delivery technique guarantees audience attention. A highly skilled speaker cannot overcome irrelevant content, poor evidence, or organisational mistrust. Audience participation may also be affected by hierarchy, culture, language, disability, fatigue, or fear of being judged.

Storytelling may oversimplify complex systems if causal claims are compressed too aggressively. Live demonstrations create authenticity but also introduce operational risk. Rehearsal improves reliability but cannot reproduce every real-world condition. Confidence techniques may help ordinary nervousness but are not substitutes for professional mental-health support when anxiety is severe or disabling.

Evaluation should therefore consider both delivery and substance. A polished performance that leads an audience to an unsafe or inaccurate conclusion is not a successful presentation.

Contemporary Developments

Hybrid and remote presentations require deliberate management of audio, chat, screen sharing, and unequal participation. Shorter segments, visible agendas, captions, and planned interaction are increasingly important. Collaborative tools can enable live annotation and polling, but technology should serve the learning or decision objective.

Artificial intelligence can support rehearsal by generating likely questions, transcribing practice sessions, or identifying repeated fillers. It should be used as an aid rather than an authority. Presenters remain responsible for verifying technical claims, protecting confidential information, and disclosing synthetic material when its nature could affect trust.

Best-Practice Checklist

Before presenting, confirm that:

• The audience, purpose, and desired outcome are explicit.
• The opening establishes relevance quickly.
• The main claim is supported by evidence or a transparent demonstration.
• Technical terms are defined for the actual audience.
• Voice, pace, pauses, posture, and movement have been rehearsed.
• The demonstration uses safe, prepared data.
• Questions and uncertain points have been anticipated.
• Captions, readable visuals, and alternative formats are available.
• A backup exists for network, software, display, and audio failure.
• The conclusion states the decision, action, or next step.

Chapter Summary

Effective presentation delivery is a coordinated communication system involving verbal content, vocal behaviour, physical presence, visual support, interaction, and feedback. Delivery must be audience-centred: technical detail should be selected and explained according to the audience’s knowledge, purpose, concerns, and constraints.

Vocal clarity depends on suitable volume, purposeful pitch, controlled rate, articulation, pauses, and signposting. Posture, eye contact, gesture, and movement should support meaning without relying on rigid or culturally narrow rules. Demonstrations are strongest when organised around a stakeholder scenario and supported by prepared data, clear success conditions, and backup evidence.

Storytelling gives technical information a causal structure involving context, problem, decision, action, evidence, and reflection. Engagement should promote cognitive involvement through prediction, questions, examples, and choices. Questions should be answered directly and honestly, with uncertainty acknowledged rather than concealed.

Rehearsal tests content, delivery, technology, timing, and audience response. Anxiety can be managed through preparation, gradual exposure, attention to audience benefit, and appropriate support. Technical failures should be handled through acknowledgement, stabilisation, substitution, continuation, and follow-up. Finally, ethical and accessible delivery protects confidentiality, represents evidence accurately, respects diverse audiences, and avoids using technology or confidence as substitutes for truth.

Key Terms

Delivery: The verbal, vocal, physical, visual, and interactive execution of a presentation.

Audience analysis: Examination of an audience’s knowledge, purpose, concerns, context, and accessibility needs.

Projection: Producing a clear, adequately strong voice without shouting.

Pacing: Management of speaking rate, pauses, transitions, activity changes, and presentation rhythm.

Signposting: Verbal language that makes the structure and direction of a presentation explicit.

Processing pause: Silence that allows an audience to understand or interpret information.

Demonstration: A planned showing of a system or process used as evidence for a claim.

Success condition: The observable result that indicates whether a demonstration achieved its purpose.

Narrative: An organised sequence that connects context, events, decisions, and consequences.

Engagement: Meaningful cognitive or communicative involvement by an audience.

Inclusive participation: Providing fair and varied opportunities for audience members to contribute.

Paraphrase: Restating a question or idea to confirm understanding.

Rehearsal: Structured practice used to test content, delivery, technology, and timing.

Contingency plan: A prepared alternative for disruption or failure.

Technical failure: A malfunction of software, hardware, network, media, or access during a presentation.

Anxiety: A state of apprehension or physiological arousal associated with perceived threat or evaluation.

Accessibility: Design that enables people with differing abilities and circumstances to participate.

Cognitive load: The mental effort required to process information.

Professional credibility: Audience confidence based on accuracy, competence, transparency, and responsible conduct.

Review Questions

Short Answer Questions

1. Why should presentation delivery be considered part of meaning-making rather than merely performance?
2. Identify four vocal behaviours that influence audience understanding.
3. What is the difference between describing an action in a demonstration and explaining its significance?
4. List the stages of the recommended question-response sequence.
5. Why should a live technical demonstration have a secondary presentation path?

Long Answer Questions

1. Explain how audience analysis should influence the vocabulary, examples, evidence, and demonstration used in a full stack presentation.
2. Discuss the relationship between pacing, pauses, cognitive load, and audience engagement.
3. Compare the strengths and limitations of live demonstrations and recorded demonstrations.
4. Explain how rehearsal can be organised into content, delivery, technical, and audience stages.
5. Discuss the ethical responsibilities of a presenter who is communicating software security or performance claims.

Analytical / Application Questions

1. You must present a new API to both software engineers and non-technical managers. Design a two-part delivery strategy that preserves technical accuracy while meeting both groups’ needs.
2. During a client demonstration, the application stops responding and a screen containing test customer data appears. Explain the immediate actions you would take and the follow-up actions required.
3. Analyse a presentation you have recently observed or delivered. Identify one issue in vocal delivery, one issue in audience engagement, and one issue in evidence or ethics. Propose a measurable improvement for each issue.

Multiple Choice Questions with Answers

Question 1

Which practice most directly reduces the cognitive load created by unfamiliar technical content?

A. Increasing the number of animations on each slide

B. Defining specialised terms and using clear signposting

C. Speaking continuously without pauses

D. Reading every slide word for word

Correct Answer: B. Defining specialised terms and using clear signposting

Question 2

What is the primary purpose of a software demonstration in a professional presentation?

A. To display every available feature

B. To prove that the presenter can navigate menus quickly

C. To provide evidence related to a meaningful user or stakeholder goal

D. To replace all verbal explanation

Correct Answer: C. To provide evidence related to a meaningful user or stakeholder goal

Question 3

Which response is most professionally appropriate when a presenter does not know the verified answer to a question?

A. Invent a plausible answer to maintain confidence

B. Ignore the question and continue

C. State the uncertainty and explain how the answer will be confirmed

D. Tell the questioner that the issue is irrelevant

Correct Answer: C. State the uncertainty and explain how the answer will be confirmed

Question 4

Which sequence best describes an effective response to technical failure?

A. Blame, restart, conceal, and continue

B. Acknowledge, stabilise, substitute, continue, and follow up

C. Ignore, improvise, apologise repeatedly, and stop

D. Refresh continuously until the system works

Correct Answer: B. Acknowledge, stabilise, substitute, continue, and follow up

Question 5

Which rehearsal stage primarily verifies links, permissions, audio, network access, and software state?

A. Content rehearsal

B. Delivery rehearsal

C. Technical rehearsal

D. Audience rehearsal

Correct Answer: C. Technical rehearsal

Question 6

Why is a deliberate pause useful before answering a difficult question?

A. It prevents the audience from asking further questions

B. It creates time to interpret the question and formulate an accurate response

C. It makes technical content unnecessary

D. It guarantees that the answer will be accepted

Correct Answer: B. It creates time to interpret the question and formulate an accurate response

Question 7

Which example best represents inclusive audience engagement?

A. Calling on participants without warning and criticising incorrect answers

B. Allowing only the most senior participant to speak

C. Providing spoken, written, and anonymous ways to contribute where appropriate

D. Avoiding all questions to preserve timing

Correct Answer: C. Providing spoken, written, and anonymous ways to contribute where appropriate

Question 8

A presenter claims that a prototype is production-ready even though it has not undergone security testing. Which professional principle is violated most directly?

A. Transparency about limitations

B. Vocal variety

C. Movement control

D. Transition signposting

Correct Answer: A. Transparency about limitations

Question 9

What is the main advantage of organising a technical story around context, tension, decision, action, evidence, and reflection?

A. It eliminates the need for evidence

B. It creates a meaningful causal sequence that supports understanding

C. It ensures every presentation is entertaining

D. It allows the presenter to omit limitations

Correct Answer: B. It creates a meaningful causal sequence that supports understanding

Question 10

Which preparation is most appropriate for protecting sensitive information during a live application demonstration?

A. Use real production credentials so the system appears authentic

B. Display personal records to make the scenario realistic

C. Use synthetic data and remove credentials and confidential material

D. Disable all security controls temporarily

Correct Answer: C. Use synthetic data and remove credentials and confidential material