ITIL 4 Foundation Practice Exam

What are 'warranty requirements' typically characterized as?

1. Unique marketing strategies

2. Non-functional requirements captured from stakeholders

3. Functional requirements for software development

4. Cost-related assessments of services

The correct answer is: Non-functional requirements captured from stakeholders

Warranty requirements are typically characterized as non-functional requirements that are gathered from stakeholders. These requirements refer to the assurances regarding a service's performance and reliability, focusing on aspects such as availability, capacity, security, and resilience. Warranty requirements ensure that a service meets the expected standards and provides value to the customer by guaranteeing certain performance attributes. Non-functional requirements are crucial because they govern how a system performs under various conditions, rather than what the system does—which is often defined by functional requirements. By emphasizing warranties, organizations can build trust with stakeholders and ensure that services remain reliable and effective in supporting business outcomes. The other choices do not accurately reflect the nature of warranty requirements. Unique marketing strategies pertain to how a service or product is promoted rather than its performance criteria. Functional requirements are related directly to specific functionalities or features of software, while cost-related assessments of services focus on financial metrics rather than performance guarantees.