A nettle-path consumer app is ready before the origin permit API exists. How can API Management let the contract be called without a live backend?
Select an answer to reveal the explanation.
Short Explanation
Backend not ready? Mock the response in APIM so the nettle-path app can call the contract today.
Full Explanation
When the nettle-path consumer app is ready before the origin permit API exists, configure APIM mock responses on the operations so callers can exercise the agreed contract without a live backend. Mocks return representative status codes and payloads from the gateway, unblocking client integration, contract tests, and UX work while the origin is still under construction in another team’s sprint.
Deleting the API until the backend ships blocks the consumer and removes the shared contract surface both sides need. Replacing the API with a Logic Apps designer workflow as the only option abandons the APIM mock technique and may change authentication, URLs, and error shapes mid-integration. Pointing every operation at Redis and returning cache keys as HTTP bodies does not implement APIM’s mock-response feature and invents a storage-centric contract nobody agreed to.
Exam caveat: mocks are for contract-first parallel work—remember to remove or disable mocks and point operations at the real origin before production cutover so partners do not ship against permanent fake data.
Operational check: enable mock responses on the permit API operations, call them from the nettle-path app through the gateway, confirm status codes and bodies match the published contract, then switch the backend to the live origin when ready and retest with the same client.