You have been given the following test cases for execution. You have been told that security and usability are the highest priorities respectively for this banking application. What is the proper…

Question

Options

• A3, 1, 5, 2, 4
• B1, 2, 5, 4, 3
• C1, 3, 5, 2, 4
• D4, 3, 1, 2, 5

• A
  11% (3)
• B
  7% (2)
• C
  4% (1)
• D
  79% (22)

Explanation

Option D (4, 3, 1, 2, 5) is correct because it follows a risk-escalation order: begin with the lowest-risk, no-data-change operation (font size, #4) to confirm the application is running properly, then progress through administrative (#3), financial-modify (#1), financial-verify (#2), and finally the highest-fraud-risk operation - adding an automatic bill pay payee (#5), which could enable unauthorized recurring payments. Critically, querying the balance (#2) is placed immediately after updating it (#1) so the update can be verified before moving on to a new security-sensitive action.

Why the distractors fail:

• A (3, 1, 5, 2, 4) buries the usability test last and jumps into data operations without a baseline check.
• B (1, 2, 5, 4, 3) starts with a high-risk financial update before any baseline is established and ends with a delete, leaving the system in a changed state with no verification.
• C (1, 3, 5, 2, 4) also dives into the highest-risk financial operation first and delays the balance query until after the payee is created, breaking the verify-what-you-just-changed dependency.

Memory tip: Think "safe to risky, verify as you go" - cosmetic UI → administrative cleanup → financial write → read to verify → new high-risk creation. This maps directly to 4 → 3 → 1 → 2 → 5.

No community discussion yet for this question.