Esri EAEP2201 Exam Dumps

Map image layers (map services) do not automatically detect schema changes, especially in registered enterprise geodatabases. Even with schema locking disabled, services cache the original schema at the time of publishing. To reflect the new field, you must overwrite the existing service.

From ArcGIS Server documentation:

''If the schema of a dataset is changed after a service is published (such as adding a field), the change is not automatically reflected in the service. You must overwrite the service or republish the map to reflect schema updates.''

Option B is not applicable; field visibility in the portal reflects what's in the published service definition.

Option C is related to editing access, not field visibility.

Option D is not a valid administrative action in this context.

ArcGIS Server -- Schema Changes and Map Service Behavior

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

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

By default, feature services limit the number of records returned in a single request (usually set to 1,000). To allow all 2,400 features to be returned in one call, the administrator needs to increase the ''Maximum number of records returned by the server'' (maxRecordCount) setting during or after publishing.

From the ArcGIS Server documentation:

''The maxRecordCount property defines the number of records returned by the server in a single request. To return all features, this value must be increased accordingly.''

Option A (adjust pooling) relates to concurrency and scalability, not data retrieval limits.

Option C would keep the default setting of 1,000, which would not meet the requirement.

Option D relates to visual performance, not record retrieval.

ArcGIS Server -- Feature Service Settings and Tuning for Performance

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