Evaluate an Application Design Considering Latency and Rate Limiting 350-901 Practice Questions (Page 6)

Questions 26–28

1. 26application · medium

   A retail company's mobile app fetches product details from a REST API. Users in a different region report that the product images and descriptions take several seconds to load, while users near the origin server have no issues. The API response time is under 100 ms when tested from the origin's region. Which design change would most directly address the latency experienced by the remote users?

   • AIncrease the timeout value in the mobile app's HTTP client to allow more time for the API to respond.
   • BEnable HTTP/2 on the origin server to allow multiplexing of multiple requests over a single connection.
   • CSwitch the API from REST to GraphQL to reduce the number of round trips required to fetch product data.
   • DImplement a content delivery network (CDN) to cache static product images and descriptions at edge locations.
   Reveal Solution Discussion Select an answer first
2. 27expert · hard

   A team is building a chat application that uses a third-party messaging API with a rate limit of 5 messages per second per user. The application must handle a user sending 50 messages in a rapid burst. The team wants to ensure all messages are delivered without violating the rate limit. Which approach best balances user experience and system stability?

   • AIncrease the API rate limit by contacting the third-party provider and requesting a higher limit.
   • BSend all 50 messages immediately and rely on the API to queue them internally.
   • CQueue the messages locally and send them at a rate of 5 per second, showing a 'sending' indicator to the user.
   • DReject the burst and ask the user to wait 10 seconds before sending more messages.
   Reveal Solution Discussion Select an answer first
3. 28application · medium

   A financial services company is redesigning a customer-facing dashboard that displays real-time account balances. The backend database query takes 800 ms, and the dashboard must display data within 500 ms. The data changes frequently but does not need to be perfectly up-to-date for every user. Which approach best meets the latency requirement while maintaining acceptable data freshness?

   • AOptimize the database query by adding indexes to the account table to reduce the query time to 400 ms.
   • BChange the dashboard to use a long-polling mechanism to fetch data every 30 seconds.
   • CMove the dashboard to the same virtual network as the database to reduce network round-trip time.
   • DCache the account balance in an in-memory store with a 5-second time-to-live (TTL) and serve the cached value to the dashboard.
   Reveal Solution Discussion Select an answer first