EAEP2201 Practice Exam Questions with Answers Enterprise Administration Professional 2201 Certification

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

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

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

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.

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

To enable SAML-based SSO, the ArcGIS Enterprise portal acts as the Service Provider (SP). To link it to an Identity Provider (IdP), you must register the portal’s SP metadata with the IdP and configure the portal to trust it.

From Esri's documentation:

“To complete SAML configuration, register the portal’s SAML service provider metadata with your organization’s identity provider, then configure the portal with the IdP metadata.”

Option A is for IWA (Kerberos), not SAML.

Option C refers to LDAP but doesn’t configure SAML or SSO.

Option D is not a valid standalone action for SAML integration.

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.

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.

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?

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

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

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

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.