When defining catalog categories and subcategories, what are some good practices to follow? (Choose two.)

Keeping the number of top-level categories to around 8-10 is indeed a good practice when defining catalog categories and subcategories. This approach helps maintain clarity and simplicity within the service catalog, making it easier for end-users to navigate and find the services they need. Having too many top-level categories can overwhelm users and lead to confusion, while having a manageable number ensures a more streamlined and user-friendly experience.

In addition to this, it's advantageous to group items in a way that avoids excessive complexity. This means limiting the subcategory hierarchy to 1-2 levels deep. Going too deep with subcategories can complicate the structure further and can hinder users' ability to quickly locate services and items. A flatter structure promotes easier navigation and a better understanding of the offerings available.

Aligning categories with Configuration Management Database (CMDB) classes or the ability for items to be assigned to multiple categories can be important considerations but are not universally recommended practices. For example, aligning with CMDB classes may not always be necessary if it complicates the service catalog unnecessarily. Similarly, while it's beneficial for items to be categorizable, enforcing a strict one-category assignment can limit flexibility and does not reflect how services may legitimately overlap in usage or function.