A municipal hospital campus must inventory thousands of devices from a controller API without client timeouts. Which retrieval pattern best scales?
Select an answer to reveal the explanation.
Short Explanation
Huge inventories are like patient charts—you do not dump the whole medical records room into one elevator. Page through the controller API until you have everyone. One giant GET times out; stopping after page one leaves wards uncounted.
Full Explanation
Controller inventory APIs typically expose offset/limit, page, or cursor parameters so clients retrieve large result sets in bounded responses. Iterating until no next page remains avoids timeouts and memory spikes from a single massive payload. Truncating after one page under-reports devices. Syslog is not a substitute for authoritative inventory APIs.