Free CPUX-F Practice Test Questions and Answers (2026)

Satisfaction refers to the user's subjective feelings and emotional responses while using a system. Annoyance is a negative emotional response, directly indicating a problem with satisfaction. The other options relate to effectiveness (C, F), efficiency (D, E), or positive satisfaction (B).

1. International Usability and User Experience Qualification Board (UXQB), "Curriculum Usability and User Experience – Foundation Level (CPUX-F)", Version 3.11EN, 2023-06-23, Section 1.3.2, p. 16.

2. ISO 9241-11:2018, "Ergonomics of human-system interaction — Part 11: Usability: Definitions and concepts", Section 3.1.14, defines satisfaction as the "extent to which the user's physical, cognitive and emotional responses that result from the use of a system, product or service meet the user's needs and expectations."

Leading questions are phrased in a way that suggests a particular answer or contains the information the questioner wants to confirm. Option A uses the word "amazing," which presupposes a positive quality and biases the user towards agreement. Option C presents another user's idea as "great," which pressures the current interviewee to concur, thereby influencing their response. Both questions steer the user's opinion rather than eliciting an unbiased one. Neutral, open-ended questions like "What do you think of..." are preferred for gathering genuine user feedback.

B. This is an open-ended, neutral question that does not suggest a positive or negative response about the instructions.

D. This is a filtering question followed by an open-ended question to gather contextual information, not to lead the user.

E. This is a closed, factual question to determine the user's prior experience; it does not imply a desired answer.

F. This is an open-ended question that invites suggestions without guiding the user toward any specific financing model.

1. International Usability and UX Qualification Board (UXQB), "CPUX-F Curriculum - Usability and User Experience – Foundation Level," Version 3.3, 2023. Chapter 3.3.2, "Conducting the contextual inquiry," pp. 50-51 (discusses asking neutral, open-ended questions).

2. ISO 9241-210:2019, "Ergonomics of human-system interaction — Part 210: Human-centred design for interactive systems," Section 7.2, "Understand and specify the context of use" (emphasizes gathering unbiased data about users).

A usability inspection is a usability evaluation method performed by one or more usability experts. The experts examine an interactive system, or a part of it, against a set of usability principles (heuristics) to identify potential usability problems. It is an expert-based method, meaning it does not involve representative users performing tasks. The goal is to find and document usability issues early in the design process, often using prototypes or specifications without needing a fully functional system. This approach is cost-effective for finding common problems.

A. This describes an ideation or brainstorming session, which is a generative activity, not an evaluative inspection.

B. While a storyboard can be the subject of an inspection, this option is too specific and doesn't define the method itself.

D. This describes a focus group, a qualitative research method for gathering opinions, not a usability inspection.

E. This describes a usability test, which is an empirical evaluation method involving representative users, not experts.

F. This describes reviewing data from a different method (contextual interview), not the inspection method itself.

1. International Usability and User Experience Qualification Board (UXQB), “CPUX-F Curriculum – Foundation Level,” Version 3.11, 2023. Section 3.4.2, "Usability Inspection," p. 78.

2. International Usability and User Experience Qualification Board (UXQB), “CPUX-F Glossary,” Version 3.11, 2023. Definition of "Usability inspection," p. 41.

The provided text is a classic example of a persona. A persona is a detailed, narrative description of a fictional character created to represent a key user group. The description of "Elena Montgomery" includes a name, age, personal details, job role, specific tasks, expertise, and goals. This rich, concrete depiction helps the design and development team to empathize with users and make decisions that align with their needs and motivations.

A. Prototype: A prototype is an early, interactive model of a product, not a description of a user.

C. As-is scenario: This describes a user's current workflow or interaction with a system, not the user's personal and professional profile.

D. Use scenario: This describes a future, desired interaction with a system, focusing on a specific task.

E. User group: A user group is a collection of users with shared characteristics, not a single, detailed fictional individual.

F. User group profile: This is a summary of a user group's attributes, lacking the narrative and personal details of a persona.

International Usability and UX Qualification Board (UXQB), "CPUX-F Curriculum - Foundation Level," Version 3.11, 2023. Section 2.4.1 Personas, p. 37. (Defines a persona as a "description of a fictitious user that represents a user group" and lists typical contents like name, photo, goals, and tasks).

Cooper, A., Reimann, R., Cronin, D., & Noessel, C. (2014). About Face: The Essentials of Interaction Design (4th ed.). Wiley. Chapter 5, "Modeling Users: Personas and Goals," describes the creation and components of personas, which directly match the example provided.

Stakeholders are individuals or groups with an interest in a system, while users are those who interact with it to achieve a goal. The designer (C) and the marketing executive (F) are stakeholders because the website's success is critical to their roles. However, they are not users in the primary sense; they do not use the website's public interface to rent cars. Their interaction is with the development process or back-end administrative systems, not the end-user product itself.

A. A trainer... teaching staff... how to use the car rental website: The trainer is a direct user of the website, as their job requires them to interact with it.

B. A call centre employee... using the car rental website: This employee is a primary, direct user of the website to perform their job.

D. An accounts administrator who receives an email invoice: This person is an indirect or secondary user, as they interact with the output of the system.

E. A customer who contacts a call centre employee: This customer is the primary user for whom the system is designed, even if their interaction is indirect.

International Usability and UX Qualification Board (UXQB), "CPUX-F Curriculum - Foundation Level," Version 3.11, 2023. Section 2.2 Users and Stakeholders, p. 27. (Distinguishes between users who interact with the product and other stakeholders like management or developers).

ISO 9241-210:2019, Ergonomics of human-system interaction — Part 210: Human-centred design for interactive systems. Section 3.1.10 Stakeholder. (Defines stakeholder broadly as an "individual or organization that has a right, share, claim, or interest in a system," which includes non-users like developers and marketing).

A prototype is a tangible representation of a design solution that allows stakeholders to interact with it and explore its suitability. It is intentionally limited in some way—for example, in its visual fidelity, functionality, or data—to enable early analysis, design iteration, and evaluation before investing in full development. Prototypes are a fundamental tool in the human-centered design process for testing design ideas with users and gathering feedback. They can range from simple paper sketches to highly interactive digital mockups.

This is a fill-in-the-blank question with one correct answer. Other terms like 'wireframe' or 'mockup' are types of prototypes but are less comprehensive than the term 'prototype' itself.

1. UXQB. (2023). CPUX-F Curriculum – Foundation Level. International Usability and User Experience Qualification Board e.V. Glossary, page 101, defines a prototype as "A representation of all or part of an interactive system that, although limited in some way, can be used for analysis, design and usability evaluation."

2. UXQB. (2023). CPUX-F Curriculum – Foundation Level. International Usability and User Experience Qualification Board e.V. Chapter 4.3, "Prototypes," details their purpose and types.

The provided text is a comprehensive definition of Human-centred design (HCD) as outlined in the international standard ISO 9241-210. It encapsulates the core principles of HCD: starting with a deep understanding of users and their context, involving users throughout an iterative process, using evaluation to drive design decisions, and focusing on the entire user experience. This approach ensures that interactive systems are useful, usable, and satisfying for the intended users.

This is a fill-in-the-blank question with only one correct answer. The description precisely matches the internationally recognized definition of Human-centred design.

1. ISO 9241-210:2019, Ergonomics of human-system interaction — Part 210: Human-centred design for interactive systems, Section 4, "Principles of human-centred design".

2. UXQB® Certified Professional for Usability and User Experience – Foundation Level (CPUX-F) Curriculum, Version 3.5 (2023), Section 2.1, p. 16.

In the context of usability and user interface design, a heuristic is a recognized principle or "rule of thumb" that provides practical guidance for creating usable systems. These are not strict, inviolable rules but rather established best practices.

1. International Usability and User Experience Qualification Board (UXQB). (2023). CPUX-F – Glossary – Foundation Level, Version 3.2. p. 11. (Defines "Heuristic" as: "A generally recognised rule of thumb that helps to achieve usability.").

2. International Usability and User Experience Qualification Board (UXQB). (2023). CPUX-F – Curriculum – Foundation Level, Version 3.2. Section 4.4.1, "What is a heuristic evaluation?", p. 75. (States, "Heuristics are recognised rules of thumb which are based on experience.").

3. Nielsen, J. (1994). Heuristic evaluation. In J. Nielsen & R. L. Mack (Eds.), Usability Inspection Methods (pp. 25-62). John Wiley & Sons. (Nielsen, who popularized the concept in HCI, consistently refers to heuristics as "rules of thumb").

An "As-is scenario" is a narrative that describes how a specific user, often represented by a persona, currently performs a task or achieves a goal. It details the existing workflow, tools used, and any challenges or pain points encountered before the introduction of a new or redesigned system. This tool is fundamental in the "Understand and specify the context of use" activity to establish a baseline of the current user experience, which helps in identifying opportunities for improvement and defining user requirements for the new system.

No alternatives were provided in the item.

1. UXQB® Certified Professional for Usability and User Experience – Foundation Level (CPUX-F) Curriculum, Version 3.1 (May 2023), Glossary, p. 100. "As-is scenario: Narrative description of the activities that a persona carries out in order to reach a goal, including the problems that the persona encounters. An as-is scenario describes the current situation before the use of the interactive system to be developed."

2. Interaction Design: Beyond Human-Computer Interaction, 5th Edition, by Rogers, Y., Sharp, H., & Preece, J. (2019), Chapter 10. This university-level textbook describes scenarios as informal narratives about user tasks and activities, distinguishing between current ("as-is") and future states.

A usability test is a formal evaluation method where representative users perform specific tasks with a system to measure its usability. It focuses on observing user behavior and performance, not on eliciting subjective opinions or conducting interviews, which are different user research techniques.

1. International Usability and User Experience Qualification Board (UXQB). (2023). CPUX-F – Curriculum – Foundation Level, Version 3.2. Section 4.3.1, "What is a usability test?", p. 68. (Defines usability test and distinguishes it from interviews and focus groups).

2. Nielsen, J. (1993). Usability Engineering. Morgan Kaufmann. Chapter 6, "Usability Testing", pp. 165-166. (Emphasizes observing users performing tasks rather than asking for opinions).

3. Dumas, J. S., & Redish, J. C. (1999). A Practical Guide to Usability Testing. Intellect Books. Chapter 1, "What Is Usability Testing?", p. 4. (Defines usability testing as observing people using a product as they perform tasks).