EAEP2201 Enterprise Administration Professional 2201 Questions and Answers

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

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.

When replacing SSL certificates in ArcGIS Enterprise components, ArcGIS Server and Portal for ArcGIS require the root and intermediate (issuing) certificates to be explicitly imported into their trust stores. Unlike the ArcGIS Data Store, which can often rely on the system-level trust store, ArcGIS Server and Portal maintain their own certificate trust management.

From the official ArcGIS Enterprise documentation:

“When using certificates issued by an internal or external CA, it is essential to also import the corresponding root and intermediate certificates into the Portal for ArcGIS and ArcGIS Server trust stores to ensure the certificate chain is validated properly.”

Option B is incorrect. Domain CA certificates are supported and recommended over self-signed certificates for internal deployments.

Option C refers to an acceptable format but does not address the issue, which is about importing the chain of trust.

Option D is incorrect; PKCS#12 (.pfx) certificates are supported but must be paired with the correct chain files.

Custom cached basemaps are stored as tile cache files on disk and are not included in backups created by the webgisdr tool or the ArcGIS Data Store backup utility. Therefore, to ensure these basemaps can be restored in the event of a disaster, it's essential to manually back up the cache directories where these tiles are stored. This involves copying the cache folders to a secure backup location and ensuring they are kept in sync with any updates made to the basemaps.​

The webgisdr tool (Option A) is used for backing up and restoring the ArcGIS Enterprise configuration and content but does not include custom tile caches. The ArcGIS Data Store backup utility (Option C) is used for backing up hosted feature layers and other data managed by the ArcGIS Data Store, not custom cached basemaps.​

Reference Source: ArcGIS Enterprise documentation on backup and restore best practices​

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​

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

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

To enable geocoding of addresses from CSV files uploaded to the ArcGIS Enterprise portal, the organization must designate a federated ArcGIS Server site as the hosting server. This hosting server must have a relational data store configured. Once set up, the portal can utilize a geocode utility service to process the addresses. This configuration allows users to map addresses from CSV files added to the portal.​

Reference Source: ArcGIS Enterprise documentation on configuring the portal to geocode addresses​

To allow users to add new features without the ability to modify or delete existing ones, the feature service should have the "Create" and "Query" operations enabled. The "Create" operation permits users to add new features, while the "Query" operation allows them to view existing features. By not enabling the "Update" and "Delete" operations, users are restricted from making changes to or removing existing features. This configuration is ideal for workflows where data integrity is crucial, and only the addition of new data is permitted.​

Enabling "Update and sync" (Option A) would allow users to modify existing features and synchronize changes, which is not desired in this scenario. "Extract and create" (Option C) is not a standard combination of operations for controlling editing permissions in feature services.​

Reference Source: ArcGIS Server documentation on editor permissions for feature services

The webgisdr utility is the official tool used to both back up and restore ArcGIS Enterprise deployments. When restoring a backup, this tool ensures all components—Portal for ArcGIS, ArcGIS Server (federated), ArcGIS Data Store, and associated configurations—are restored in the correct sequence and with integrity.

The utility reads from a configuration file that defines the backup location, type, and parameters. webgisdr orchestrates the entire restoration process automatically. Running restoredatastore (Option B) individually is not required and may only restore part of the deployment, such as the relational store. Restore (Option C) is not a valid utility for ArcGIS Enterprise.

Reference Source: ArcGIS Enterprise documentation — Web GIS Disaster Recovery tool (webgisdr)

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

To publish feature classes as services in bulk from an enterprise geodatabase, it must first be registered 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 through ArcGIS 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.”

Option B is used for hosted services, not referenced publishing.

Option C is not the correct interface for registering data sources.

Option D involves hosting data, which is not applicable for referenced layers from a geodatabase.