Pre-Order Your ArcGIS Pro Associate 2025 EAPA_2025

A relationship class defines a permanent association between a feature class and a table or between two feature classes in a geodatabase. Composite relationship classes enforce referential integrity, ensuring that related records remain consistent (e.g., when a parent record is deleted, related child records are also removed).

Attribute join (Option A) is temporary and does not enforce integrity.

Spatial join (Option B) requires spatial relationships and applies only between spatial datasets.

Relationship class (Option C) allows managing relationships between spatial and non-spatial tables with referential integrity.

Therefore, the correct answer is C.

—

In ArcGIS Pro, ared Xnext to a parameter in a geoprocessing tool typically indicates an invalid input due to conflicts with the current environment settings. One of the most common causes is when theProcessing Extentenvironment setting is configured in a way thatexcludesthe actual input features.

TheUniontool requires that input features fall within the set extent. If the Processing Extent does not cover any part of one or more input features, they are considered invalid and flagged with a red X, preventing the tool from running.

The software checks whether all input features are accessible within the defined extent. If they are not, this pre-validation error is triggered—even if the inputs are valid in terms of geometry or feature type.

Option A is incorrect because geometrical intersection is not a requirement for Union to run—it simply overlays features and includes all areas.

Option C is also incorrect, as the Union tool does indeed require polygon feature classes, but if incorrect feature types are used, a different error (not a red X related to extent) is shown.

This confirms that the red X in this scenario is caused by the Processing Extent settings not including the input features, making the correct answer B.

TheSpatial Jointool in ArcGIS Pro allows specifying aMatch Optionthat defines how spatial relationships between feature geometries are evaluated. In this scenario, the target and join features are of different geometry types—Points (trees) and Polylines (power lines)—so the appropriate match options are based on proximity rather than containment or other spatial relations.

Within a distance: Matches features based on a planar search radius, ignoring elevation (Z-value), making it ideal for cases where all trees within a certain horizontal distance from power lines should be included, regardless of height.

Within a distance 3D: Includes vertical (Z) differences in the search, which is unnecessary here since tree height shouldn't affect inclusion.

Within Clementini: Refers to a topological boundary relationship and is only valid for comparisons involving polygons—not points vs polylines.

Thus, to includeall trees within a specified horizontal buffer of the power lines, theWithin a distanceoption is the correct one.