Pass the Esri Technical Certification EAEP2201 Questions and answers with ExamsMirror

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

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.​

To meet the listed requirements, the appropriate user type is GIS Professional. This user type includes:

Access to ArcGIS Pro (essential for desktop GIS work and analysis)

Full content management and sharing privileges in the portal

Use of premium apps like ArcGIS StoryMaps, Experience Builder, and others

The Creator user type provides access to web-based apps and content but does not include ArcGIS Pro without an additional add-on license. The Editor user type is limited to viewing and editing existing data and does not support app creation or use of ArcGIS Pro.

Reference Source: ArcGIS Enterprise user type documentation — Application access matrix

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.

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.

When replacing SSL certificates in ArcGIS Enterprise components, ArcGIS Server and Portal for ArcGIS require the root and intermediate (issuing) certificates to be explicitly imported into their trust stores. Unlike the ArcGIS Data Store, which can often rely on the system-level trust store, ArcGIS Server and Portal maintain their own certificate trust management.

From the official ArcGIS Enterprise documentation:

“When using certificates issued by an internal or external CA, it is essential to also import the corresponding root and intermediate certificates into the Portal for ArcGIS and ArcGIS Server trust stores to ensure the certificate chain is validated properly.”

Option B is incorrect. Domain CA certificates are supported and recommended over self-signed certificates for internal deployments.

Option C refers to an acceptable format but does not address the issue, which is about importing the chain of trust.

Option D is incorrect; PKCS#12 (.pfx) certificates are supported but must be paired with the correct chain files.