A calculated insight is a custom metric or measure that is derived from one or more data model objects or data lake objects in Data Cloud. A calculated insight can be used in segmentation to filter or group the data based on the calculated value. However, not all calculated insights can appear in the segmentation canvas. There are two requirements that must be met for a calculated insight to appear in the segmentation canvas:
* The calculated insight must contain a dimension including the Individual or Unified Individual Id. A dimension is a field that can be used to categorize or group the data, such as name, gender, or location.
The Individual or Unified Individual Id is a unique identifier for each individual profile in Data Cloud.
The calculated insight must include this dimension to link the calculated value to the individual profile and to enable segmentation based on the individual profile attributes.
* The primary key of the segmented table must be a dimension in the calculated insight. The primary key is a field that uniquely identifies each record in a table. The segmented table is the table that contains the data that is being segmented, such as the Customer or the Order table. The calculated insight must include the primary key of the segmented table as a dimension to ensure that the calculated value is associated with the correct record in the segmented table and to avoid duplication or inconsistency in the segmentation results.
References: Create a Calculated Insight, Use Insights in Data Cloud, Segmentation

The cause of this issue is that the new custom data model object (DMO) is not of category Profile. A category is a property of a DMO that defines its purpose and functionality in Data Cloud. There are three categories of DMOs: Profile, Event, and Other. Profile DMOs are used to store attributes of individuals or entities, such as name, email, address, etc. Event DMOs are used to store actions or interactions of individuals or entities, such as purchases, clicks, visits, etc. Other DMOs are used to store any other type of data that does not fit into the Profile or Event categories, such as products, locations, categories, etc. Only Profile DMOs can be used for creating segments in Data Cloud, as segments are based on the attributes of individuals or entities.
Therefore, if the new custom DMO is not of category Profile, it will not appear in the segmentation canvas.
The other options are not correct because they are not the cause of this issue. Data ingestion is not a prerequisite for creating segments, as segments can be created based on the data model schema without actual data. The new DMO does not need to have a relationship to the individual DMO, as segments can be created based on any Profile DMO, regardless of its relationship to other DMOs. Segmentation is not only supported for the Individual and Unified Individual DMOs, as segments can be created based on any Profile DMO, including custom ones. References: Create a Custom Data Model Object from an Existing Data Model Object, Create a Segment in Data Cloud, Data Model Object Category

Explanation
The Ignore Empty Value option in identity resolution allows customers to ignore empty fields when running reconciliation rules. Reconciliation rules are used to determine the final value of an attribute for a unified individual profile, based on the values from different sources. The Ignore Empty Value option can be set to true or false for each attribute in a reconciliation rule. If set to true, the reconciliation rule will skip any source that has an empty value for that attribute and move on to the next source in the priority order. If set to false, the reconciliation rule will consider any source that has an empty value for that attribute as a valid source and use it to populate the attribute value for the unified individual profile.
The other options are not correct descriptions of what the Ignore Empty Value option does in identity resolution. The Ignore Empty Value option does not affect the custom match rules or the standard match rules, which are used to identify and link individuals across different sources based on their attributes. The Ignore Empty Value option also does not ignore individual object records with empty fields when running identity resolution rules, as identity resolution rules operate on the attribute level, not the record level.
References:
* Data Cloud Identity Resolution Reconciliation Rule Input
* Configure Identity Resolution Rulesets
* Data and Identity in Data Cloud

To delete a data stream in Data Cloud, the underlying data lake object (DLO) must not have any dependencies or references to other objects or processes. The following two dependencies prevent a data stream from being deleted1:
* Data transform: This is a process that transforms the ingested data into a standardized format and structure for the data model. A data transform can use one or more DLOs as input or output. If a DLO is used in a data transform, it cannot be deleted until the data transform is removed or modified2.
* Data model object: This is an object that represents a type of entity or relationship in the data model. A data model object can be mapped to one or more DLOs to define its attributes and values. If a DLO is mapped to a data model object, it cannot be deleted until the mapping is removed or changed3.
References:
* 1: Delete a Data Stream article on Salesforce Help
* 2: [Data Transforms in Data Cloud] unit on Trailhead
* 3: [Data Model in Data Cloud] unit on Trailhead

Identity resolution is the process of creating unified profiles of individuals by matching and merging data from different sources. When there is conflicting information in the data model, such as different names, addresses, or phone numbers for the same person, identity resolution leverages reconciliation rules to select the most accurate and complete attributes for the unified profile. Reconciliation rules are configurable rules that define how to resolve conflicts based on criteria such as recency, frequency, source priority, or completeness. For example, a reconciliation rule can specify that the most recent name or the most frequent phone number should be selected for the unified profile. Reconciliation rules can be applied at the attribute level or the contact point level. References: Identity Resolution, Reconciliation Rules, Salesforce Data Cloud Exam Questions