A BA's work ends up in a few kinds of deliverables. Knowing which one a situation calls for is half of an interview answer.
- Business requirements document (BRD): why the change is needed, its scope, the stakeholders and the business requirements, for the sponsor to sign off.
- Functional requirements or specification (FRS): what the system must do, in detail, for the people who build and test it.
- User stories with acceptance criteria: the same detail, written as small pieces in an agile backlog.
- Process map: who does what, in what order, with the decisions (often in BPMN).
- Data dictionary and mapping: what each field means and where it comes from.
- Traceability matrix: links each requirement to its source and its tests.
- UAT plan: how the business will test the solution before go-live.
Pick the deliverable for the audience: a sponsor wants scope and value, developers want testable detail, testers want traceability.