Skip to content

Tracks Drills Topics Technologies Tech stacks Skill areas

Tracks Drills Guides

Loading

Aporeon

Technical interview practice, from one developer to another.

Guides About Editorial standards Support Privacy Terms Refund policy

HTTP API Semantics - .NET Full Stack | Aporeon

.NET Full Stack

HTTP API Semantics

HTTP methods, outcomes, update semantics, media types, caching, preconditions, browser access, streaming, and retry signals.

11 drillsPractice one at a timeOrdered pathConcept questionArchitecture scenarioComparison question

Recommended start

Safe and idempotent methods

Explains HTTP safety and idempotency, then connects those guarantees to retries, side effects, and API design.

Medium~7 minStep 1 of 11

Practice this drill Choose another

Search

11 of 11 shown

1Safe and idempotent methodsRecommended startExplains HTTP safety and idempotency, then connects those guarantees to retries, side effects, and API design.Concept questionMedium~7 min.NETASP.NET CorePractice 2

Practice order

11 drillsOne at a time

1Safe and idempotent methodsUp next / Medium / ~7 min
2Choose HTTP status codesMedium / ~10 min
3PUT vs PATCHMedium / ~7 min

Choose HTTP status codesMaps creation, updates, asynchronous work, validation, authorization, conflicts, and failures to useful HTTP outcomes.Architecture scenarioMedium~10 min.NETASP.NET Core

Practice

3PUT vs PATCHCompares replacement and partial-update semantics, including omitted fields, patch formats, validation, and concurrency.Comparison questionMedium~7 min.NETASP.NET CorePractice

4HTTP content negotiationDistinguishes request and response media types and designs predictable negotiation, rejection, documentation, and caching behavior.Concept questionMedium~7 minPractice

5API Cache-ControlChooses response cache directives for public, private, sensitive, and revalidated API data without leaking user-specific content.Architecture scenarioHard~12 min.NETASP.NET CorePractice

6ETag conditional GETImplements representation-aware ETags and conditional GETs correctly, including validators, 304 metadata, authorization, cache variation, generation cost, and tests.Concept questionHard~9 min.NETASP.NET CorePractice

7If-Match and lost updatesConnects HTTP preconditions to atomic database concurrency checks and honest 412 or 428 API behavior.Architecture scenarioHard~12 min.NETASP.NET CorePractice

8CORS and preflightExplains browser same-origin enforcement, preflight requests, credentials, middleware behavior, and why CORS is not authorization.Concept questionMedium~7 minPractice

9Stream large responsesDesigns cancellation-aware response streaming with bounded memory, correct resource ownership, and practical download behavior.Architecture scenarioHard~12 min.NETASP.NET CorePractice

10Retry signals and budgetsCoordinates server retry signals with client backoff, deadlines, idempotency, overload protection, and bounded retry budgets.Architecture scenarioHard~12 min.NETASP.NET CorePractice

11Output vs response cachingCompares server-controlled output caching with HTTP cache semantics and defines safe keys, variation, invalidation, identity, and multi-instance behavior.Comparison questionMedium~7 min.NETASP.NET CorePractice

4

HTTP content negotiation

Medium / ~7 min

5API Cache-ControlHard / ~12 min

6ETag conditional GETHard / ~9 min

7If-Match and lost updatesHard / ~12 min

8CORS and preflightMedium / ~7 min

+3 more drills in this section