Free Esri EAEP2201 Practice Exam with Questions & Answers | Set: 2

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​

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.

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.

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

This issue is consistent with desktop heap exhaustion, especially when a high number of ArcSOC processes (e.g., 390) are running on Windows. Desktop heap is a limited memory resource used for GUI and system object management. When it runs out, services can fail to start and produce XML-related errors.

Increasing the non-interactive desktop heap size in the Windows registry resolves this.

From Esri documentation:

“If the Windows desktop heap size is too low, ArcGIS Server may be unable to create new processes (ArcSOC), causing service failures and related internal server errors.”

Option B is a generic fix and won’t address the specific heap exhaustion issue.

Option C doesn’t help if the root issue is OS-level heap size limits.