Quiz — Prepare to create game

E1-Q1 Select all that apply

A small studio is about to estimate a beta prototype for a complex 3-D interactive game. Which items should be obtained before the team treats the requirements as production-ready? Select all that apply.

Select all that apply.

The latest authorised project brief or statement of work The Game Design Document covering mechanics, rules, progression and player feedback Technical specifications, including engine version, target platform and build pipeline requirements Organisational procedures for version control, naming, reviews, bug reporting and security A personal folder structure used successfully on a previous unrelated project Post-release marketing analytics from a different game with a similar genre

E1-Q2 Fill the gaps

A producer finds that the art bible asks for cinematic realistic lighting, while the target hardware list includes low-spec school laptops. In a requirements clarification log, record the source document and section, describe the , identify the , assign the , and capture the with date and approval evidence.

E1-Q3 Multiple choice

A brief calls for a visually rich 3-D exploration game, but the beta must run reliably on older laptops. What is the best asset-planning response?

Set budgets for LODs, textures, collision, shaders and target-hardware performance. Create all art at maximum fidelity first, then decide near beta which assets should be optimised, merged, replaced or removed when performance problems become visible. Use only placeholder cubes for the beta because target hardware constraints mean creative asset planning and representative visual direction are unnecessary until release. Allow each artist to choose export settings independently so the team can compare visual styles, file sizes and import behaviours at the end of production.

E1-Q4 Matching

Match each asset register field with the production-control purpose it supports.

Owner or responsible role

Dependencies

Beta priority

Acceptance criteria

Required format and engine destination

E1-Q5 Select all that apply

A technical artist is preparing the first test import of character and environment assets into the game engine. Which issues should be discussed with relevant personnel before large-scale asset production continues? Select all that apply.

Select all that apply.

Scale, units, pivot points and orientation between the 3-D tool and the engine Rig hierarchy, skeleton rules, animation clips and controller requirements Texture formats, material setup, shader compatibility and memory budget Collision, LODs, prefab setup and in-game placement requirements Audio looping, compression, loudness and whether sounds should stream or load into memory Postponing all test imports until every final asset is complete Increasing every texture size because the engine can import high-resolution files

E1-Q6 True or false

Powerful engine features such as advanced lighting, virtualised geometry, complex shaders or high-end physics still need technical budgets because they can affect GPU time, memory, build size and target-platform performance.

True False

E1-Q7 Fill the gaps

Complete the milestone descriptions. Simple geometry used to test layout, scale and interaction is a . A small section demonstrating intended final quality across art, audio, code and gameplay is a . When major features are implemented but content may be incomplete and bugs remain, the build is typically . The quality gate where features and required assets are complete or controlled exceptions are recorded, with testing focused on defects, balance, performance and polish, is .

E1-Q8 Numerical

A beta prototype critical path is: rig setup 2 days, player controller scripting 4 days, combat integration 3 days, and beta smoke test 1 day. The tasks cannot overlap. Rig setup finishes 1 day late and player controller scripting takes 6 days instead of 4. Other task durations are unchanged. What is the forecast slip in the beta date, in days?

E1-Q9 Multiple choice

A team must determine the development sequence for a beta prototype that proves a new 3-D combat loop. Which sequence best supports reliable gameplay testing while reducing downstream blockers?

Define beta criteria, greybox the core loop, test risks early, integrate progressively and gate readiness. Finish all final character and environment art first, then begin gameplay scripting once the visual style, material library and lighting direction are completely locked. Create a polished promotional trailer first, then use stakeholder reactions to decide whether a playable beta prototype should still be built and tested. Assign each discipline to work independently until the final week, then combine all systems for the first time in a single beta integration push.

E1-Q10 Matching

Match each testing activity with the most suitable point or purpose in the beta production schedule.

Unit or component testing of scripts

Smoke testing

Integration testing

Playtesting

Regression testing

E1-Q11 Select all that apply

A production schedule currently allocates three days for “make environment props” and nothing else. Which additions would make the schedule more realistic for beta asset production and integration? Select all that apply.

Select all that apply.

Requirement confirmation and source or GDD reference checks Internal creative review and technical art review before export LOD, collision, export, engine import, prefab or setup work In-game QA against acceptance criteria and time for revisions Separate visibility for beta-critical or high-risk assets rather than hiding them in a broad task Only modelling time, because importing and testing assets can safely wait until the final beta build Removing dependency information so the schedule is easier to read

E1-Q12 True or false

If the beta date is fixed and the team has limited capacity, the safest schedule-control response is to quietly reduce acceptance criteria and remove testing time so the task list still appears on schedule.

True False

E1-Q13 Multiple choice

A producer asks for a monitoring strategy for the beta prototype schedule. Which response is strongest?

Track schedule, quality, risks, bugs, build health and critical path movement with agreed review and escalation rules. Ask team members whether they feel on track at the end of each month, then avoid changing the schedule unless the beta date has already passed and the client has complained. Monitor only the percentage of tasks marked complete because build stability, asset acceptance, risk exposure and bug severity can be checked after the beta milestone. Use a private spreadsheet that is not shared with artists, programmers, QA or stakeholders so reporting remains simple and fewer people can question the schedule.

E1-Q14 Fill the gaps

Monitoring a beta prototype should compare actual progress with planned progress. A is the gap between plan and reality. A records likelihood, impact, owner and response for threats. The is the dependent task chain controlling the earliest beta date. A Definition of Done prevents false progress by requiring work to be .

E1-Q15 Short answer

A build engineer records that an unfamiliar engine plug-in might block beta builds. The record includes likelihood, impact, owner and response actions. What production-control artefact is being used?

E1-Q16 Multiple choice

A gameplay programmer needs spawn-wave data for enemies, while designers need to tune values without editing compiled code. What is the best preparation action before asset and scripting work scales up?

Agree and document a supported data format with import and validation rules. Hard-code all enemy spawn values into gameplay scripts so designers cannot accidentally change balance while preparing beta builds, test waves or tuning passes. Let each designer create enemy waves in any spreadsheet or text format, then ask the programmer to manually convert and troubleshoot them at the end of production. Choose the format that looks most readable in a presentation because spawn-wave data is mainly a visual communication asset for stakeholders and reviewers.

E1-F1 True or false

If the project brief is unclear about target platforms, the safest preparation action is to assume the most powerful platform available and continue production.

True False

E1-F2 Matching

Match each production item to its asset category.

Footstep sound loops

Enemy behaviour script

Health bar icons

NPC walk cycle

E1-F3 Multiple choice

When is the best time to perform initial test imports for a new 3-D asset pipeline?

Early, using representative assets before production scales up Only after every final asset has been approved by the art director and the team has no remaining revision time in the schedule After beta testing is complete, because integration findings are most useful once all gameplay feedback has already been collected Only when the final release candidate is built and all platform submission checks are being completed

E1-F4 Fill the gaps

A useful production schedule shows what work will be done, , , and in what order.

E1-F5 Select all that apply

Which evidence sources can help monitor beta production progress? Select all that apply.

Select all that apply.

Kanban or sprint board status Bug dashboard by severity Build verification report Risk register review notes A guess that the team is probably fine because no one complained