Core Analyst Badge Prep Exam Questions With Verified
Correct Answers Already Graded A
Section 1: Usability Fundamentals
1. What is Usability?
• Answer: Usability reduces the friction between the user and their ability to
accomplish tasks with efficiency and satisfaction.
• Rationale: This definition focuses on the core goal of usability: creating a seamless
experience. It’s not just about making something "easy," but about minimizing
obstacles ("friction") so users can achieve their objectives effectively and with a
positive experience.
2. What are the three portions of Usability?
• Answer: User interviews, Heuristic evaluations, Workflow analysis tools.
• Rationale: These three components represent a holistic approach to evaluating and
improving usability. User interviews provide direct feedback, heuristic evaluations
apply expert principles, and workflow analysis tools offer data-driven insights into
process efficiency.
3. What is a user interview?
• Answer: Interviewing users to help determine how and why your end users do what
they do.
• Rationale: The purpose is to gain deep, qualitative insights into user behavior,
motivations, and challenges, which is foundational for designing user-centered
systems.
4. What is the purpose of a User Interview?
• Answer: To determine what they NEED and not what they WANT. To determine
HOW and WHY they do what they do.
• Rationale: This highlights a critical distinction in design. Users often ask for features
("wants") based on current workflows. The goal of an interview is to uncover the
underlying goals and needs that drive those requests, allowing for more effective and
innovative solutions.
, 5. How do you identify appropriate users for a user interview?
• Answer: Ask yourself: Who are the primary users of this build? What users interact
with this build (including users who use the information or results produced by the
build)? What workflows and tasks intersect with this area? Why are they using this
build to accomplish the defined tasks?
• Rationale: A comprehensive user selection process ensures you capture perspectives
from everyone impacted by the build, including direct users and those who consume
the output. Understanding the "why" confirms the user's relevance to the goals of
the interview.
6. How do you write questions for a user interview?
• Answer:
o Start with open-ended questions as a warm-up and then narrow your scope.
o Don't ask leading questions.
o Vary phrasing and types of questions (multiple choice, free response, quantitative) to
keep them engaged.
o Don't include "want."
o Don't ask "how" (results in a surface-level response), rather pair open-ended
questions with more pointed ones. With follow-up questions, don't ask "why," as this
may make the interviewee defensive. Instead, frame questions using "how," "what,"
or "when."
• Rationale: These techniques are designed to gather unbiased, rich data. Avoiding
leading questions prevents influencing the answer. Varying question types maintains
engagement. Steering clear of "want" and "why" (which can feel judgmental)
encourages users to describe their actual processes and thought patterns without
feeling defensive or pressured to provide a specific answer.
7. How do you conduct a user interview?
• Answer: Make sure the participant feels valued and that their time is well spent. Start
with general questions, moving on to questions focused on the topic at hand.
• Rationale: Building rapport and showing respect for the participant's time is crucial
for a successful interview. A structured flow from general to specific helps the
participant feel comfortable and provides context before diving into detailed topics.
8. Why would you complete a user interview?
• Answer: In order to identify needs rather than wants. Used to determine how and
why your end users do what they do and configure the system to make their
workflows efficient, elegant, and usable.
, • Rationale: This reinforces the core value of user interviews as a tool for need-finding,
ensuring that system configuration is grounded in actual user behavior and goals,
leading to more effective and adopted solutions.
9. What is a heuristic?
• Answer: Simple rules that you can use to approximate a larger probable truth from
smaller truths that are easier to observe. General rules of thumb that can be used to
help make decisions.
• Rationale: This defines heuristics as practical, experience-based guidelines that
simplify complex problems, making them useful for quick evaluations and decision-
making.
10. What is a heuristic evaluation?
• Answer: An evaluation of an existing or planned build using heuristics to identify
successes and violations.
• Rationale: This describes the process of systematically applying heuristics to identify
usability strengths and weaknesses, providing a structured way to critique a design.
11. What are the six Heuristics?
• Answer:
1. System Matches the Real World
2. Consistency and Standards
3. Recognition, Not Recall
4. Flexibility and Efficiency
5. Aesthetic and Minimalist Design
6. Help and Documentation
• Rationale: These six principles are a core set of usability guidelines adapted for
system building. They cover key aspects of user experience, from using familiar
language to reducing cognitive load and providing support.
12. What are the six usability heuristics for builders?
• Answer: System matches the real world. Consistency and standards (use
organization's terminology and naming conventions, and don't let users wonder
whether different words, situations, or actions mean the same thing.)
• Rationale: (Note: The provided answer is incomplete in the original text, only listing
two). These first two heuristics are foundational. They ensure the system speaks the
user's language and behaves predictably, which builds trust and reduces errors.
13. How do you complete a heuristics evaluation?
Correct Answers Already Graded A
Section 1: Usability Fundamentals
1. What is Usability?
• Answer: Usability reduces the friction between the user and their ability to
accomplish tasks with efficiency and satisfaction.
• Rationale: This definition focuses on the core goal of usability: creating a seamless
experience. It’s not just about making something "easy," but about minimizing
obstacles ("friction") so users can achieve their objectives effectively and with a
positive experience.
2. What are the three portions of Usability?
• Answer: User interviews, Heuristic evaluations, Workflow analysis tools.
• Rationale: These three components represent a holistic approach to evaluating and
improving usability. User interviews provide direct feedback, heuristic evaluations
apply expert principles, and workflow analysis tools offer data-driven insights into
process efficiency.
3. What is a user interview?
• Answer: Interviewing users to help determine how and why your end users do what
they do.
• Rationale: The purpose is to gain deep, qualitative insights into user behavior,
motivations, and challenges, which is foundational for designing user-centered
systems.
4. What is the purpose of a User Interview?
• Answer: To determine what they NEED and not what they WANT. To determine
HOW and WHY they do what they do.
• Rationale: This highlights a critical distinction in design. Users often ask for features
("wants") based on current workflows. The goal of an interview is to uncover the
underlying goals and needs that drive those requests, allowing for more effective and
innovative solutions.
, 5. How do you identify appropriate users for a user interview?
• Answer: Ask yourself: Who are the primary users of this build? What users interact
with this build (including users who use the information or results produced by the
build)? What workflows and tasks intersect with this area? Why are they using this
build to accomplish the defined tasks?
• Rationale: A comprehensive user selection process ensures you capture perspectives
from everyone impacted by the build, including direct users and those who consume
the output. Understanding the "why" confirms the user's relevance to the goals of
the interview.
6. How do you write questions for a user interview?
• Answer:
o Start with open-ended questions as a warm-up and then narrow your scope.
o Don't ask leading questions.
o Vary phrasing and types of questions (multiple choice, free response, quantitative) to
keep them engaged.
o Don't include "want."
o Don't ask "how" (results in a surface-level response), rather pair open-ended
questions with more pointed ones. With follow-up questions, don't ask "why," as this
may make the interviewee defensive. Instead, frame questions using "how," "what,"
or "when."
• Rationale: These techniques are designed to gather unbiased, rich data. Avoiding
leading questions prevents influencing the answer. Varying question types maintains
engagement. Steering clear of "want" and "why" (which can feel judgmental)
encourages users to describe their actual processes and thought patterns without
feeling defensive or pressured to provide a specific answer.
7. How do you conduct a user interview?
• Answer: Make sure the participant feels valued and that their time is well spent. Start
with general questions, moving on to questions focused on the topic at hand.
• Rationale: Building rapport and showing respect for the participant's time is crucial
for a successful interview. A structured flow from general to specific helps the
participant feel comfortable and provides context before diving into detailed topics.
8. Why would you complete a user interview?
• Answer: In order to identify needs rather than wants. Used to determine how and
why your end users do what they do and configure the system to make their
workflows efficient, elegant, and usable.
, • Rationale: This reinforces the core value of user interviews as a tool for need-finding,
ensuring that system configuration is grounded in actual user behavior and goals,
leading to more effective and adopted solutions.
9. What is a heuristic?
• Answer: Simple rules that you can use to approximate a larger probable truth from
smaller truths that are easier to observe. General rules of thumb that can be used to
help make decisions.
• Rationale: This defines heuristics as practical, experience-based guidelines that
simplify complex problems, making them useful for quick evaluations and decision-
making.
10. What is a heuristic evaluation?
• Answer: An evaluation of an existing or planned build using heuristics to identify
successes and violations.
• Rationale: This describes the process of systematically applying heuristics to identify
usability strengths and weaknesses, providing a structured way to critique a design.
11. What are the six Heuristics?
• Answer:
1. System Matches the Real World
2. Consistency and Standards
3. Recognition, Not Recall
4. Flexibility and Efficiency
5. Aesthetic and Minimalist Design
6. Help and Documentation
• Rationale: These six principles are a core set of usability guidelines adapted for
system building. They cover key aspects of user experience, from using familiar
language to reducing cognitive load and providing support.
12. What are the six usability heuristics for builders?
• Answer: System matches the real world. Consistency and standards (use
organization's terminology and naming conventions, and don't let users wonder
whether different words, situations, or actions mean the same thing.)
• Rationale: (Note: The provided answer is incomplete in the original text, only listing
two). These first two heuristics are foundational. They ensure the system speaks the
user's language and behaves predictably, which builds trust and reduces errors.
13. How do you complete a heuristics evaluation?
