Pass the Esri Technical Certification EAEP2201 Questions and answers with CertsForce

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

Workload separation is a best practice in ArcGIS Enterprise architecture. By dedicating a separate ArcGIS Server site for analysis tasks, such as geoprocessing services used in web tools, system resources can be managed more effectively, and performance can be improved. This configuration avoids overloading a single site and ensures that interactive web applications are not affected by resource-intensive analysis tools.

Adding more machines to the same site (Option A) does not isolate workloads and may still result in contention. Installing an entirely new ArcGIS Enterprise deployment (Option C) increases complexity and administration effort unnecessarily. The recommended solution is to implement a dedicated ArcGIS Server site for analysis as part of a federated multi-site deployment.

Reference Source: ArcGIS Enterprise System Design Strategies — Workload separation practices

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

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

ArcGIS Enterprise doesn’t currently offer automated license expiration email alerts. However, administrators can use administrative scripts to query license status and generate reports that can be automated using task schedulers (e.g., Windows Task Scheduler).

From Esri guidance:

“Administrators can monitor license status using the ArcGIS REST API or scripting tools. Automating these checks allows timely action before licenses expire.”

Option A is not a native capability of the portal.

Option C is not tied to licensing and is only useful as a passive alert.

Option D is not a valid license management option.

The Spatiotemporal big data store is designed for massive datasets and optimized for high-speed visualization, time-enabled querying, and big data analytics. It is ideal for storing millions of point features such as sensors or oil rig locations, especially when performance and scalability are critical.

From ArcGIS documentation:

“The spatiotemporal big data store is designed for writing and querying large volumes of spatial and temporal data. It’s optimized for visualizing high-density datasets in web maps.”

Option B (Relational) works for moderate data volumes but may not scale well.

Option C supports cached tiles, not dynamic feature access.

Hosted 3D scene layers are stored in the tile cache data store, which is optimized for storing and serving cached 3D content, such as buildings and elevation surfaces. This data store supports scene layers published from ArcGIS Pro and allows for efficient rendering in 3D web scenes within the portal.

The relational data store is used for feature layers and structured tabular data. The raster data store supports large raster datasets for imagery layers. Neither is appropriate for 3D scene layer content. Thus, for hosted 3D scenes, the correct data store is the tile cache.

Reference Source: ArcGIS Enterprise Help — Data store types and publishing workflows

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.

For IWA authentication, Active Directory users are not automatically added to the ArcGIS Enterprise portal. They must either be:

Manually added as members, or

Automatically created at first login if auto-creation is enabled.

Since the new users are assigned to the gisusers group but cannot sign in or create content, it's clear that their accounts have not yet been added to the portal.

From ArcGIS Enterprise documentation:

“Integrated Windows Authentication (IWA) allows users to sign in with their Windows credentials. However, users must still be members of the portal. You can manually add users or enable automatic account creation during login.”

Option B is invalid since default user type settings do not prevent login.

Option C is incorrect because synchronization is not time-based—it’s account-creation dependent.