EAEP2201 Exam Dumps and Practice Questions

After federating a GIS Server with the portal and registering a relational data store, the next step is to designate the GIS Server as the hosting server in 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 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.

ArcGIS Enterprise -- Multi-Machine Installations and Secure Service Account Practices

After upgrading, it's essential to reindex the portal to ensure that all items, groups, and users are correctly displayed. The administrator should check the Portal for ArcGIS index status to 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

These errors point to problems accessing the configuration store, which is commonly stored on a shared file location across ArcGIS Server machines. Intermittent access, latency, or I/O issues with the shared drive can cause synchronization failures and service visibility problems.

From Esri documentation:

''If ArcGIS Server cannot reliably access the configuration store, errors such as heartbeat failure, sync issues, and missing service configurations may occur. Always ensure the shared file location is on a reliable, supported file system with proper permissions and stability.''

Option A (VM resources) might impact general performance but not sync reliability.

Option C (patches) is important but doesn't fix shared drive instability.

Option D is not relevant in this context.

ArcGIS Server -- High Availability Configuration Store Troubleshooting

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