Which statement accurately describes functional user stories?

• A. Adds functionality to background processes
• B. Adds external system integration only
• C. Adds functionality end users can experience directly
• D. Are not related to user experience

Answer: (C)

Functional user stories focus on features that provide something a real user can interact with and experience directly in the app. They describe capabilities from the user’s perspective and are written so you can observe and test the resulting behavior in the UI or through the app’s available actions. That’s why the best choice says the stories add functionality end users can experience directly—the essence of a user-facing feature.

In practice, a functional user story might express something like a user being able to perform an action, see concrete results, and have those results verifiable by acceptance criteria (for example, clicking a button saves data and shows a confirmation message). While some stories may involve integrating with other systems, the core idea is that the user can do something meaningful with the product, not just that a backend task or external integration is happening behind the scenes. Statements about adding only background processing or about not relating to user experience don’t capture that user-visible, value-delivering aspect.