GraphQL vs REST interview questions

1. A.the downside that POSTing to one URL forgoes REST's per-URL response caching, pushing caching into the client or layer
2. B.when one endpoint returns too little, forcing extra round-trips that a single nested selection can collapse
3. C.the property that every field, argument and result is described by an enforced, introspectable schema contract
4. D.retrieving more fields than the client needs, a waste that a precise per-field selection avoids

Answer + AI explanation with Pro

1. A.Over-fetching
2. B.Single endpoint
3. C.Under-fetching
4. D.HTTP caching tradeoff

Answer + AI explanation with Pro

1. A.Over-fetching — when one endpoint returns too little, forcing extra round-trips that a single nested selection can collapse
2. B.Over-fetching — retrieving more fields than the client needs, a waste that a precise per-field selection avoids
3. C.Over-fetching — the property that every field, argument and result is described by an enforced, introspectable schema contract
4. D.Over-fetching — the architecture where all operations are POSTed to one URL instead of many resource-specific REST paths

Answer + AI explanation with Pro

1. A.the architecture where all operations are POSTed to one URL instead of many resource-specific REST paths
2. B.the property that every field, argument and result is described by an enforced, introspectable schema contract
3. C.retrieving more fields than the client needs, a waste that a precise per-field selection avoids
4. D.when one endpoint returns too little, forcing extra round-trips that a single nested selection can collapse

Answer + AI explanation with Pro

1. A.Over-fetching
2. B.Strong typing
3. C.Under-fetching
4. D.Single endpoint

Answer + AI explanation with Pro

1. A.Under-fetching — when one endpoint returns too little, forcing extra round-trips that a single nested selection can collapse
2. B.Under-fetching — retrieving more fields than the client needs, a waste that a precise per-field selection avoids
3. C.Under-fetching — the architecture where all operations are POSTed to one URL instead of many resource-specific REST paths
4. D.Under-fetching — the property that every field, argument and result is described by an enforced, introspectable schema contract

Answer + AI explanation with Pro

1. A.when one endpoint returns too little, forcing extra round-trips that a single nested selection can collapse
2. B.the property that every field, argument and result is described by an enforced, introspectable schema contract
3. C.the downside that POSTing to one URL forgoes REST's per-URL response caching, pushing caching into the client or layer
4. D.the architecture where all operations are POSTed to one URL instead of many resource-specific REST paths

Answer + AI explanation with Pro

1. A.Under-fetching
2. B.Strong typing
3. C.Over-fetching
4. D.Single endpoint

Answer + AI explanation with Pro

1. A.Single endpoint — the downside that POSTing to one URL forgoes REST's per-URL response caching, pushing caching into the client or layer
2. B.Single endpoint — the architecture where all operations are POSTed to one URL instead of many resource-specific REST paths
3. C.Single endpoint — the property that every field, argument and result is described by an enforced, introspectable schema contract
4. D.Single endpoint — when one endpoint returns too little, forcing extra round-trips that a single nested selection can collapse

Answer + AI explanation with Pro

1. A.the downside that POSTing to one URL forgoes REST's per-URL response caching, pushing caching into the client or layer
2. B.the architecture where all operations are POSTed to one URL instead of many resource-specific REST paths
3. C.when one endpoint returns too little, forcing extra round-trips that a single nested selection can collapse
4. D.the property that every field, argument and result is described by an enforced, introspectable schema contract

Answer + AI explanation with Pro

1. A.Under-fetching
2. B.HTTP caching tradeoff
3. C.Strong typing
4. D.Single endpoint

Answer + AI explanation with Pro

1. A.Strong typing — the property that every field, argument and result is described by an enforced, introspectable schema contract
2. B.Strong typing — the architecture where all operations are POSTed to one URL instead of many resource-specific REST paths
3. C.Strong typing — the downside that POSTing to one URL forgoes REST's per-URL response caching, pushing caching into the client or layer
4. D.Strong typing — when one endpoint returns too little, forcing extra round-trips that a single nested selection can collapse

Answer + AI explanation with Pro

1. A.the downside that POSTing to one URL forgoes REST's per-URL response caching, pushing caching into the client or layer
2. B.the property that every field, argument and result is described by an enforced, introspectable schema contract
3. C.retrieving more fields than the client needs, a waste that a precise per-field selection avoids
4. D.the architecture where all operations are POSTed to one URL instead of many resource-specific REST paths

Answer + AI explanation with Pro

1. A.Strong typing
2. B.HTTP caching tradeoff
3. C.Over-fetching
4. D.Single endpoint

Answer + AI explanation with Pro

1. A.HTTP caching tradeoff — when one endpoint returns too little, forcing extra round-trips that a single nested selection can collapse
2. B.HTTP caching tradeoff — the architecture where all operations are POSTed to one URL instead of many resource-specific REST paths
3. C.HTTP caching tradeoff — the downside that POSTing to one URL forgoes REST's per-URL response caching, pushing caching into the client or layer
4. D.HTTP caching tradeoff — retrieving more fields than the client needs, a waste that a precise per-field selection avoids

Answer + AI explanation with Pro