Pass the Esri Technical Certification EAEP2201 Questions and answers with ExamsMirror

The webgisdr utility is the official tool used to both back up and restore ArcGIS Enterprise deployments. When restoring a backup, this tool ensures all components—Portal for ArcGIS, ArcGIS Server (federated), ArcGIS Data Store, and associated configurations—are restored in the correct sequence and with integrity.

The utility reads from a configuration file that defines the backup location, type, and parameters. webgisdr orchestrates the entire restoration process automatically. Running restoredatastore (Option B) individually is not required and may only restore part of the deployment, such as the relational store. Restore (Option C) is not a valid utility for ArcGIS Enterprise.

Reference Source: ArcGIS Enterprise documentation — Web GIS Disaster Recovery tool (webgisdr)

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

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​

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.

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.

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

By default, feature services limit the number of records returned in a single request (usually set to 1,000). To allow all 2,400 features to be returned in one call, the administrator needs to increase the “Maximum number of records returned by the server” (maxRecordCount) setting during or after publishing.

From the ArcGIS Server documentation:

“The maxRecordCount property defines the number of records returned by the server in a single request. To return all features, this value must be increased accordingly.”

Option A (adjust pooling) relates to concurrency and scalability, not data retrieval limits.

Option C would keep the default setting of 1,000, which would not meet the requirement.

Option D relates to visual performance, not record retrieval.

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.

After federating a GIS Server with the portal and registering a relational data store, the next step is to designate the GIS Server as the hosting server in the ArcGIS Enterprise portal. This configuration enables the portal to support the publishing of hosted feature layers and hosted scene layers. The hosting server must have both a relational data store and a tile cache data store configured to support these functionalities.​

Reference Source: ArcGIS Enterprise documentation on configuring a hosting server​