Free Practice Questions for Esri EAEP2201 Exam

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.

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

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.

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

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

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

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

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.

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.