Pass the Esri Technical EAEP2201 Questions and answers with ValidTests

This issue is consistent withdesktop heap exhaustion, especially when a high number ofArcSOC 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 thenon-interactive desktop heap sizein 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.”

OptionBis a generic fix and won’t address the specific heap exhaustion issue.

OptionCdoesn’t help if the root issue is OS-level heap size limits.

Adistributed collaborationin ArcGIS Enterprise is designed to operatebetween two organizations only. Therefore, to collaborate withtwo separate ArcGIS Online organizations, the administrator must createseparate collaborationsbetween the Enterprise org and each ArcGIS Online org.

From Esri documentation:

“Each collaboration is established between two organizations. To collaborate with multiple organizations, you must set up multiple one-to-one collaborations.”

OptionBis incorrect because adding external users from other orgs to a group doesn’t extend collaboration capabilities.

OptionCis not supported — collaborations are strictlybetween two parties.

To performincremental backupsusing thewebgisdr tool,point-in-time recoverymust be enabled on therelational data store. This creates transaction logs needed for differential backups and aligns with best practices for enterprise-level backup strategies.

From Esri documentation:

“Incremental backups can only be used with a relational data store when point-in-time recovery is enabled. This enables transaction log capture needed for delta backups.”

OptionAis unrelated to backup functionality.

OptionCis not required unless performance tuning is needed.

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​

During the upgrade from ArcGIS Enterprise 10.6.1 to 10.9.1, user type licensing is enforced. If the new license file includes more than one compatible user type (e.g., Creator and GIS Professional), existing members without a specified user type may be assigned temporary user types like "Standard (Temporary)" or "Lite (Temporary)." These temporary assignments prevent users from logging in until valid user types are manually assigned.​

This issue is not related to internet access (Option B) or the need to restart services (Option C).​

Reference Source:ArcGIS Enterprise documentation on user type licensing during upgrades

When usingIWA through the Web Adaptor (IIS), theIIS server itself must be configuredto deny anonymous access and allow Windows Authentication. Simply disabling anonymous accesswithin the Portal settingsisnot 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.”

OptionBis irrelevant here—user types don’t affect login behavior.

OptionCis a content sync feature, not related to authentication.

OptionD(Enable Windows Authentication) is correctonly if it hasn't already been done, but the missing step isdisabling anonymous accessin IIS.

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.

Thestandard feature analysis toolsin ArcGIS Enterprise (e.g., buffer, overlay, aggregate points) requirehosted feature layers, which depend on therelational 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.”

OptionA(spatiotemporal big data store) is used forreal-time and big data feeds, not standard analysis.

OptionCsupportscached tiles, not feature layers.

In ArcGIS Enterprise, when performing raster analysis that results in feature data (e.g., vector outputs), theArcGIS Hosting Serveris responsible for hosting the resulting feature services. The Raster Analytics Server processes the raster data, and the output is then stored in the ArcGIS Data Store associated with the Hosting Server, which subsequently serves the feature layer.​

The Image Hosting Server is primarily used for hosting large imagery datasets and does not handle feature services. The Raster Analytics Server conducts the analysis but does not host the output services.​

Reference Source:ArcGIS Enterprise documentation on configuring and deploying raster analytics​

ArcGIS Enterprise Sites is a capability within ArcGIS Enterprise that enables organizations to create tailored web pages for sharing data and content. These sites are designed to be user-friendly for non-GIS users, allowing them to interact with, download, and create applications from the organization's data. Since the organization does not have access to ArcGIS Online, ArcGIS Enterprise Sites provides the necessary functionality within their existing deployment.​

ArcGIS Hub (Option A) is a separate product that requires ArcGIS Online. ArcGIS Experience Builder (Option C) is a tool for creating web applications but does not provide the comprehensive site-building capabilities needed for this scenario.​

Reference Source: ArcGIS Enterprise documentation on Sites

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