Free Esri EAEP2201 Practice Exam with Questions & Answers

The GIS Professional user type includes access to ArcGIS Pro, which is required for creating print layouts, charts, animations, and conducting advanced analysis. It also includes capabilities such as creating groups, editing features, and creating web apps within the ArcGIS Enterprise portal—without needing additional add-on licenses.

The Creator user type supports most web GIS tasks but does not include ArcGIS Pro unless an add-on license is assigned. The Editor user type is the most limited and is intended for editing existing content only, not for creating or managing groups or web applications.

Reference Source: ArcGIS Enterprise documentation — User types, capabilities, and included applications

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.

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)

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

These errors point to problems accessing the configuration store, which is commonly stored on a shared file location across ArcGIS Server machines. Intermittent access, latency, or I/O issues with the shared drive can cause synchronization failures and service visibility problems.

From Esri documentation:

“If ArcGIS Server cannot reliably access the configuration store, errors such as heartbeat failure, sync issues, and missing service configurations may occur. Always ensure the shared file location is on a reliable, supported file system with proper permissions and stability.”

Option A (VM resources) might impact general performance but not sync reliability.

Option C (patches) is important but doesn't fix shared drive instability.

Option D is not relevant in this context.

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

To enable geocoding of addresses from CSV files uploaded to the ArcGIS Enterprise portal, the organization must designate a federated ArcGIS Server site as the hosting server. This hosting server must have a relational data store configured. Once set up, the portal can utilize a geocode utility service to process the addresses. This configuration allows users to map addresses from CSV files added to the portal.​

Reference Source: ArcGIS Enterprise documentation on configuring the portal to geocode addresses​

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.

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.

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

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