EAEP2201 Enterprise Administration Professional 2201 Questions and Answers

After upgrading, it's essential to reindex the portal to ensure that all items, groups, and users are correctly displayed. The administrator should check the Portal for ArcGIS index status to verify if the reindexing process has completed successfully. Incomplete or failed reindexing can result in missing content within the portal.​

Reference Source: ArcGIS Enterprise documentation on common problems and solutions after upgrading

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

For ArcGIS Enterprise deployments on Microsoft Azure that were initially installed manually, the recommended approach for upgrading is to manually upgrade each component. This involves downloading the latest installers for each component (Portal for ArcGIS, ArcGIS Server, ArcGIS Data Store, etc.) and following the standard upgrade procedures for each. This method ensures that each component is properly updated and configured according to the organization's specific setup.​

Using ArcGIS Enterprise Builder (Option B) is intended for new installations and is not suitable for upgrading existing deployments. ArcGIS Enterprise Cloud Builder for Microsoft Azure (Option C) is designed for deployments that were originally created using Cloud Builder; it cannot be used to upgrade deployments that were installed manually.​

Reference Source: ArcGIS Enterprise documentation on upgrading manually installed deployments​

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

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

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.

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.

When downloading a new license file from My Esri to accommodate the organization’s user needs, administrators should request the exact quantities identified in the internal needs assessment:

10 Viewer

40 Editor

20 GIS Professional

These quantities will be used to generate the new license file, which reflects the actual number of entitlements needed. Esri licensing is flexible in this regard, and the administrator can request different counts per type within their entitlements.

From the ArcGIS Enterprise Licensing documentation:

“When generating a new license file for your deployment, you can specify the number of each user type and role needed. The license file will reflect these values, and must match the needs of your organization.”

Option A provides insufficient licenses.

Option B omits the necessary Viewer licenses.

Option D reflects original entitlements, not the updated requirement.

To publish and serve cached image services, the ArcGIS Server must be licensed as an Image Server. This licensing role is designed specifically for serving raster datasets, image services, and cache-based imagery workflows.

From ArcGIS Server documentation:

“The Image Server role is required to publish and manage image services, including those that serve pre-generated tile caches and support raster analytics.”

Option A (GIS Server) supports feature and map services, but not cached imagery.

Option C (Mission Server) is for real-time operations, unrelated to imagery or features.

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

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.