Most Recent Esri EAEP2201 Exam Dumps

For ArcGIS Enterprise deployments on Microsoft Azure that were initially installed manually, the recommended approach for upgrading is to manually upgrade each component. This involves downloading the latest installers for each component (Portal for ArcGIS, ArcGIS Server, ArcGIS Data Store, etc.) and following the standard upgrade procedures for each. This method ensures that each component is properly updated and configured according to the organization's specific setup.

Using ArcGIS Enterprise Builder (Option B) is intended for new installations and is not suitable for upgrading existing deployments. ArcGIS Enterprise Cloud Builder for Microsoft Azure (Option C) is designed for deployments that were originally created using Cloud Builder; it cannot be used to upgrade deployments that were installed manually.

Reference Source: ArcGIS Enterprise documentation on upgrading manually installed deployments

To allow users to add new features without the ability to modify or delete existing ones, the feature service should have the 'Create' and 'Query' operations enabled. The 'Create' operation permits users to add new features, while the 'Query' operation allows them to view existing features. By not enabling the 'Update' and 'Delete' operations, users are restricted from making changes to or removing existing features. This configuration is ideal for workflows where data integrity is crucial, and only the addition of new data is permitted.

Enabling 'Update and sync' (Option A) would allow users to modify existing features and synchronize changes, which is not desired in this scenario. 'Extract and create' (Option C) is not a standard combination of operations for controlling editing permissions in feature services.

Reference Source: ArcGIS Server documentation on editor permissions for feature services

The correct solution is to place ArcGIS Enterprise in read-only mode. This is an administrative function designed specifically to prevent changes to content or configuration while still allowing users to view and access existing items.

From the official ArcGIS Enterprise documentation:

''Read-only mode allows an administrator to restrict changes to the portal. When enabled, no users (including administrators) can create, update, or delete items, groups, or users. However, users can still search for and view items, access content, and use apps and services.''

This feature is typically used during maintenance windows or before performing disaster recovery tasks to preserve system state.

Option B is incorrect because changing user roles to Viewer would not prevent content changes by administrators or other roles with publishing privileges.

Option C refers to cloning, which is not a preventive or temporary access control measure, but rather a method for standby deployments or replication.

Option D (disabling the Web Adaptor) would disrupt access entirely, which does not match the requirement to allow viewing.

ArcGIS Enterprise Portal Administration Guide -- Read-only mode feature behavior and impact on user interactions

Registering the database as a data store item in the ArcGIS Enterprise portal allows administrators to control who can publish services referencing the data. By sharing the data store item with specific groups or individuals, administrators can restrict publishing capabilities to authorized users. At the same time, all users can be granted appropriate permissions to access and edit the data directly in the user-managed database, independent of the publishing privileges.

Registering the database as an ArcGIS-managed data store in Server Manager does not provide the same level of control over publishing permissions. Registering it as a relational data store in ArcGIS Data Store is intended for managed data storage and does not apply to user-managed databases.

Reference Source: ArcGIS Enterprise documentation on registering user-managed data stores and controlling access.