Performance Risks Across the Software Development Lifecycle CT-PT Practice Questions (Page 4)

Questions 16–20

1. 16application · medium

   A performance test team has identified three risks: (1) a database deadlock that occurs only under extreme load, (2) a slow file upload feature that affects a small group of users, and (3) a memory leak that causes the application to crash after several days of uptime. The team has time to address only one before release. Which risk should be prioritized?

   • AThe slow file upload, because it affects user satisfaction directly.
   • BAll three equally, because every risk must be addressed before release.
   • CThe database deadlock, because it is a technical issue that must be fixed.
   • DThe memory leak, because it can cause a complete system crash, affecting all users and potentially causing data loss.
   Reveal Solution Discussion Select an answer first
2. 17application · medium

   A development team is implementing a new feature that involves a complex algorithm processing large datasets. The team is under pressure to deliver quickly and decides to skip unit-level performance checks. What is the most likely consequence of this decision?

   • AThe feature will definitely be faster because less time is spent on testing.
   • BThe only impact will be on test coverage, not on project timelines.
   • CPerformance issues in the algorithm may go undetected until system-level testing, making them harder and more expensive to fix.
   • DThe algorithm will automatically be optimized by the compiler at runtime.
   Reveal Solution Discussion Select an answer first
4. 18application · medium

   During the design phase, the team identifies a risk that the new authentication service may not handle the expected peak load. Which mitigation strategy is most appropriate to apply during the design phase?

   • AUse a single powerful server to handle all authentication traffic.
   • BPlan to run a performance test after the service is deployed to production.
   • CDesign the authentication service to be stateless and horizontally scalable, allowing additional instances to be added during peak load.
   • DIncrease the timeout values for authentication requests to reduce user-perceived errors.
   Reveal Solution Discussion Select an answer first
5. 19expert · hard

   A team is developing a system that integrates with several external services. During the design phase, they identify a risk that one of the external services may have variable latency. The team is considering two mitigations: (1) implement caching to reduce calls to the external service, and (2) set aggressive timeouts to fail fast. Which approach is more appropriate?

   • ASet aggressive timeouts to fail fast, because it is simpler and avoids the complexity of caching.
   • BIgnore the external service's latency because it is outside the team's control.
   • CIncrease the timeout values to allow the external service more time to respond.
   • DImplement caching to reduce dependency on the external service, and set reasonable timeouts to handle failures gracefully.
   Reveal Solution Discussion Select an answer first
6. 20expert · hard

   A team is developing a system that must handle a known peak load during a seasonal sale. The performance test lead has identified a risk that the current architecture may not handle the peak. The team has two mitigation options: (1) optimize the code to reduce response times, and (2) add more servers to increase capacity. The budget is limited, and the code optimization will take two weeks, while adding servers can be done immediately. Which approach is most appropriate?

   • ADo both simultaneously, even if it exceeds the budget.
   • BAdd more servers immediately to ensure capacity for the peak, and plan code optimization for after the sale.
   • COptimize the code first, because it is a permanent solution that reduces the need for additional servers.
   • DDo nothing and hope the system handles the peak.
   Reveal Solution Discussion Select an answer first