A backend interview often asks you to explain more than the body of one function. An interviewer may change the request method, supply a zero value or cancel the caller before your code starts. This round uses six original contracts from data and service work. You have already learned the required operations. Read the signature, say which failures belong to the input boundary and preserve successful behavior while handling them. The checks use fresh inputs as well as a normal example. For the HTTP questions, all requests run locally through a recorder, so there is no server to deploy. Finish by explaining how the caller distinguishes missing data from a valid empty result and who owns the context passed across the boundary.