EAEP2201 Sample Questions Answers

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.

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

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.

To publish feature classes as services in bulk from an enterprise geodatabase, it must first be registered with the ArcGIS Server site. This registration tells ArcGIS Server where to access the data directly for referenced service publishing. The proper way to do this is through ArcGIS Server Manager.

From ArcGIS Enterprise documentation:

“To publish layers directly from a registered enterprise geodatabase without copying data, you must register the geodatabase with your ArcGIS Server site using ArcGIS Server Manager.”

Option B is used for hosted services, not referenced publishing.

Option C is not the correct interface for registering data sources.

Option D involves hosting data, which is not applicable for referenced layers from a geodatabase.

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

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

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

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.

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.

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