Pass the Esri Technical Certification EAEP2201 Questions and answers with CertsForce

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

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

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.

To publish and serve cached image services, the ArcGIS Server must be licensed as an Image Server. This licensing role is designed specifically for serving raster datasets, image services, and cache-based imagery workflows.

From ArcGIS Server documentation:

“The Image Server role is required to publish and manage image services, including those that serve pre-generated tile caches and support raster analytics.”

Option A (GIS Server) supports feature and map services, but not cached imagery.

Option C (Mission Server) is for real-time operations, unrelated to imagery or features.

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.

For ArcGIS Enterprise deployments on Microsoft Azure that were initially installed manually, the recommended approach for upgrading is to manually upgrade each component. This involves downloading the latest installers for each component (Portal for ArcGIS, ArcGIS Server, ArcGIS Data Store, etc.) and following the standard upgrade procedures for each. This method ensures that each component is properly updated and configured according to the organization's specific setup.​

Using ArcGIS Enterprise Builder (Option B) is intended for new installations and is not suitable for upgrading existing deployments. ArcGIS Enterprise Cloud Builder for Microsoft Azure (Option C) is designed for deployments that were originally created using Cloud Builder; it cannot be used to upgrade deployments that were installed manually.​

Reference Source: ArcGIS Enterprise documentation on upgrading manually installed deployments​

To meet the listed requirements, the appropriate user type is GIS Professional. This user type includes:

Access to ArcGIS Pro (essential for desktop GIS work and analysis)

Full content management and sharing privileges in the portal

Use of premium apps like ArcGIS StoryMaps, Experience Builder, and others

The Creator user type provides access to web-based apps and content but does not include ArcGIS Pro without an additional add-on license. The Editor user type is limited to viewing and editing existing data and does not support app creation or use of ArcGIS Pro.

Reference Source: ArcGIS Enterprise user type documentation — Application access matrix

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