EAEP2201 EAEP2201 Questions and Answers

To meet the listed requirements, the appropriate user type isGIS 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 likeArcGIS StoryMaps,Experience Builder, and others

TheCreatoruser type provides access to web-based apps and content butdoes not include ArcGIS Prowithout an additional add-on license. TheEditoruser 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

When using aWeb Adaptorto accessArcGIS Server Manager,administrative access must be explicitly enabled during Web Adaptor configuration. If this setting is not enabled, even valid administrator accounts (including Windows accounts with elevated privileges) will be unable to access ArcGIS Server Manager via the Web Adaptor.

This is a common configuration oversight. The federation, IWA setup, and domain certificate are not the causes here. A domain certificate is valid within trusted enterprise networks, and Windows accounts can access services through IWA once configured correctly.

Reference Source:ArcGIS Enterprise documentation — Enabling administrative access for Web Adaptor

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

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​

After federating a GIS Server with the portal and registering a relational data store, the next step is to designate the GIS Server as thehosting serverin the ArcGIS Enterprise portal. This configuration enables the portal to support the publishing of hosted feature layers and hosted scene layers. The hosting server must have both a relational data store and a tile cache data store configured to support these functionalities.​

Reference Source:ArcGIS Enterprise documentation on configuring a hosting server​

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

ArcGIS GeoAnalytics Server is designed to perform distributed analysis on large volumes of spatial and temporal data. It is particularly suited for workflows that involve analyzing patterns over time and space, such as identifying interstates with the most incidents over decades and correlating vehicle behavior (like speeding and braking) with accident locations.​

GeoAnalytics Server provides tools for aggregating data, detecting incidents, and reconstructing tracks, which are essential for understanding complex transportation datasets. Its distributed computing framework allows for efficient processing of big data, making it the appropriate choice for the described workflow.​

GeoEvent Server (Option B) is primarily used for real-time data processing and event detection, which is not the focus of this analysis. Notebook Server (Option C) supports interactive data science and analysis workflows using Jupyter notebooks but does not provide the same level of performance and scalability for big data analysis as GeoAnalytics Server.​

Reference Source:ArcGIS Enterprise documentation on GeoAnalytics Server capabilities and use cases.

When users perform standard analysis tasks in the portal Map Viewer, the hostingserver 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.​

Theprimary site administrator accountin ArcGIS Server is abuilt-in accountthat bypasses external identity store configurations. To ensureonly users from a configured identity store(e.g., Active Directory) can administer the site, the primary site admin account must bedisabledafter 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.”

OptionBrelates to token security, not access control.

OptionCis about running the service securely, not defining user permissions.

After upgrading, it's essential toreindexthe portal to ensure that all items, groups, and users are correctly displayed. The administrator should check thePortal for ArcGIS index statusto verify if the reindexing process has completed successfully. Incomplete or failed reindexing can result in missing content within the portal.​

Reference Source:ArcGIS Enterprise documentation on common problems and solutions after upgrading

In ArcGIS Enterprise,data store itemsadded via the Portal (such as those using .sde files for SQL Server) are represented asportal items. To allow other users to publish using that data store, the administrator mustshare the item with them, typically via agroup.

From the official documentation:

“To allow other users to publish with a user-maintained data store, share the item with a group to which they belong. Users must have access to the data store item in the portal to publish services using it.”

OptionAis not required—users don’t need admin rights to publish.

OptionCrefers to registering data in Server Manager, not managing access.

OptionDis not a valid setting for data store items.

In ArcGIS Enterprise, theCreatoruser type includes full privileges for content creation, sharing, and administration. When paired with thePublisherrole, 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.

TheEditoruser type is limited to editing and cannot publish content. TheGIS Professionaluser type provides access to ArcGIS Pro but, when assigned theData Editorrole, restricts the user from publishing content. Therefore, only theCreator user type with Publisher rolesupports 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 beregistered 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 throughArcGIS 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.”

OptionBis used for hosted services, not referenced publishing.

OptionCis not the correct interface for registering data sources.

OptionDinvolves hosting data, which is not applicable for referenced layers from a geodatabase.

For environments without internet access, the organization can use thepatchnotification.batutility 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​

Vector tile services are optimized for high-resolution display and efficient storage, making them ideal for offline workflows. They allow for smaller file sizes compared to raster tiles and support dynamic styling. Additionally, vector tile services can be updated by regenerating tiles from updated feature services, facilitating easy incorporation of data updates. ​

Hosted 3D scene layers are stored in thetile 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.

Therelational data storeis used for feature layers and structured tabular data. Theraster data storesupports large raster datasets for imagery layers. Neither is appropriate for 3D scene layer content. Thus, for hosted 3D scenes, the correct data store is thetile cache.

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

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 implementa dedicated ArcGIS Server site for analysisas part of a federated multi-site deployment.

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

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