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 .

For field operations, Vector Tile Services are highly efficient and suitable for basemaps. They offer fast rendering, smaller file sizes, and are easily scalable across various devices, including those with limited bandwidth or processing capabilities. Vector tiles also support dynamic styling and are ideal for offline use, which is often necessary for field crews working in areas with limited connectivity.​

Cached map services (Option A) are raster-based and can be larger in size, making them less optimal for mobile use. Dynamic map services (Option C) require real-time data rendering, which can be resource-intensive and may not perform well in field conditions with limited connectivity.​

Reference Source: ArcGIS Enterprise documentation on customizing basemaps

In ArcGIS Enterprise, the Creator user type includes full privileges for content creation, sharing, and administration. When paired with the Publisher role, it grants the user the ability to publish hosted feature layers, map image layers, and other services, as well as perform editing tasks on existing data. This combination is specifically designed for users who require both publishing and editing capabilities.

The Editor user type is limited to editing and cannot publish content. The GIS Professional user type provides access to ArcGIS Pro but, when assigned the Data Editor role, restricts the user from publishing content. Therefore, only the Creator user type with Publisher role supports both publishing and editing workflows.

Reference Source: ArcGIS Enterprise Administrator Guide — User types and roles

=====================

Esri recommends using a Group Managed Service Account (gMSA) to run Portal for ArcGIS services in Windows environments. gMSAs automatically manage passwords , align with Active Directory policies , and are ideal for enterprise-scale deployments .

From Esri documentation:

“Using a group managed service account (gMSA) to run Portal for ArcGIS services improves security by allowing Windows to manage the password, reducing administrative overhead while meeting enterprise security requirements.”

Option B (regular AD account) is acceptable but requires manual password updates .

Option C and D are not secure or scalable for enterprise environments.

To publish and serve cached image services , the ArcGIS Server must be licensed as an Image Server . This licensing role is designed specifically for serving raster datasets , image services , and cache-based imagery workflows .

From ArcGIS Server documentation:

“The Image Server role is required to publish and manage image services, including those that serve pre-generated tile caches and support raster analytics.”

Option A (GIS Server) supports feature and map services, but not cached imagery .

Option C (Mission Server) is for real-time operations, unrelated to imagery or features.

When an organization purchases additional licenses (e.g., ArcGIS Pro), a new combined license file must be generated that includes both the existing entitlements and the newly purchased ones . This updated license file reflects the total number of licenses (original + new).

From the ArcGIS Enterprise Licensing documentation:

“When downloading a new license file from My Esri to assign additional licenses, the license file must reflect the complete set of user types and extensions required. You must generate a new license file that includes both the existing and new entitlements.”

Option A is incorrect because a license file with only the new licenses would overwrite the previous file.

Option B is incorrect for the same reason—partial license files are not valid for merging with existing licenses.

Option D does not accommodate the new licenses.

During the upgrade from ArcGIS Enterprise 10.6.1 to 10.9.1, user type licensing is enforced. If the new license file includes more than one compatible user type (e.g., Creator and GIS Professional), existing members without a specified user type may be assigned temporary user types like " Standard (Temporary) " or " Lite (Temporary). " These temporary assignments prevent users from logging in until valid user types are manually assigned.​

This issue is not related to internet access (Option B) or the need to restart services (Option C).​

Reference Source: ArcGIS Enterprise documentation on user type licensing during upgrades