Esri Enterprise Administration Professional 2201 EAEP2201 Exam Dumps: Updated Questions & Answers (October 2025)

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.

For map services that are infrequently updated and contain numerous detailed features with complex symbology, configuring the service to use cached tiles is the most effective way to improve drawing performance. Cached map services pre-render map images at various scales and store them, allowing for faster display to users. This approach is particularly beneficial when the data does not change frequently, as it reduces the server's processing load during user interactions.​

Eliminating scale-dependent rendering (Option B) may lead to performance degradation, as it could result in rendering all features at all scales, increasing the amount of data processed and displayed unnecessarily.​

Switching to dedicated instances (Option C) can improve performance in some scenarios, but it also increases resource usage on the server. Given that the service is infrequently updated and the primary concern is drawing performance, caching is the more efficient and scalable solution.​

Reference Source: ArcGIS Enterprise documentation on optimizing map services for performance.​

After federating a GIS Server with the portal and registering a relational data store, the next step is to designate the GIS Server as the hosting server in the ArcGIS Enterprise portal. This configuration enables the portal to support the publishing of hosted feature layers and hosted scene layers. The hosting server must have both a relational data store and a tile cache data store configured to support these functionalities.​

Reference Source: ArcGIS Enterprise documentation on configuring a hosting server​

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

To enable SAML-based SSO, the ArcGIS Enterprise portal acts as the Service Provider (SP). To link it to an Identity Provider (IdP), you must register the portal’s SP metadata with the IdP and configure the portal to trust it.

From Esri's documentation:

“To complete SAML configuration, register the portal’s SAML service provider metadata with your organization’s identity provider, then configure the portal with the IdP metadata.”

Option A is for IWA (Kerberos), not SAML.

Option C refers to LDAP but doesn’t configure SAML or SSO.

Option D is not a valid standalone action for SAML integration.

To enable geocoding of addresses from CSV files uploaded to the ArcGIS Enterprise portal, the organization must designate a federated ArcGIS Server site as the hosting server. This hosting server must have a relational data store configured. Once set up, the portal can utilize a geocode utility service to process the addresses. This configuration allows users to map addresses from CSV files added to the portal.​

Reference Source: ArcGIS Enterprise documentation on configuring the portal to geocode addresses​

A distributed collaboration in ArcGIS Enterprise is designed to operate between two organizations only. Therefore, to collaborate with two separate ArcGIS Online organizations, the administrator must create separate collaborations between the Enterprise org and each ArcGIS Online org.

From Esri documentation:

“Each collaboration is established between two organizations. To collaborate with multiple organizations, you must set up multiple one-to-one collaborations.”

Option B is incorrect because adding external users from other orgs to a group doesn’t extend collaboration capabilities.

Option C is not supported — collaborations are strictly between two parties.

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