To implement branch versioning in ArcGIS Pro, what change must be made?

To implement branch versioning in ArcGIS Pro, you must change the connection to use branch versioning. This is a crucial step because branch versioning relies on a specific type of geodatabase setup that differs from traditional versioning. When using branch versioning, each branch represents a different version of the data, allowing for more flexible editing workflows, especially in collaborative environments.

By establishing a connection explicitly geared towards branch versioning, ArcGIS Pro can manage edits and changes in a way that accommodates the branching model, enabling users to create, manage, and merge versions effectively. This connection change facilitates enhanced data editing capabilities and supports a newer architecture for versioning compared to traditional methods. The underlying geodatabase must be configured properly to support branch versioning, which is what this connection adjustment accomplishes.

The other options relate to alternative procedures or versioning methods that do not align with the requirements for branch versioning, which emphasizes the need for a specific connection to leverage its functionalities.