Esri EAEP2201 Enterprise Administration Professional 2201 Exam Practice Test

Esri recommends using a Group Managed Service Account (gMSA) to run Portal for ArcGIS services in Windows environments. gMSAs automatically manage passwords, align with Active Directory policies, and are ideal for enterprise-scale deployments.

From Esri documentation:

“Using a group managed service account (gMSA) to run Portal for ArcGIS services improves security by allowing Windows to manage the password, reducing administrative overhead while meeting enterprise security requirements.”

Option B (regular AD account) is acceptable but requires manual password updates.

Option C and D are not secure or scalable for enterprise environments.

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

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.

A distributed collaboration in ArcGIS Enterprise is designed to operate between two organizations only. Therefore, to collaborate with two separate ArcGIS Online organizations, the administrator must create separate collaborations between the Enterprise org and each ArcGIS Online org.

From Esri documentation:

“Each collaboration is established between two organizations. To collaborate with multiple organizations, you must set up multiple one-to-one collaborations.”

Option B is incorrect because adding external users from other orgs to a group doesn’t extend collaboration capabilities.

Option C is not supported — collaborations are strictly between two parties.

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

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

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

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

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.

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.

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

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

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.

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.

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.