Describe the Difference Between Rate Limiting and Bandwidth Throttling F5N3 Practice Questions (Page 2)

Questions 6–10

1. 6foundation · easy

   Which statement best defines rate limiting in NGINX?

   • ARestricting the number of requests a client can make within a specified time period
   • BLimiting the maximum data transfer rate for a connection
   • CLimiting the size of a single request payload
   • DRestricting the total number of concurrent connections from a client
   Reveal Solution Discussion Select an answer first
2. 7foundation · easy

   What is the primary purpose of rate limiting in NGINX?

   • ATo manage network traffic and ensure fair usage of bandwidth
   • BTo cache static content for faster delivery
   • CTo encrypt data transmitted between client and server
   • DTo control request frequency and protect servers from overload
   Reveal Solution Discussion Select an answer first
4. 8foundation · easy

   Which statement best defines bandwidth throttling in NGINX?

   • ALimiting the maximum data transfer rate for a connection or client
   • BRestricting the total amount of data a client can download in a day
   • CRestricting the number of requests a client can make per minute
   • DLimiting the number of concurrent connections from a client
   Reveal Solution Discussion Select an answer first
5. 9foundation · easy

   Which of the following is a common use case for bandwidth throttling?

   • ALimiting the number of concurrent connections from a client
   • BLimiting the bitrate of a video stream to ensure fair usage
   • CLimiting the number of login attempts per minute
   • DLimiting the size of a request body
   Reveal Solution Discussion Select an answer first
6. 10expert · hard

   A SaaS provider hosts a document collaboration platform. Users upload and download large files, and the platform also exposes a REST API used by third-party integrations. The operations team has observed two distinct problems: (1) a single integration client is hammering the API with thousands of small requests per second, and (2) a few users are saturating the network link by downloading very large documents. The team wants to address both problems with a single NGINX configuration change. Which approach should they take?

   • AApply both a rate limit of 100 requests per second per IP address and a bandwidth throttle of 2 MB/s per IP address.
   • BApply a rate limit of 100 requests per second per IP address only.
   • CApply a bandwidth throttle of 2 MB/s per IP address only.
   • DSet the limit_req_zone and limit_conn_zone directives to the same shared memory zone.
   Reveal Solution Discussion Select an answer first