Data Management
Data Management questions test whether you understand how ArcGIS Pro stores, connects to, and protects data rather than how to click through menus. Know the difference between a project (an .aprx file that references data and stores maps, layouts, and connections) and the data itself, which lives in folders, file geodatabases, enterprise geodatabases, or services. A project does not embed your feature classes; it stores paths and connection files, so moving or renaming source data breaks layers.
Understand the geodatabase hierarchy: feature datasets group feature classes that share a spatial reference, and relationship classes, domains, and subtypes enforce data integrity. Domains constrain attribute values (coded or range); subtypes partition a feature class by category; attribute rules go further with validation, calculation, and constraint logic. Know field types and the trap of changing a field type on populated data.
Coordinate systems are a favorite trap. Distinguish a geographic coordinate system (degrees) from a projected one (linear units). A layer can display in the map's coordinate system while its source remains in another. Reprojection is a permanent transformation of the data; changing the map frame is display-only.
Worked example
A colleague copies a feature class from one file geodatabase into a feature dataset that uses a different spatial reference. The tool projects the data on the fly during copy. Rule of thumb: copying into a feature dataset forces the dataset's coordinate system; copying into the geodatabase root preserves the source.
Traps to watch: assuming deleting a layer deletes the data (it does not), confusing a project's default geodatabase with the source geodatabase, and forgetting that locked files or open schemas block edits.