EAEP2201 Enterprise Administration Professional 2201 Questions and Answers

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.

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​

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

Map image layers (map services) do not automatically detect schema changes, especially in registered enterprise geodatabases. Even with schema locking disabled, services cache the original schema at the time of publishing. To reflect the new field, you must overwrite the existing service.

From ArcGIS Server documentation:

“If the schema of a dataset is changed after a service is published (such as adding a field), the change is not automatically reflected in the service. You must overwrite the service or republish the map to reflect schema updates.”

Option B is not applicable; field visibility in the portal reflects what's in the published service definition.

Option C is related to editing access, not field visibility.

Option D is not a valid administrative action in this context.

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.

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.

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

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

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.

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

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.

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​