An organization needs to reduce the number of RDBMS users. ArcGIS Enterprise and ArcGIS Pro are implemented. Editors need to isolate edits and ensure…

Branch versioning is the correct model as it is designed for a service-based architecture, which is a key aspect of ArcGIS Enterprise. Editors interact with the data through a feature service, authenticating with their ArcGIS Enterprise named user accounts rather than requiring individual RDBMS user accounts. This directly addresses the primary requirement to reduce the number of RDBMS users. Furthermore, branch versioning provides the necessary functionality for editors to work in isolated versions and allows for a formal review and approval process before edits are merged into the default public version.

B. Traditional versioning: This model requires editors to have direct connections to the enterprise geodatabase, meaning each editor needs a dedicated RDBMS user account. This directly contradicts the main requirement to reduce RDBMS users.

C. Nonversioned editing: This model does not support long transactions or isolated editing environments (versions). Edits are applied directly to the business tables, which does not allow for a review process before edits become public.

1. Esri, ArcGIS Enterprise Documentation, "Versioning types in ArcGIS": This document explicitly contrasts the two versioning models. It states, "With traditional versioning, editors access the data directly...This requires that the editors have database user accounts...Branch versioning is the mechanism behind long transactions in ArcGIS Enterprise and is accessed through a feature service." This directly supports the choice of branch versioning to reduce RDBMS users.

Source: https://enterprise.arcgis.com/en/portal/latest/use/versioning-types.htm (Refer to the sections "Traditional versioning" and "Branch versioning").

2. Esri, ArcGIS Pro Documentation, "An overview of versioning": This guide details the workflows for each model. It clarifies that branch versioning is designed for service-based editing workflows, which aligns with the scenario. It notes, "Branch versioning is for web-based editing workflows...and is the basis for long transactions in a services-based environment."

Source: https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/overview/an-overview-of-versioning.htm (Refer to the comparison table and the "Branch versioning" section).

3. Esri, ArcGIS Enterprise Documentation, "Share branch versioned data": This page describes the publishing process required for branch versioning, reinforcing its service-oriented nature. It states, "To work with branch versioned data, you must publish it to an ArcGIS Enterprise portal...The data is accessed through the web feature layer." This confirms that users interact with a service, not the database directly.

Source: https://enterprise.arcgis.com/en/portal/latest/use/share-branch-versioned-data.htm (Refer to the introductory paragraph).