EAEP2201 Enterprise Administration Professional 2201 Questions and Answers

To license the ArcGIS Data Interoperability extension on a federated ArcGIS Server site, the administrator must use the Software Authorization Wizard. This is the officially supported and recommended method provided by Esri for authorizing additional extensions to ArcGIS Server.

According to the ArcGIS Enterprise Installation Guide and Esri’s administration best practices:

The Software Authorization Wizard is the tool used to input license information and authorize software features such as the Data Interoperability extension.

This wizard can be launched after installation or from the ArcGIS Server program group at any time.

Once the license is applied using the wizard, it is necessary to restart the ArcGIS Server service so that the newly authorized extension is loaded properly.

Option A is incorrect because Esri does not support manually modifying license JSON files. Doing so can corrupt the licensing configuration and is not documented or recommended.

Option C is incorrect because the ArcGIS Server installation program does not apply or manage licenses—it is used solely for installing the core server software.

Therefore, the correct method is to use the Software Authorization Wizard, apply the license file, and restart the ArcGIS Server service to activate the extension.

Reference Source: ArcGIS Enterprise Administration and Installation documentation – ArcGIS Server Software Authorization and Extension Licensing section.

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.

After an upgrade, Portal for ArcGIS often changes web elements, scripts, and cached content. If the browser is using old cached files, the portal page may not render correctly, and authentication may fail. Clearing the browser cache ensures that new files are loaded.

From Esri documentation:

“After upgrading ArcGIS Enterprise, clear the browser’s cache to ensure that all updated components and scripts are loaded properly.”

Option A is a diagnostic tool, not a fix.

Option B may be excessive if the issue is simply browser cache.

Option D is not a standard troubleshooting step.

Custom cached basemaps are stored as tile cache files on disk and are not included in backups created by the webgisdr tool or the ArcGIS Data Store backup utility. Therefore, to ensure these basemaps can be restored in the event of a disaster, it's essential to manually back up the cache directories where these tiles are stored. This involves copying the cache folders to a secure backup location and ensuring they are kept in sync with any updates made to the basemaps.​

The webgisdr tool (Option A) is used for backing up and restoring the ArcGIS Enterprise configuration and content but does not include custom tile caches. The ArcGIS Data Store backup utility (Option C) is used for backing up hosted feature layers and other data managed by the ArcGIS Data Store, not custom cached basemaps.​

Reference Source: ArcGIS Enterprise documentation on backup and restore best practices​

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

The contractor should publish a hosted feature service. Hosted feature services are managed entirely by the ArcGIS Data Store, not by the ArcGIS Server site directly. This means they consume fewer server resources since they are not managed by a dedicated ArcGIS Server site’s memory or CPU at runtime the way traditional services are.

From ArcGIS documentation:

“Hosted feature layers (services) are stored in and powered by the ArcGIS Data Store, relieving ArcGIS Server from managing service processes. This is ideal for testing, lightweight apps, or non-production workflows when minimizing load on the GIS Server is desired.”

Option B (Non-hosted map service) would require server-side management and is more resource-intensive.

Option C (Scene service) is used for 3D visualization and is not appropriate for 2D hydrant location data.

Option D (Non-hosted feature service) would also consume more ArcGIS Server resources.

For environments without internet access, the organization can use the patchnotification.bat utility to check for available patches and updates. This utility can be run from the command line and provides information about the current patch status of the ArcGIS Enterprise components. Administrators can then manually download the necessary patches from another machine with internet access and transfer them to the internal environment for installation.​

Reference Source: ArcGIS Enterprise documentation on checking for and installing software patches and updates​

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 perform incremental backups using the webgisdr tool, point-in-time recovery must be enabled on the relational data store. This creates transaction logs needed for differential backups and aligns with best practices for enterprise-level backup strategies.

From Esri documentation:

“Incremental backups can only be used with a relational data store when point-in-time recovery is enabled. This enables transaction log capture needed for delta backups.”

Option A is unrelated to backup functionality.

Option C is not required unless performance tuning is needed.

This issue is consistent with desktop heap exhaustion, especially when a high number of ArcSOC processes (e.g., 390) are running on Windows. Desktop heap is a limited memory resource used for GUI and system object management. When it runs out, services can fail to start and produce XML-related errors.

Increasing the non-interactive desktop heap size in the Windows registry resolves this.

From Esri documentation:

“If the Windows desktop heap size is too low, ArcGIS Server may be unable to create new processes (ArcSOC), causing service failures and related internal server errors.”

Option B is a generic fix and won’t address the specific heap exhaustion issue.

Option C doesn’t help if the root issue is OS-level heap size limits.

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

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.

The Spatiotemporal big data store is designed for massive datasets and optimized for high-speed visualization, time-enabled querying, and big data analytics. It is ideal for storing millions of point features such as sensors or oil rig locations, especially when performance and scalability are critical.

From ArcGIS documentation:

“The spatiotemporal big data store is designed for writing and querying large volumes of spatial and temporal data. It’s optimized for visualizing high-density datasets in web maps.”

Option B (Relational) works for moderate data volumes but may not scale well.

Option C supports cached tiles, not dynamic feature access.