Within theCommon Service Data Model (CSDM),information objectsare used to representnon-CI data entitiesthat provide important business or governance context but are not configuration items themselves. These objects are especially important when extending service visibility beyond pure infrastructure and application relationships.

The use case described inOption A—understandingasset lifecycle compliance in a Business Application context—explicitly requires information objects. Asset lifecycle data (such as financial state, depreciation, warranty, and compliance milestones) is typically managed in IT Asset Management (ITAM) and must beassociated to Business Applicationswithout converting every asset-related data point into a CI. Information objects enable this linkage while maintaining clean CMDB boundaries.

Option B focuses on event-to-incident automation, which relies onCIs, technical services, and operational relationships, not information objects. Option C (proactive case management) is primarily aCSM and service offeringuse case. Option D (SecOps risk context) relies onapplication services and business application relationships, not information objects. Option E (business service impact) is addressed throughservice modeling and service mapping, again without requiring information objects.

Information objects are introduced as organizations mature and need to integrategovernance, financial, or compliance datawith service and application models—making asset lifecycle compliance the correct match.

Therefore, the correct answer isA.