Identifying Non-Functional Chatbot Requirements
A large retail chain plans to add a chatbot to its website for customer support operations. The company has the following requirements for the chatbot integration: • The chatbot must integrate with the existing knowledge base. • Agents must participate in the chat when there is a customer escalation. • The chatbot must adhere to all relevant regulatory and compliance requirements. • The chatbot must generate accurate and relevant responses to common customer queries. • The solution must scale to handle high volumes of customer interactions. You need to identify the non-functional chatbot requirements. Which two requirements are non-functional? Each correct answer presents a complete solution. (Choose two.) NOTE: Each correct selection is worth one point.
Community Votes
100% of anonymous learners picked answer AE. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
Distinguishing non-functional requirements (like scalability and compliance) from functional requirements (what the system does) is critical for solution planning.
This guide distinguishes between functional and non-functional requirements for a chatbot integration. It establishes that scalability and compliance are non-functional requirements, while integration, escalation, and response generation are functional.
Choosing options B, C, or D, which are functional requirements describing specific system behaviors or actions, rather than system qualities or constraints.
Community Discussion (3 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Options A and E are correct because non-functional requirements define the system's operational qualities and constraints. Option A specifies scalability, a classic performance quality attribute. Option E specifies compliance, which acts as a constraint on how the system must operate. Neither dictates specific functional behavior but rather how the system performs or restricts its operations.Why the Other Options Are Wrong
Options B, C, and D are functional requirements because they describe specific actions, behaviors, or integrations the system must perform. Option B defines an explicit escalation workflow. Option C describes the core functional output of generating responses. Option D specifies a required integration with another system. All three describe what the system must do, not how well it does it.Community Comment Notes
Commenters agree that scalability and compliance are the only non-functional requirements in the list. As WASSIM2020 noted, scalability "deals with the performance and capacity," making it a classic NFR. Tootru2bReal emphasized that "the rest are functional but you have to read carefully," highlighting the importance of distinguishing system actions from system qualities.Exam Strategy
When identifying non-functional requirements, look for keywords related to performance, security, scalability, reliability, and compliance. Functional requirements will always describe specific actions, data manipulations, or business processes the system must execute.