The Contribution of the Test Analyst to Product Risk Analysis CTAL-TA Practice Questions (Page 1)

Questions 1–5

1. 1expert · hard

   A test analyst is working on a new customer relationship management (CRM) system. The risk analysis has identified that the 'data import' feature has a high likelihood of failure because the data formats from legacy systems are inconsistent. The impact of a failure is moderate (data may need to be re-imported). The project sponsor is concerned about the release date and wants to know if the risk can be accepted. How should the test analyst communicate the risk to the sponsor?

   • AState that the risk is acceptable because the impact is only moderate.
   • BTell the sponsor that the risk is a technical issue and should be discussed with the development team.
   • CRecommend that the sponsor accept the risk without further analysis, as the impact is moderate.
   • DExplain that the risk has a high likelihood of failure, which could cause delays in data migration, and recommend that testing focus on this area to reduce the risk.
   Reveal Solution Discussion Select an answer first
2. 2expert · hard

   A test analyst is facilitating a risk assessment workshop for a new online payment system. The workshop includes business stakeholders, developers, and the product owner. The business stakeholders are rating the 'fraud detection' feature as low risk because 'the system is new and has no historical data.' The developers, however, have identified that the fraud detection algorithm is complex and has several edge cases that could be problematic. The test analyst must ensure the risk assessment is accurate. What should the test analyst do?

   • ASuggest that the fraud detection feature be rated as high risk based on the developers' technical complexity concerns, and document the rationale.
   • BAsk the business stakeholders to provide historical data from other systems to support their low-risk rating.
   • CAccept the business stakeholders' rating, as they have the final say on risk levels.
   • DDefer the risk rating decision to the product owner, as they are the ultimate authority.
   Reveal Solution Discussion Select an answer first
4. 3foundation · easy

   During a product risk analysis session, the test analyst identifies that a new feature for online payment may have usability issues for first-time users. Which product risk category does this concern?

   • AUsability risk
   • BCompatibility risk
   • CSecurity risk
   • DPerformance risk
   Reveal Solution Discussion Select an answer first
5. 4expert · hard · select all that apply

   A test analyst is participating in a risk assessment workshop for a new online banking system. The system has the following features: fund transfer, bill payment, account balance inquiry, and customer profile management. The team has identified the following risks: (1) fund transfer may fail to execute correctly, (2) bill payment may double-charge customers, (3) account balance inquiry may show stale data, and (4) customer profile management may allow unauthorized changes. The system must comply with financial regulations. Select all the product risk categories that the test analyst should ensure are considered in the risk analysis.

   • ASecurity, for risks like unauthorized changes to customer profiles.
   • BPerformance, for risks like slow account balance inquiry.
   • CUsability, for risks like a confusing fund transfer interface.
   • DFunctional correctness, for risks like fund transfer and bill payment.
   • EData integrity, for risks like stale account balance data.
   Check answers Discussion Select an answer first
6. 5application · medium

   A test analyst is communicating product risk information to a group of stakeholders, including the project sponsor, the development lead, and the customer representative. The risk analysis has identified that the 'user authentication' feature has a high likelihood of failure due to recent changes in the security framework. How should the test analyst communicate this risk to the different stakeholders?

   • ACommunicate the risk in a way that is tailored to each stakeholder group: business impact for the sponsor, technical details for the development lead, and user impact for the customer representative.
   • BOnly inform the development lead, as they are the ones who can fix the issue.
   • CWait until the risk is confirmed by testing before communicating it to anyone.
   • DSend a single, detailed technical report to all stakeholders, as the risk information is the same for everyone.
   Reveal Solution Discussion Select an answer first