Esri Enterprise Administration Professional 2201 EAEP2201 Exam Practice Test

Answer : A

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

Answer : C

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.

ArcGIS Enterprise -- ArcSOC process limits and Windows desktop heap size

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

Answer : A

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.

Answer : B

Answer : C

To prevent confusion among users who do not have access to certain functionalities, such as creating web maps and web scenes, the GIS administrator should configure the ArcGIS Enterprise home page to display only the items and tools that are accessible to the signed-in user. This customization ensures that users see a tailored interface that aligns with their permissions and responsibilities, reducing the likelihood of encountering inaccessible options.

Configuring a maintenance notification (Option A) is more appropriate for temporary service outages or updates, not for managing user interface elements. Adjusting Page visibility settings (Option B) affects the visibility of entire pages but does not provide the granular control needed to tailor the home page based on user roles and permissions.

Reference Source: ArcGIS Enterprise documentation on customizing the home page and user experience

Answer : C

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 Enterprise -- Post-Upgrade Troubleshooting and Web Adaptor Behavior

Answer : A

A shared update group allows group members to edit each other's items without needing to transfer ownership. This is ideal for collaborative editing and shared responsibility for applications, maps, or dashboards.

From Esri documentation:

''Shared update groups allow multiple members to update items shared with the group, even if they do not own the items.''

Option B doesn't exist as a group type in ArcGIS Enterprise.

Option C allows viewing, but not editing others' content.

Option D applies to distributed collaboration, not shared editing.

ArcGIS Enterprise -- Group Settings for Collaborative Management

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