Esri EAEP2201 Exam Dumps

To license the ArcGIS Data Interoperability extension on a federated ArcGIS Server site, the administrator must use the Software Authorization Wizard. This is the officially supported and recommended method provided by Esri for authorizing additional extensions to ArcGIS Server.

According to the ArcGIS Enterprise Installation Guide and Esri's administration best practices:

The Software Authorization Wizard is the tool used to input license information and authorize software features such as the Data Interoperability extension.

This wizard can be launched after installation or from the ArcGIS Server program group at any time.

Once the license is applied using the wizard, it is necessary to restart the ArcGIS Server service so that the newly authorized extension is loaded properly.

Option A is incorrect because Esri does not support manually modifying license JSON files. Doing so can corrupt the licensing configuration and is not documented or recommended.

Option C is incorrect because the ArcGIS Server installation program does not apply or manage licenses---it is used solely for installing the core server software.

Therefore, the correct method is to use the Software Authorization Wizard, apply the license file, and restart the ArcGIS Server service to activate the extension.

Reference Source: ArcGIS Enterprise Administration and Installation documentation -- ArcGIS Server Software Authorization and Extension Licensing section.

In ArcGIS Enterprise, the Creator user type includes full privileges for content creation, sharing, and administration. When paired with the Publisher role, it grants the user the ability to publish hosted feature layers, map image layers, and other services, as well as perform editing tasks on existing data. This combination is specifically designed for users who require both publishing and editing capabilities.

The Editor user type is limited to editing and cannot publish content. The GIS Professional user type provides access to ArcGIS Pro but, when assigned the Data Editor role, restricts the user from publishing content. Therefore, only the Creator user type with Publisher role supports both publishing and editing workflows.

Reference Source: ArcGIS Enterprise Administrator Guide --- User types and roles

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

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

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

When an organization purchases additional licenses (e.g., ArcGIS Pro), a new combined license file must be generated that includes both the existing entitlements and the newly purchased ones. This updated license file reflects the total number of licenses (original + new).

From the ArcGIS Enterprise Licensing documentation:

''When downloading a new license file from My Esri to assign additional licenses, the license file must reflect the complete set of user types and extensions required. You must generate a new license file that includes both the existing and new entitlements.''

Option A is incorrect because a license file with only the new licenses would overwrite the previous file.

Option B is incorrect for the same reason---partial license files are not valid for merging with existing licenses.

Option D does not accommodate the new licenses.

ArcGIS Enterprise -- Managing Portal License Files and User Entitlements

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

The configuration store and server directories for ArcGIS Enterprise should be placed in a partition with ample disk space and stable read/write performance, as these directories store logs, cache, uploads, and critical site configuration information.

In this scenario:

The /home partition (20 GB) is insufficient for growth and operational overhead.

The /opt partition (75 GB) is moderately sized but still smaller than the /data partition.

The /data partition (150 GB) provides the most space, making it the best choice to ensure scalability and system reliability.

Best practice from ArcGIS Enterprise documentation recommends placing server directories and configuration stores on high-capacity partitions like /data when available.

Reference Source: ArcGIS Enterprise Installation Guide --- File system and storage planning on Linux

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