The issue arises because a new feature class was added to an already versioned feature dataset. In traditional versioning, adding a feature class requires the administrator to first unregister the dataset, add the new class, and then re-register the entire dataset as versioned. The new feature class is not automatically registered. This creates an inconsistent state where the new class is not versioned, preventing edit sessions from starting correctly on the dataset. Re-registering the feature dataset ensures that all its contents, including the newly added feature class, are properly registered for versioned editing, resolving the issue.

A. Connecting as the data owner will not resolve the underlying technical issue, as the dataset is in an inconsistent versioning state. Permissions are not the root cause.

B. Unregistering the feature dataset permanently is a destructive action that would delete all existing versions and their associated edits, leading to significant data loss.

1. Esri ArcGIS Pro Documentation, "Register data as versioned": This document outlines the required workflow for schema changes. It states, "To add or remove a feature class from a feature dataset that participates in traditional versioning, you must first unregister the feature dataset as versioned." This confirms that adding a class requires an unregister/re-register cycle, which the administrator must complete to restore edit functionality.

Source: Esri. (n.d.). Register data as versioned. ArcGIS Pro Documentation. Retrieved from https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/overview/register-data-as-versioned.htm (See the section on "Registering and unregistering feature datasets").

2. Esri ArcGIS Pro Documentation, "Schema locking": This resource explains that exclusive schema locks are required to make changes to a dataset's structure, and these locks cannot be obtained on versioned data. This is the underlying reason why the dataset must be unregistered before adding a feature class.

Source: Esri. (n.d.). Schema locking. ArcGIS Pro Documentation. Retrieved from https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/overview/schema-locking.htm

3. Esri Training, "Deploying and Maintaining a Multiuser Geodatabase (for ArcGIS 10.5)" Courseware: This course covers administrative workflows for enterprise geodatabases. Module 7, "Geodatabase Maintenance," details the procedures for performing schema changes on versioned data, emphasizing the necessity of the unregister-modify-reregister workflow to maintain data integrity and functionality.

Source: Esri Training Courseware, "Deploying and Maintaining a Multiuser Geodatabase," Module 7, "Geodatabase Maintenance," section on "Modifying Versioned Data."

The core issue is resource contention between write-intensive editing operations and potentially read-intensive public queries hitting the same database. Creating separate database instances is a standard architectural pattern for workload isolation. This approach dedicates one instance to transactional editing and another for public-facing, read-only services. Data can be synchronized from the editing instance to the public instance using methods like geodatabase replication. This physical separation ensures that high traffic from public use does not consume resources (CPU, I/O, memory) needed by editors, thereby resolving the performance degradation during peak hours.

A. Build new feature datasets: This is a logical data organization method within a single geodatabase and does not separate the underlying database resources or resolve performance contention.

B. Separate permissions for public services: This is a security measure to control access. It does not prevent high-volume, read-only queries from the public from consuming database resources and impacting editor performance.

1. Esri Documentation - ArcGIS Enterprise, System Design Strategies: The concept of separating workloads is a key system design strategy. "For a highly available deployment that must support a large number of users and a variety of applications and services, you may need to segment your architecture by function... For example, you might have one site for internal editing and analysis and another for public-facing applications." This functional segmentation often implies separate data stores (instances or databases) to prevent contention.

Source: ArcGIS Enterprise Documentation, "Deployment patterns," section on "Highly available and disaster recovery-focused architecture."

2. Esri Documentation - ArcGIS Pro, Geodatabase Replication: Replication is the mechanism used to synchronize data between separate geodatabases (which can be in different instances). "Replication also allows you to disconnect from the network and edit or query the data... Another use is to create a copy of the data to a different location to be used for a specific purpose, such as reporting." This supports the pattern of creating a separate, query-optimized copy for public use.

Source: ArcGIS Pro Documentation, "What is geodatabase replication?"

3. Esri White Paper - Architecting the ArcGIS Platform: Best Practices: This document frequently discusses separating systems based on workload. It recommends isolating intensive workflows. "Isolate systems that have different availability or performance requirements... For example, a public-facing web mapping application may have different requirements than a back-office data editing and maintenance system." This architectural principle directly supports using separate database instances.

Source: Architecting the ArcGIS Platform: Best Practices (May 2021), Page 12, "System Isolation."

The question's premise is technically inaccurate, as editors in child versions must reconcile to see changes from the default version, regardless of the versioning type. However, interpreting the question's likely intent—to allow other applications or non-versioned users to see changes made to the default version—the correct answer is A. Registering a dataset as traditional versioned with the "move edits to base" option ensures that once edits are posted to the default version, they are written directly to the base business tables. This makes the changes immediately visible to any client or application reading the non-versioned state of the data, without requiring them to access a specific version.

B. Branch versioning is designed for feature service editing workflows and, like traditional versioning, requires a reconcile operation to update a child version with changes from default.

C. Enabling archiving creates a historical log of transactions for auditing or temporal analysis but does not alter the core versioning behavior of isolating edits until reconciliation.

---

1. Esri ArcGIS Pro Documentation, "Versioning options in ArcGIS Pro": This document explicitly states for the "Register as versioned with the option to move edits to base" setting: "When edits are saved, they are moved from the delta tables to the base tables... Because the edits are in the base tables, the data is accessible to other applications that may not be able to read the delta tables in a geodatabase." (Found under Manage Data > Geodatabases > Traditional versioning > Register data as versioned).

2. Esri ArcGIS Pro Documentation, "A tour of traditional versioning": This guide clarifies the standard workflow: "To merge the changes, you reconcile your version with the default version. This process applies the edits made in the default version to your version." This confirms that reconciliation is the required step for a child version to see parent changes. (Found under Manage Data > Geodatabases > Traditional versioning).

3. Esri ArcGIS Pro Documentation, "Overview of branch versioning": This document describes the branch versioning model, which is based on a service-oriented architecture. The workflow still involves discrete versions that must be reconciled to incorporate changes from other versions, such as default. (Found under Manage Data > Geodatabases > Branch versioning).

A mosaic dataset is the optimal storage mechanism for this scenario. It is a data model within an enterprise geodatabase specifically designed to manage, view, and query large collections of raster and image data. It stores metadata and references to the source imagery (which can remain in a centralized folder) rather than the pixels themselves. This allows for dynamic mosaicking, on-the-fly processing, and efficient serving of imagery as a single layer across an organization, which directly meets the administrator's requirements for enterprise-wide access.

A. Raster dataset: A raster dataset typically represents a single raster image. It is not designed to manage or visualize a collection of multiple images as a single, cohesive layer.

B. Raster catalog: A raster catalog is a legacy data model for managing collections of rasters. While functional, it has been largely superseded by the mosaic dataset, which offers superior performance and more advanced capabilities.

1. Esri ArcGIS Pro Documentation, "What is a mosaic dataset?": "A mosaic dataset is a data model in the geodatabase that is used to manage a collection of raster datasets (images) stored as a catalog and viewed as a single mosaicked image." This source confirms its purpose for managing collections.

2. Esri ArcGIS Pro Documentation, "Fundamentals of raster storage": In the section comparing storage options, it states, "Mosaic datasets are ideal for managing and visualizing large collections of imagery... They are also the best way to serve imagery." This highlights its suitability for enterprise access.

3. Esri ArcGIS Pro Documentation, "Raster catalog properties": "Raster catalogs are useful for displaying adjacent, non-overlapping raster datasets... If you have overlapping raster datasets, it is recommended that you use a mosaic dataset." This indicates the mosaic dataset is the more modern and recommended approach.

A database view is a stored SQL query that functions as a virtual table. A data administrator can create a view that selects only a specific subset of fields (columns) from the source feature class's business table. By granting user permissions on this view while revoking or denying permissions on the underlying base table, access to the sensitive fields is effectively restricted at the database level. This is a standard, robust security practice for implementing column-level security in an enterprise geodatabase, ensuring unauthorized users cannot access the restricted data regardless of the client application used.

A. Layer file: A layer file (.lyrx) only controls the display properties and field visibility within a specific ArcGIS Pro map or project; it does not enforce security at the data source.

B. Query layer: A query layer is an ArcGIS mechanism for displaying data from a SQL query, but it is not the fundamental database security object. The underlying security is managed by database permissions on views or tables.

1. Esri ArcGIS Pro Documentation, "Views in a geodatabase": "You can use views to control access to data by granting privileges on the view to specific users. This allows you to limit the columns (fields) or rows (features or records) the users can see." This document explicitly states that views are a primary method for restricting access to specific columns.

2. Esri ArcGIS Pro Documentation, "Data access and security": "To restrict access to certain columns in a table, you can create a view on the table that includes only the non-sensitive columns. Then grant privileges on the view to users and revoke privileges from the base table." This section provides a step-by-step conceptual model for the exact scenario in the question.

3. Pennsylvania State University, GEOG 485: GIS Database Development and Administration, Lesson 6: Multiuser Geodatabase Administration: The courseware explains security models, stating, "A common strategy for restricting access to certain rows or columns in a table is to create a database view...You can then grant privileges on the view to a role, and add users to that role." This confirms the use of views as a standard academic and professional practice for field-level security.