Easy HTTP Question 13 of 226

What is the difference between path parameters and query parameters?

MERN Full Stack · Speak this in 60–90 seconds · Faridabad & Delhi NCR

ClientGET /users/1

ServerFind row

JSON back200 OK

Path parameters identify a specific resource, such as /users/42.

Why interviewers care about HTTP:

They want a clean

contrast on HTTP, not two memorised paragraphs.

Say what changes for

the developer, then one case where picking wrong hurts.

Stay structured

Name the idea, why it exists, then one short example.

Close cleanly

End with when you use it and one common pitfall.

Before you speak the answer, walk the interviewer through these steps:

1
Path parameters identify a
specific resource, such as /users/42.
2
Query parameters filter, sort,
or paginate, such as /users?role=admin&page=2.
3
Keep stable IDs in
the path and optional filters in the query string so URLs stay predictable.
4
Give an example
One tiny concrete case you can say aloud.
5
Common mistake
What juniors usually get wrong.
6
Close
When you pick this over the alternative.

Here's a short line you can speak, broken into clear beats:

Say this line

“Query parameters filter, sort, or paginate, such as /users?role=admin&page=2.”

Break into beats

Queryparametersfiltersortorpaginate

Speaking order

2987408337471632900

Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.

Path parameters identify a specific resource, such as /users/42. Query parameters filter, sort, or paginate, such as /users?role=admin&page=2.