Quiz — Transform prototype into final publication

E6-Q1 Multiple choice

During a user trial, three participants become trapped behind a lift in Level 2 and cannot continue without restarting the game. Which action best treats this finding as a required publication-stage change?

Log a high-severity defect with evidence, acceptance criteria and regression checks. Treat it as a suggestion for a later sprint because only some players encountered it. Close it after the lift script is edited, without waiting for QA verification. Raise it at sign-off only, so reviewers can decide whether the risk is acceptable.

E6-Q2 Fill the gaps

A disciplined change request for a playtest issue should link the issue to , state the result from the specification or intended design, define criteria for QA, and send the fix for testing before closure.

E6-Q3 True or false

A user-trial defect can be marked closed as soon as its status is changed to 'Ready for test'.

True False

E6-Q4 Matching

Match each late-stage issue status to its most appropriate meaning.

Open

Assigned

Ready for test

Verified

Deferred

E6-Q5 Select all that apply

A team is preparing to integrate final 3-D game elements into the release build. Which checks should be included in the integration checklist? Select all that apply.

Select all that apply.

Confirm assets use approved formats, naming conventions, folder locations and import settings. Check scripts, prefabs, scenes, references and dependencies after merging content. Validate platform settings, input mappings and performance budgets for target hardware. Confirm lighting, texture sizes, polygon budgets and visual effects align with the visual design and hardware constraints. Import every file supplied by the team, even if it is unapproved or outside the GDD. Ignore licence and asset ownership checks until after distribution, because they do not affect whether the engine can load the build.

E6-Q6 Matching

Match each game asset or engine item to a typical format or representation used during integration.

3-D model mesh

Texture image

Audio clip

Unity reusable configured object

Unreal reusable scripted asset

E6-Q7 Multiple choice

A final build contains the 3-D model for a locked door, but players receive no prompt, no sound, no inventory check and no fallback message when they lack the key. What is the best assessment of this element?

It is not fully integrated; key gameplay and feedback links are missing. It is complete because the model renders in the scene and can be viewed by players. It is feature-complete because prompts, sound and fallback messages are only final polish. It should be deferred automatically, because locked-door interactions are never release blockers.

E6-Q8 True or false

A feature-complete build must have every required system present so QA can test the product as a whole, but it may still contain bugs that need fixing.

True False

E6-Q9 Matching

Match each final QA activity to the check it mainly performs.

Smoke testing

Functional testing

Regression testing

Compatibility testing

Performance testing

E6-Q10 Select all that apply

A release candidate must be checked against the approved navigation design. Which checks provide evidence that implemented sequences conform? Select all that apply.

Select all that apply.

Verify required entry and exit paths between screens, levels and states. Confirm failure, restart, pause, resume and return-to-menu paths recover correctly. Check that progress, settings and inventory persist as specified. Test menus with the required controller, keyboard and mouse input devices. Approve navigation if the lead designer remembers the intended flow and it seems close enough. Skip cutscene and loading transitions because they are presentation rather than navigation.

E6-Q11 Fill the gaps

To check a gameplay sequence, start from a , follow the , then test and confirm from failure states.

E6-Q12 Multiple choice

A final check report shows that all required menu paths work, but one unresolved defect sometimes prevents players from progressing after a checkpoint reload. What recommendation is most appropriate?

Fix it before release, unless an authorised deferral is recorded. Proceed because the menus work and the issue occurs only after a checkpoint reload. Remove it from the report so the sign-off decision is not delayed by one defect. Treat it as a feature request because it appears after a save-state transition.

E6-Q13 Select all that apply

Before asking required personnel to approve a release candidate, which items should be prepared as part of the sign-off evidence pack? Select all that apply.

Select all that apply.

Specific build number, version label, date and distribution target. Final QA results, navigation test report, regression notes and unresolved known issues. Release notes, acceptance criteria, licence or credit evidence and relevant asset documentation. Record of approved user-trial changes being closed or formally deferred. A general statement that the team feels the build is ready, without build traceability. A folder of the latest unlabelled editor files so reviewers can choose whichever version opens.

E6-Q14 Multiple choice

During final sign-off, a senior reviewer suggests adding a new multiplayer mode that was not in the approved specification. What is the best release-management response?

Treat it as a new feature request; include it only after formal scope approval. Implement it immediately because senior stakeholder comments override the release candidate scope. Add it to the final package without retesting because multiplayer is separate from navigation. Reject every reviewer comment during sign-off, including genuine blocking defects.

E6-Q15 Short answer

Your team freezes a specific versioned build that could become the final publication if the required reviewers approve it. Enter the standard two-word term for this build.

E6-Q16 Numerical

An organisational procedure requires the final archive allocation to include the approved packaged build, the source snapshot and the evidence pack, plus 10% contingency. The packaged build is 2.8 GB, the source snapshot is 1.6 GB and the evidence pack is 0.35 GB. What minimum storage allocation, in GB, should be planned?

E6-F1 True or false

A game that works correctly in the engine editor should still be launched and smoke-tested as a packaged build before distribution.

True False

E6-F2 Multiple choice

A team has final sign-off for a WebGL build. What should they do immediately after uploading it to the approved portal?

Launch it from the portal as a user and run a short smoke test. Delete the local approved build because the upload has completed successfully. Change the build settings to prepare for a different platform before checking it. Assume the release is valid because the upload progress bar reached 100%.

E6-F3 Matching

Match each publication item to its purpose.

Release notes

Install instructions

Third-party notices

Support information

E6-F4 Fill the gaps

A safe release workflow is to confirm , obtain , upload through an , and archive the .