EAEP2201 Enterprise Administration Professional 2201 Questions and Answers

Hosted 3D scene layers are stored in the tile cache data store , which is optimized for storing and serving cached 3D content, such as buildings and elevation surfaces. This data store supports scene layers published from ArcGIS Pro and allows for efficient rendering in 3D web scenes within the portal.

The relational data store is used for feature layers and structured tabular data. The raster data store supports large raster datasets for imagery layers. Neither is appropriate for 3D scene layer content. Thus, for hosted 3D scenes, the correct data store is the tile cache .

Reference Source: ArcGIS Enterprise Help — Data store types and publishing workflows

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.

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​

When an organization purchases additional licenses (e.g., ArcGIS Pro), a new combined license file must be generated that includes both the existing entitlements and the newly purchased ones . This updated license file reflects the total number of licenses (original + new).

From the ArcGIS Enterprise Licensing documentation:

“When downloading a new license file from My Esri to assign additional licenses, the license file must reflect the complete set of user types and extensions required. You must generate a new license file that includes both the existing and new entitlements.”

Option A is incorrect because a license file with only the new licenses would overwrite the previous file.

Option B is incorrect for the same reason—partial license files are not valid for merging with existing licenses.

Option D does not accommodate the new licenses.

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.

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.

To monitor usage patterns , including the number of requests and instances in use, ArcGIS Server provides statistics reports in Server Manager. These reports show peak and average service usage , helping administrators decide how to scale service instance counts .

From ArcGIS Server documentation:

“Use the ArcGIS Server Manager statistics reporting tool to monitor service usage trends over time. This data helps inform adjustments to instance counts.”

Option A gives only raw system metrics, not service-specific insights.

Option B (Debug logs) causes overhead and isn’t appropriate for monitoring trends.

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

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

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.

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.

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

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 standard feature analysis tools in ArcGIS Enterprise (e.g., buffer, overlay, aggregate points) require hosted feature layers , which depend on the relational data store (a component of ArcGIS Data Store). The relational data store is the default location for hosting feature layers.

From ArcGIS Enterprise documentation:

“To use the standard spatial analysis tools and create hosted feature layers, the ArcGIS Data Store (relational) must be configured and set as the default hosting location.”

Option A (spatiotemporal big data store) is used for real-time and big data feeds , not standard analysis.

Option C supports cached tiles , not feature layers.

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.