EAEP2201 Enterprise Administration Professional 2201 Questions and Answers

When using IWA through the Web Adaptor (IIS), the IIS server itself must be configured to deny anonymous access and allow Windows Authentication. Simply disabling anonymous access within the Portal settings is not enough.

From Esri’s web-tier authentication guide:

“For IWA to function as expected, anonymous access must be disabled in IIS for the ArcGIS Web Adaptor, and Windows Authentication must be enabled. If IIS still allows anonymous access, users will bypass authentication prompts.”

Option B is irrelevant here—user types don’t affect login behavior.

Option C is a content sync feature, not related to authentication.

Option D (Enable Windows Authentication) is correct only if it hasn't already been done, but the missing step is disabling anonymous access in IIS.

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​

ArcGIS GeoAnalytics Server is designed to perform distributed analysis on large volumes of spatial and temporal data. To efficiently process large datasets, it is recommended that each machine in the GeoAnalytics Server site has at least 16 GB of RAM and 4 CPU cores. However, for optimal performance, especially when handling very large datasets, increasing the available RAM can significantly improve processing times.​

In this scenario, the machine already has 16 GB of RAM and 4 cores. Adding more RAM would allow the GeoAnalytics Server to allocate more memory per job, enhancing its ability to process large datasets efficiently. Therefore, the recommended action is to add 16 GB of RAM to the GeoAnalytics Server machine.​

Reference Source: ArcGIS Enterprise documentation on GeoAnalytics Server system requirements and performance optimization.​

When expanding an ArcGIS Server site from one to three machines, the number of ArcSOC processes (service instances) will increase proportionally. For dedicated instances, each service's minimum and maximum instances are configured per machine, so tripling the number of machines will triple the number of dedicated ArcSOCs. For shared instances, the shared instance pool runs on each machine, and the number of shared instances is configured per machine. Therefore, the total number of ArcSOCs (both dedicated and shared) will be approximately three times greater after the expansion

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​

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.

The configuration store and server directories for ArcGIS Enterprise should be placed in a partition with ample disk space and stable read/write performance, as these directories store logs, cache, uploads, and critical site configuration information.

In this scenario:

The /home partition (20 GB) is insufficient for growth and operational overhead.

The /opt partition (75 GB) is moderately sized but still smaller than the /data partition.

The /data partition (150 GB) provides the most space, making it the best choice to ensure scalability and system reliability.

Best practice from ArcGIS Enterprise documentation recommends placing server directories and configuration stores on high-capacity partitions like /data when available.

Reference Source: ArcGIS Enterprise Installation Guide — File system and storage planning on Linux

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

These errors point to problems accessing the configuration store, which is commonly stored on a shared file location across ArcGIS Server machines. Intermittent access, latency, or I/O issues with the shared drive can cause synchronization failures and service visibility problems.

From Esri documentation:

“If ArcGIS Server cannot reliably access the configuration store, errors such as heartbeat failure, sync issues, and missing service configurations may occur. Always ensure the shared file location is on a reliable, supported file system with proper permissions and stability.”

Option A (VM resources) might impact general performance but not sync reliability.

Option C (patches) is important but doesn't fix shared drive instability.

Option D is not relevant in this context.

To publish feature classes as services in bulk from an enterprise geodatabase, it must first be registered with the ArcGIS Server site. This registration tells ArcGIS Server where to access the data directly for referenced service publishing. The proper way to do this is through ArcGIS Server Manager.

From ArcGIS Enterprise documentation:

“To publish layers directly from a registered enterprise geodatabase without copying data, you must register the geodatabase with your ArcGIS Server site using ArcGIS Server Manager.”

Option B is used for hosted services, not referenced publishing.

Option C is not the correct interface for registering data sources.

Option D involves hosting data, which is not applicable for referenced layers from a geodatabase.

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.

For multi-machine deployments, a Group Managed Service Account (gMSA) is the best option. It supports running services across multiple servers without requiring manual password updates, making it ideal for high-availability and enterprise security compliance.

From Esri’s deployment guidance:

“Use a group managed service account (gMSA) when installing ArcGIS Enterprise on multiple machines. gMSAs allow centralized password management and seamless cross-machine authentication.”

Option A could lead to password expiration issues.

Option C lacks centralized management and complicates maintenance.

When users perform standard analysis tasks in the portal Map Viewer, the hosting server executes geoprocessing operations that are computationally intensive. These operations require significant CPU resources. Monitoring CPU utilization helps ensure that the server can handle the increased load without performance degradation.​

While disk activity and network utilization are important, they are less directly impacted by standard analysis tasks compared to CPU usage. Therefore, CPU utilization is the primary resource to monitor in this scenario.​

Reference Source: ArcGIS Enterprise documentation on system performance monitoring.​

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.

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