Free and Premium Esri EAEP2201 Dumps Questions Answers

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.

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.

The GIS Professional user type includes access to ArcGIS Pro, which is required for creating print layouts, charts, animations, and conducting advanced analysis. It also includes capabilities such as creating groups, editing features, and creating web apps within the ArcGIS Enterprise portal—without needing additional add-on licenses.

The Creator user type supports most web GIS tasks but does not include ArcGIS Pro unless an add-on license is assigned. The Editor user type is the most limited and is intended for editing existing content only, not for creating or managing groups or web applications.

Reference Source: ArcGIS Enterprise documentation — User types, capabilities, and included applications

By default, feature services limit the number of records returned in a single request (usually set to 1,000). To allow all 2,400 features to be returned in one call, the administrator needs to increase the “Maximum number of records returned by the server” (maxRecordCount) setting during or after publishing.

From the ArcGIS Server documentation:

“The maxRecordCount property defines the number of records returned by the server in a single request. To return all features, this value must be increased accordingly.”

Option A (adjust pooling) relates to concurrency and scalability, not data retrieval limits.

Option C would keep the default setting of 1,000, which would not meet the requirement.

Option D relates to visual performance, not record retrieval.

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

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

Map image layers (map services) do not automatically detect schema changes, especially in registered enterprise geodatabases. Even with schema locking disabled, services cache the original schema at the time of publishing. To reflect the new field, you must overwrite the existing service.

From ArcGIS Server documentation:

“If the schema of a dataset is changed after a service is published (such as adding a field), the change is not automatically reflected in the service. You must overwrite the service or republish the map to reflect schema updates.”

Option B is not applicable; field visibility in the portal reflects what's in the published service definition.

Option C is related to editing access, not field visibility.

Option D is not a valid administrative action in this context.

ArcGIS Enterprise Sites is a capability within ArcGIS Enterprise that enables organizations to create tailored web pages for sharing data and content. These sites are designed to be user-friendly for non-GIS users, allowing them to interact with, download, and create applications from the organization's data. Since the organization does not have access to ArcGIS Online, ArcGIS Enterprise Sites provides the necessary functionality within their existing deployment.​

ArcGIS Hub (Option A) is a separate product that requires ArcGIS Online. ArcGIS Experience Builder (Option C) is a tool for creating web applications but does not provide the comprehensive site-building capabilities needed for this scenario.​

Reference Source: ArcGIS Enterprise documentation on Sites

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

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.

A shared update group allows group members to edit each other’s items without needing to transfer ownership. This is ideal for collaborative editing and shared responsibility for applications, maps, or dashboards.

From Esri documentation:

“Shared update groups allow multiple members to update items shared with the group, even if they do not own the items.”

Option B doesn’t exist as a group type in ArcGIS Enterprise.

Option C allows viewing, but not editing others' content.

Option D applies to distributed collaboration, not shared editing.

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.

In ArcGIS Enterprise, data store items added via the Portal (such as those using .sde files for SQL Server) are represented as portal items. To allow other users to publish using that data store, the administrator must share the item with them, typically via a group.

From the official documentation:

“To allow other users to publish with a user-maintained data store, share the item with a group to which they belong. Users must have access to the data store item in the portal to publish services using it.”

Option A is not required—users don’t need admin rights to publish.

Option C refers to registering data in Server Manager, not managing access.

Option D is not a valid setting for data store items.

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​

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.