To fulfill a customer's requirement of visibility on products supported, which role is necessary?

The correct choice for fulfilling a customer's requirement for visibility on supported products is the role associated with read access for problems. This role allows users to view information related to problems, which typically includes details about products that are experiencing issues or have known defects. By having read access, users can see the supported products and any related incidents or changes linked to those products, thereby providing the visibility the customer requires.

This read capability is crucial for transparency in IT service management, as it ensures that stakeholders can access important information without making modifications to the data. This aligns with best practices in IT service management, where roles are carefully defined to provide appropriate levels of access based on individual needs.

The other roles, while relevant in certain contexts, do not provide the necessary visibility on supported products. The service owner role is more focused on oversight and ownership of services rather than direct visibility into specific product issues. The roles concerning problem business users usually involve a broader scope of engagement beyond just viewing supported products, while writing access is reserved for those who need to update or manage records, which is not required for simply viewing products.