The Enterprise Administration Professional 2201 (EAEP2201)

When expanding an ArcGIS Server site from one to three machines, the number of ArcSOC processes (service instances) will increase proportionally. For dedicated instances, each service ' s minimum and maximum instances are configured per machine, so tripling the number of machines will triple the number of dedicated ArcSOCs. For shared instances, the shared instance pool runs on each machine, and the number of shared instances is configured per machine. Therefore, the total number of ArcSOCs (both dedicated and shared) will be approximately three times greater after the expansion

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

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

For field operations, Vector Tile Services are highly efficient and suitable for basemaps. They offer fast rendering, smaller file sizes, and are easily scalable across various devices, including those with limited bandwidth or processing capabilities. Vector tiles also support dynamic styling and are ideal for offline use, which is often necessary for field crews working in areas with limited connectivity.​

Cached map services (Option A) are raster-based and can be larger in size, making them less optimal for mobile use. Dynamic map services (Option C) require real-time data rendering, which can be resource-intensive and may not perform well in field conditions with limited connectivity.​

Reference Source: ArcGIS Enterprise documentation on customizing basemaps

A distributed collaboration in ArcGIS Enterprise is designed to operate between two organizations only . Therefore, to collaborate with two separate ArcGIS Online organizations , the administrator must create separate collaborations between 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.”

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

Option C is not supported — collaborations are strictly between two parties .

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

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

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

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

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.

To perform incremental backups using the webgisdr tool , point-in-time recovery must be enabled on the relational 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.”

Option A is unrelated to backup functionality.

Option C is not required unless performance tuning is needed.