What is 'API mocking' and how does it enable frontend and backend teams to develop in parallel?
- A.API mocking creates a simulated API server that returns predefined responses matching the agreed contract (OpenAPI spec). Frontend developers can build against the mock API before the backend is ready. Backend developers implement against the spec without waiting for frontend integration. Tools: Prism (OpenAPI-based mock server), Mirage.js (in-browser mocking), WireMock, MSW (Mock Service Worker)
- B.API mocking is the practice of creating fake user accounts to test API behavior at scale
- C.API mocking is a security testing technique that impersonates production APIs to detect SSRF vulnerabilities
- D.API mocking automatically generates test data by analyzing production database schemas
Why A is correct