EAEP2201 Questions and Answers

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

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.

For multi-machine deployments, a Group Managed Service Account (gMSA) is the best option. It supports running services across multiple servers without requiring manual password updates, making it ideal for high-availability and enterprise security compliance.

From Esri’s deployment guidance:

“Use a group managed service account (gMSA) when installing ArcGIS Enterprise on multiple machines. gMSAs allow centralized password management and seamless cross-machine authentication.”

Option A could lead to password expiration issues.

Option C lacks centralized management and complicates maintenance.

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.

For map services that are infrequently updated and contain numerous detailed features with complex symbology, configuring the service to use cached tiles is the most effective way to improve drawing performance. Cached map services pre-render map images at various scales and store them, allowing for faster display to users. This approach is particularly beneficial when the data does not change frequently, as it reduces the server's processing load during user interactions.​

Eliminating scale-dependent rendering (Option B) may lead to performance degradation, as it could result in rendering all features at all scales, increasing the amount of data processed and displayed unnecessarily.​

Switching to dedicated instances (Option C) can improve performance in some scenarios, but it also increases resource usage on the server. Given that the service is infrequently updated and the primary concern is drawing performance, caching is the more efficient and scalable solution.​

Reference Source: ArcGIS Enterprise documentation on optimizing map services for performance.​

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.

When using IWA through the Web Adaptor (IIS), the IIS server itself must be configured to deny anonymous access and allow Windows Authentication. Simply disabling anonymous access within the Portal settings is not enough.

From Esri’s web-tier authentication guide:

“For IWA to function as expected, anonymous access must be disabled in IIS for the ArcGIS Web Adaptor, and Windows Authentication must be enabled. If IIS still allows anonymous access, users will bypass authentication prompts.”

Option B is irrelevant here—user types don’t affect login behavior.

Option C is a content sync feature, not related to authentication.

Option D (Enable Windows Authentication) is correct only if it hasn't already been done, but the missing step is disabling anonymous access in IIS.

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​

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

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