EAEP2201 Esri Enterprise Administration Professional 2201 Free Practice Exam Questions (2025 Updated)

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.

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.

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

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.

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​

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

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

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 primary site administrator account in ArcGIS Server is a built-in account that bypasses external identity store configurations. To ensure only users from a configured identity store (e.g., Active Directory) can administer the site, the primary site admin account must be disabled after alternative administrative access has been confirmed.

From ArcGIS Server documentation:

“After you configure your ArcGIS Server to use users and roles from an identity store (LDAP or Active Directory), you can disable the primary site administrator account to prevent bypassing the identity store.”

Option B relates to token security, not access control.

Option C is about running the service securely, not defining user permissions.

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

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

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

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