An application calls a REST API and expects a result set of more than 550 records, but each time the call is made, only 25 are returned. Which feature limits the amount of data that is returned by the API?
B and C cannot be the soluction.
A (Pagination) is the solution: When a request is made to get a list, it is almost never a good idea to return all resources at once. This is where a pagination mechanism comes into play. There are two popular approaches to pagination: Offset-based pagination Keyset-based pagination, also known as continuation token or cursor pagination (recommended)
Jackson Chris; Gooley Jason; Iliesiu Adrian; Malegaonkar Ashutosh. Cisco Certified DevNet Associate DEVASC 200-901 Official Cert Guide (p. 162). Pearson Education. Edición de Kindle.
D is not because: Rate limiting is an essential REST API design method for developers. Rate-limiting techniques are used to increase security, business impact, and efficiency across the board or end to end.
Jackson Chris; Gooley Jason; Iliesiu Adrian; Malegaonkar Ashutosh. Cisco Certified DevNet Associate DEVASC 200-901 Official Cert Guide (p. 163). Pearson Education. Edición de Kindle.
D is used with "all" configuration files of an API device to reduce the performance of a requesting API. So D is not the answer. In pagination you can include the first and maxlines needed in a query to request one or more lines within the rate limiting.
Payload limit - if number of requests exceeded than 413 code returned.
Rate limiting - if limit of the number of requests exceeded than 429 code returned.
Pagination breaks the content on equal parts (based on limit and offset) and returns them 1 by 1. So to my mind Pagination is correct.
A is correct. The question says that it is expecting 500+ records and EACH time returns only 25 (records). To me this says it's returning a valid document back to the user with exactly 25 records. If B were correct the API would return nothing or an invalid document. The question says it returns exactly 25 RECORDS. Pagination is the correct answer.
I don't think paginatin is correct, because it only displays 25 restults. If pagination was in place it would show all 550+ results, 25 results at a time but thats not whats happening. I think the answer is B Payload Limit
With rate limiting you limit the rate of API calls toward the API, while with payload limiting you limit the size of the API request bodies
B is correct
D is not correct. Question says "An application calls a REST" --> that means its talking about a single api call. Rate Limiting is to limit the "number of api calls"
So, we need to focus on REST API response size.
API Response size is actually a system level property- i.e. the server will define the payload size.
I think, B is correct.
Based in the follwoing definition of REST API Pagination as opposed to REST API Rate limiting in the following resource I think D is correct
Pagination: https://nordicapis.com/everything-you-need-to-know-about-api-pagination/
Rate Limiting: https://apisyouwonthate.com/blog/what-is-api-rate-limiting-all-about
upvoted 1 times
...
This section is not available anymore. Please use the main Exam Page.200-901 Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
Alan2036
Highly Voted 2 years, 10 months agomodatruhio
Highly Voted 2 years, 9 months agoTejas007
Most Recent 1 month agojohnbran
7 months agoMedra76
2 years, 1 month ago[Removed]
1 year, 1 month agoPlayer
2 years, 3 months agoPlayer
2 years, 3 months agorobmVT
2 years, 4 months agobpbenabd
2 years, 6 months agofffffff
2 years, 6 months agomememe6666
2 years, 3 months agoCiscoNinja
2 years, 9 months agoJohnJoe
2 years, 10 months agoFireTv
2 years, 10 months agoReadTheDoc
2 years, 10 months ago