A dashboard API returns the first page of store access points and a pointer to the next page. The script prints only that first page and reports 50 access points. The dashboard shows 200. What did the script skip?
Select an answer to reveal the explanation.
Short Explanation
The API handed you the first stack of cards and told you there is another stack. Your script stopped at 50 and called that the whole inventory. Follow the pointer until the pages run out.
Full Explanation
List APIs commonly return one page and a pointer, token, or link to the next page. This script printed the first page of 50 and ignored the pointer, so it reported 50 while the dashboard, which walks every page, shows 200. The skip is the rest of the pages. An RF tag is a controller object. It does not hide access points from a dashboard API count. The guest VLAN is not a prerequisite for pagination. The API already returned the first page without it. A channel change does not delete later pages. The other 150 access points are still in the inventory and would appear if the script followed the pointer. A page plus a pointer is not the whole list. Stopping after the first page is why the script reports 50 of the 200 access points. Exam caveat: stop when the pointer is absent, not after a fixed number of pages. A store that grows past two pages will be undercounted again if you only fetch twice. Operational check: follow the pointer in the lab until it ends and confirm the summed pages equal the dashboard count of 200.