Risk Identification CTAL-TTA Practice Questions (Page 5)

Questions 21–25

1. 21foundation · easy

   A Technical Test Analyst is preparing for a risk identification workshop and wants to ensure that common technical risks are not overlooked. The analyst plans to use a structured list of typical risks derived from past projects and industry experience. Which technique is the analyst applying?

   • AFailure mode and effects analysis (FMEA)
   • BExpert judgment
   • CChecklist-based analysis
   • DBrainstorming
   Reveal Solution Discussion Select an answer first
2. 22application · medium

   During requirements review, a technical test analyst notices that the requirement 'The system shall process orders quickly' is vague. Which risk should the analyst document?

   • AThe project schedule may slip because the requirement is unclear.
   • BThe test environment may not support performance testing.
   • CThe system may have a security vulnerability in the order processing module.
   • DAmbiguity in the requirement may lead to incorrect test design and unmet user expectations.
   Reveal Solution Discussion Select an answer first
4. 23application · medium

   During a code review, a technical test analyst notices that a module has a very high cyclomatic complexity and is tightly coupled to a database schema that is expected to change. Which risk should be documented?

   • AThe module may have a poor user interface.
   • BThe test environment may not support the database version.
   • CThe project schedule may be delayed due to code review.
   • DThe module is likely to contain defects and may be difficult to test thoroughly.
   Reveal Solution Discussion Select an answer first
5. 24foundation · easy

   A requirements document describes the behavior of a login function, but it does not specify what happens when a user enters an incorrect password. Which requirement risk is most directly indicated?

   • AAmbiguity
   • BInconsistency
   • COver-specification
   • DIncompleteness
   Reveal Solution Discussion Select an answer first
6. 25application · medium

   During a risk identification workshop, the team identifies several risks, including a potential security flaw in the authentication module and a risk that the test environment will not be ready on time. What is the most appropriate way to document these risks?

   • ARecord each risk with a description, likelihood, and impact in a risk register.
   • BList the risks in an email to the project manager without further details.
   • CCreate a separate document for each risk and store them in different folders.
   • DVerbally agree on the risks and take no written record.
   Reveal Solution Discussion Select an answer first