Esri EAEP2201 Enterprise Administration Professional 2201 Exam Practice Test

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

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

For map services that are infrequently updated and contain numerous detailed features with complex symbology, configuring the service to use cached tiles is the most effective way to improve drawing performance. Cached map services pre-render map images at various scales and store them, allowing for faster display to users. This approach is particularly beneficial when the data does not change frequently, as it reduces the server's processing load during user interactions.​

Eliminating scale-dependent rendering (Option B) may lead to performance degradation, as it could result in rendering all features at all scales, increasing the amount of data processed and displayed unnecessarily.​

Switching to dedicated instances (Option C) can improve performance in some scenarios, but it also increases resource usage on the server. Given that the service is infrequently updated and the primary concern is drawing performance, caching is the more efficient and scalable solution.​

Reference Source: ArcGIS Enterprise documentation on optimizing map services for performance.​

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.

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.

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

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 prevent confusion among users who do not have access to certain functionalities, such as creating web maps and web scenes, the GIS administrator should configure the ArcGIS Enterprise home page to display only the items and tools that are accessible to the signed-in user. This customization ensures that users see a tailored interface that aligns with their permissions and responsibilities, reducing the likelihood of encountering inaccessible options.​

Configuring a maintenance notification (Option A) is more appropriate for temporary service outages or updates, not for managing user interface elements. Adjusting Page visibility settings (Option B) affects the visibility of entire pages but does not provide the granular control needed to tailor the home page based on user roles and permissions.​

Reference Source: ArcGIS Enterprise documentation on customizing the home page and user experience​

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.

During the upgrade from ArcGIS Enterprise 10.6.1 to 10.9.1, user type licensing is enforced. If the new license file includes more than one compatible user type (e.g., Creator and GIS Professional), existing members without a specified user type may be assigned temporary user types like "Standard (Temporary)" or "Lite (Temporary)." These temporary assignments prevent users from logging in until valid user types are manually assigned.​

This issue is not related to internet access (Option B) or the need to restart services (Option C).​

Reference Source: ArcGIS Enterprise documentation on user type licensing during upgrades

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.

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.

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.

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.

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.

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.

In ArcGIS Enterprise, the Creator user type includes full privileges for content creation, sharing, and administration. When paired with the Publisher role, it grants the user the ability to publish hosted feature layers, map image layers, and other services, as well as perform editing tasks on existing data. This combination is specifically designed for users who require both publishing and editing capabilities.

The Editor user type is limited to editing and cannot publish content. The GIS Professional user type provides access to ArcGIS Pro but, when assigned the Data Editor role, restricts the user from publishing content. Therefore, only the Creator user type with Publisher role supports both publishing and editing workflows.

Reference Source: ArcGIS Enterprise Administrator Guide — User types and roles

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