1617. Keyset pagination — Subscription Billing — implementation variant 17

DBMS Published 30 Sept 2026 Updated 30 Sept 2026 0 Views Verified

In a Subscription Billing application, implement this production problem: Fetch the next 50 products after the last seen ID. The API/service receives user input and must return or modify data safely. Give the SQL solution, explain why it works, and show how the same operation is called from the selected stack.

Looking for the latest Sarkari Result 2026 updates? Check the latest government exam results, merit lists and result updates on Sarkari Resultess.

Answer & Explanation

4 Answers

Verified

Option A

SELECT * FROM the_table;

Additional Explanation

Incorrect: it does not implement the stated business rule and may modify/fetch the wrong rows.

Verified Correct Answer

Option B

SELECT id,name,price FROM products WHERE status='active' AND id > :last_id ORDER BY id LIMIT 50;

Additional Explanation

Keyset pagination avoids large offsets and is usually preferable for high-volume APIs when a stable ordered key is available.

Verified

Option C

UPDATE the_table SET status='active';

Additional Explanation

Incorrect: it does not implement the stated business rule and may modify/fetch the wrong rows.

Verified

Option D

DELETE FROM the_table;

Additional Explanation

Incorrect: it does not implement the stated business rule and may modify/fetch the wrong rows.