Free EAEP2201 Practice Test Questions and Answers (2026) Practice Questions

When an organization purchases additional licenses for ArcGIS Pro to be managed through ArcGIS Enterprise, a new, updated license file must be obtained from My Esri. This file is cumulative; it contains all previously held entitlements (such as user types and other app licenses) in addition to the newly acquired 25 ArcGIS Pro licenses. The portal administrator then imports this single, consolidated file into Portal for ArcGIS to update the organization's entitlements. This process makes the new licenses available for assignment to users without disrupting existing license assignments.

A. New license file with just the 25 ArcGIS Pro licenses: Importing a license file with only the new licenses would overwrite all existing entitlements, potentially un-licensing all current users and apps.

B. An updated license file with only the 25 additional ArcGIS Pro licenses: This is functionally the same as option A. A license file must be comprehensive, containing all entitlements, not just the additional ones.

D. Any existing license file used previously: A previous license file does not contain the newly purchased 25 licenses, so it cannot be used to make them available for assignment.

1. Esri ArcGIS Enterprise Documentation (Portal for ArcGIS): "Obtain a portal license file." The documentation states

"If you add or change the user types or add-on app licenses in your organization

you must obtain a new portal license file and reapply it to the portal." This confirms that a new

updated file is required for any additions.

Source: ArcGIS Enterprise 11.0 Documentation

Portal for ArcGIS

Installation and deployment

"Obtain a portal license file".

2. Esri ArcGIS Enterprise Documentation (Portal for ArcGIS): "Manage licenses." This section details the process of importing the license file. It explains

"To update user types or add-on licenses

or to add more of either

you must obtain a new portal license file from My Esri and import it to the portal." This reinforces that a new

comprehensive file is the correct mechanism for adding licenses.

Source: ArcGIS Enterprise 11.0 Documentation

Portal for ArcGIS

Administer

"Manage licenses"

section "Import licenses".

Standard feature analysis tools in the ArcGIS Enterprise portal generate new hosted feature layers as their output. The ArcGIS relational data store is the required component for storing and managing the data for these hosted feature layers. It is the primary data repository for an organization's hosted vector data, enabling spatial analysis, editing, and sharing capabilities through the portal. The relational data store is a mandatory component of a base ArcGIS Enterprise deployment configured as a hosting server.

A. Spatiotemporal big data store: This is an optional data store used specifically for real-time data archiving and for running GeoAnalytics Tools, not the standard feature analysis tools.

C. Tile cache data store: This data store is used to store caches for hosted 3D scene layers, which improves drawing performance, but it does not store feature data.

D. File-based geodatabase: While a file geodatabase can be a data source for publishing layers, it is not the managed data store used by ArcGIS Enterprise to store the output of analysis tools run within the portal.

1. Esri ArcGIS Enterprise Documentation. "What is ArcGIS Data Store?". ArcGIS Enterprise 11.0 Documentation. Accessed October 2023.

Section: Relational data store: "A relational data store stores data for the hosted feature layers that are created when you... run analysis tools in Map Viewer or ArcGIS Pro... It is the data storage component for a hosting server." This directly confirms that the relational data store is required for the output of standard analysis tools.

2. Esri ArcGIS Enterprise Documentation. "Data and publishing in ArcGIS Enterprise". ArcGIS Enterprise 11.0 Documentation. Accessed October 2023.

Section: Copy data: "When you publish a hosted feature layer... the data is always copied to the relational data store that is registered with the hosting server." This clarifies that hosted layers

the output of the described workflow

reside in the relational data store.

3. Esri ArcGIS Enterprise Documentation. "An overview of the ArcGIS Data Store configuration process". ArcGIS Enterprise 11.0 Documentation. Accessed October 2023.

Section: Overview: "At a minimum

you must create a relational data store. You can optionally configure a tile cache data store

spatiotemporal big data store

graph store

or object store." This establishes the relational data store as the fundamental and required type for core hosting functionality.

The ArcGIS Enterprise configuration store and associated directories (such as content, cache, and jobs) store dynamic data that grows over time. It is a best practice to place these directories on a dedicated, large partition separate from the operating system and the software installation files. In the given scenario, the /data partition has the most available space (150 GB) and, by convention, is intended for application data. Placing the directories here ensures sufficient space for growth and separates volatile data from static software binaries, which are typically installed in /opt.

A. /home: The /home partition (20 GB) is too small for the potential growth of ArcGIS Enterprise data and is conventionally reserved for user-specific configuration files and personal data.

C. /opt: The /opt partition is the standard location for installing optional, third-party software packages (the ArcGIS Enterprise binaries). Co-locating growing data with static application files is not a recommended practice.

1. Esri Documentation

ArcGIS Enterprise 11.2

ArcGIS Server System Requirements: "The directories used by ArcGIS Server to store caches and other data can also be large. For example

if you create caches for your services

the disk space required can easily be tens or hundreds of gigabytes... For this reason

it's important that you have a separate disk or partition for the server directories."

Source: Esri. (2024). ArcGIS Server system requirements. ArcGIS Enterprise Documentation. Retrieved from https://enterprise.arcgis.com/en/server/latest/install/windows/arcgis-server-system-requirements.htm (The principle applies equally to Linux).

2. Esri Documentation

ArcGIS Enterprise 11.2

About Server Directories: "The server directories store content

configuration

and logging information used by your GIS server... You should ensure that the account that will be used to run ArcGIS Server has write access to the server directories and that there is sufficient disk space to store the directories."

Source: Esri. (2024). About server directories. ArcGIS Enterprise Documentation. Retrieved from https://enterprise.arcgis.com/en/server/latest/administer/windows/about-server-directories.htm.

3. Esri Documentation

ArcGIS Enterprise 11.2

Portal for ArcGIS System Requirements: "The portal's content directory stores content saved and uploaded by users... The content directory can grow very large depending on the number and size of the files saved by users. It is highly recommended that you place the directory on a separate

highly available disk."

Source: Esri. (2024). Portal for ArcGIS system requirements. ArcGIS Enterprise Documentation. Retrieved from https://enterprise.arcgis.com/en/portal/latest/install/windows/portal-for-arcgis-system-requirements.htm.

The most appropriate action is to create a service definition file (.sd). This is the standard Esri workflow for disconnected or offline publishing. A service definition file allows the analyst to configure all service properties, define capabilities like editing, and package the data (if not referencing an enterprise geodatabase) without a direct connection to ArcGIS Server. The resulting .sd file is a portable package that can be transferred to a portal administrator who has the necessary connection and privileges to upload and publish the service to the specified ArcGIS Server. This method directly addresses the core constraint of the analyst not having a server connection.

B. Change the privileges on their user role to allow publishing

This is incorrect because the fundamental issue is the lack of a network connection to the server, not user privileges. Enhanced privileges cannot overcome a physical or network-level disconnection.

C. Upload the layer to the portal as a layer package file and add it to a web map

This workflow creates a hosted feature layer on the portal's designated hosting server. It is not a general solution for publishing to any specified ArcGIS Server and does not support referenced services. Option A is more versatile and directly fits the classic disconnected publishing pattern.

1. Esri ArcGIS Pro Documentation

"Introduction to saving a service definition": "A service definition allows you to preconfigure the properties of a service and share it with others to publish at a later time. This is useful in a number of workflows

such as when you are disconnected from the server or when you want to keep a record of the service configuration." This source directly validates the use of a service definition file for disconnected workflows.

2. Esri ArcGIS Pro Documentation

"Publish a service definition": This document outlines the process

stating

"You can create a service definition in a disconnected state from the server and share it with an administrator who can publish it later." This confirms the workflow described in option A.

3. Esri ArcGIS Enterprise Documentation

"User roles and privileges": The documentation on portal roles (e.g.

Publisher

Administrator) shows that privileges are for performing actions within the system. They do not grant network connectivity where none exists

making option B incorrect.

4. Esri ArcGIS Enterprise Documentation

"Publish hosted feature layers": This document details how various items

including layer packages (.lpkx)

can be used to publish services. It clarifies that this process creates hosted layers

which are published to the portal's configured hosting server

confirming the limitation of the workflow in option C.

Registering the database as a data store item in the ArcGIS Enterprise portal is the correct method to meet the specified requirements. This approach leverages the portal's integrated security and sharing model. The administrator can create the data store item and share it exclusively with a specific group of portal members who are designated to publish services from that database. This directly fulfills the requirement to "limit the users who can publish services" from that source. Other users with publishing privileges in the portal will not be able to see or use this specific data store for their publishing workflows.

A. As an ArcGIS-managed data store in Server Manager: Registering a database directly in ArcGIS Server Manager makes it available to any user with privileges to publish to that server. This method does not provide a mechanism to restrict which publishers can use that specific data store.

C. As a relational data store in ArcGIS Data Store: ArcGIS Data Store is a component used to create and manage data storage for layers hosted on the portal (e.g., hosted feature layers). It is not used for registering existing, user-managed databases.

---

1. Esri

ArcGIS Enterprise Documentation. "Data stores in ArcGIS Enterprise." Portal for ArcGIS. Accessed October 2023.

Section: "Add a data store item in the portal"

Content: "When you add a data store item

you can share it with groups of portal members who have privileges to create content and publish. This allows those members to browse the data store and publish layers from it. For example

you can create a group of publishers in your organization who work with the contents of a specific database. You create a data store item for the database and share it with the group. Only members of that group will see the data store item and can publish from it." This directly supports using data store items to limit publishers.

2. Esri

ArcGIS Pro Documentation. "Data sources for ArcGIS Enterprise." ArcGIS Pro. Accessed October 2023.

Section: "Register your data"

Content: "When you add a data store item to the portal

you can share the data store item with members of a group who have privileges to publish. This allows you to make specific data sources available to specific groups of publishers." This confirms that sharing a data store item is the intended workflow for controlling publisher access to specific data sources.

3. Esri

ArcGIS Enterprise Documentation. "What is ArcGIS Data Store?" ArcGIS Data Store. Accessed October 2023.

Section: "Introduction to ArcGIS Data Store"

Content: "ArcGIS Data Store provides you with a convenient setup and configuration experience that creates and maintains the following types of data stores... You should not access the databases that ArcGIS Data Store creates and manages for the hosting server directly..." This reference clarifies that ArcGIS Data Store is for ArcGIS-managed data

not for registering user-managed databases

making option C incorrect.

Portal for ArcGIS provides built-in administrative tools to generate usage reports. These reports can be created for members, groups, and content items, providing detailed statistics on activity within the organization. The administrator can create reports that show who is creating, viewing, and editing specific types of content. These reports can be downloaded in a tabular format (.csv file), which directly fulfills the requirement to pull tabular statistics on user and group content production and consumption. This is the most direct and standard method for this task within ArcGIS Enterprise.

B: ArcGIS Server statistics focus on the performance and usage of individual web services (e.g., request counts, draw times), not on the broader portal-level content items, users, or groups.

C: ArcGIS Monitor is a separate, comprehensive monitoring product for system health and performance. While it can capture usage data, using the built-in Portal reports is the more direct and standard action for this specific administrative task.

1. Esri ArcGIS Enterprise Documentation

"View usage reports": This document details the process for administrators to generate reports on members

items

and groups within Portal for ArcGIS. It explicitly states

"You can create and view reports about members

items

and groups... The reports are provided in comma-separated values (.csv) format." This directly supports option A.

Source: Esri. (2022). ArcGIS Enterprise 11.0 Documentation

Portal for ArcGIS

Administer

View usage reports. Retrieved from https://enterprise.arcgis.com/en/portal/latest/administer/windows/view-usage-reports.htm

2. Esri ArcGIS Enterprise Documentation

"About server statistics": This source explains that ArcGIS Server statistics are used to "find the response times for your services

see how many times they are being used

and get a list of the most failed requests." This confirms that Server statistics are service-focused

making option B incorrect for analyzing user and group content types.

Source: Esri. (2022). ArcGIS Enterprise 11.0 Documentation

ArcGIS Server

Administer

About server statistics. Retrieved from https://enterprise.arcgis.com/en/server/latest/administer/windows/about-server-statistics.htm

3. Esri ArcGIS Enterprise Documentation

"What is ArcGIS Monitor?": This document describes ArcGIS Monitor as a tool to "collect data and provide information on the status

health

and usage of your enterprise GIS." While it can collect usage data

its primary purpose is comprehensive system health monitoring

making it a less direct tool for the specific reporting task described compared to the built-in Portal functionality.

Source: Esri. (2022). ArcGIS Monitor 2023.1 Documentation

Get started

What is ArcGIS Monitor?. Retrieved from https://enterprise.arcgis.com/en/monitor/latest/get-started/what-is-arcgis-monitor.htm

The most effective action is to configure the map service to use cached tiles. The service's characteristics—numerous detailed features, complex symbology, and infrequent updates—make it an ideal candidate for caching. Caching pre-renders the map at various scales and stores the images (tiles) on the server. When a user requests the map, the server returns these pre-rendered tiles instead of drawing the complex data on the fly. This dramatically improves drawing performance for data that is largely static, directly addressing the reported slowness.

B. Eliminate scale-dependent rendering: This would worsen performance. Scale-dependent rendering is an optimization technique that simplifies the map by showing fewer details at smaller scales, thus reducing the server's rendering load.

C. Use dedicated instances instead of shared instances: While dedicated instances can improve performance by allocating specific server resources, it does not solve the core issue of slow on-the-fly rendering. Caching eliminates the need for most on-the-fly rendering, making it a more direct and impactful solution for this specific problem.

1. Esri

ArcGIS Enterprise Documentation. (2024). Map Caching.

Section: "What is map caching?"

Content: "A map cache is a set of map tiles... The server can distribute these images whenever they are requested. It's much faster for the server to return a cached image than to draw the map each time... The most important reason to cache your map is to improve its performance." This directly supports using caching for performance.

2. Esri

ArcGIS Enterprise Documentation. (2024). Tune and configure services.

Section: "Anticipating and accommodating users"

Content: "The most effective strategy you can take to improve the performance of map services is to cache them. When you cache a map service

the server draws the map at a set of predefined scale levels and saves the images." This identifies caching as the primary performance strategy.

3. Esri

ArcGIS Pro Documentation. (2024). Author a map for publishing.

Section: "Performance tips"

Content: "Use scale ranges to limit the display of layers to only the scales at which they are needed... This prevents layers with a lot of detail from being drawn at small scales

which would slow down drawing performance." This confirms that eliminating scale-dependent rendering (Option B) is counterproductive.

4. Esri

ArcGIS Enterprise Documentation. (2024). Configure service instance settings.

Section: "Shared and dedicated instances"

Content: This section explains that dedicated instances are useful for heavily used services or those with long-running jobs. However

for slow drawing performance due to complex cartography on static data

caching is the recommended and more fundamental solution before adjusting instance models.

The key evidence is that at the median request load (p50), the service is already using all 8 of its maximum configured instances. This indicates that for at least half the time, the service is operating at full capacity. When all instances are busy, incoming requests are placed in a queue, leading to significant delays. This queuing effect is the direct cause of the p75 request time being 10 times longer than the p25 time. The server's low CPU (53%) and memory (44%) utilization confirms that the hardware is not the bottleneck; rather, the service's instance setting is too low to meet user demand.

A. There is no data provided, such as network latency or I/O wait times, to suggest network saturation. Low system usage on the database server also makes this an unlikely primary bottleneck.

C. The client operating system (Android) and server operating system (Linux) are not inherently a cause of performance issues and are irrelevant given the specific metrics provided.

---

1. Esri ArcGIS Enterprise Documentation. (2022). "Tune service instance settings." ArcGIS Server Administration.

Section: Configure service instance settings.

Content: The documentation states

"If you anticipate high traffic

you may want to increase the maximum number of instances. If all instances are busy processing requests

new requests are queued until an instance becomes available. If the request waits in the queue longer than the maximum wait time

it will time out." This directly explains the behavior observed in the question

where maxing out instances leads to long wait times (high p75).

2. Esri ArcGIS Monitor Documentation. (2022). "Key metrics." ArcGIS Monitor Help.

Section: Analysis > Charts and data.

Content: The documentation explains that percentiles (p25

p50

p75) are used to understand the distribution of response times. A large gap between percentiles

as seen in the question (p75 is 10x p25)

is a strong indicator of a bottleneck causing requests to queue. Correlating this with the "Instances In Use" metric hitting its maximum configured value confirms an instance-related bottleneck.

3. Esri. (2019). "ArcGIS Enterprise: Performance and Scalability Best Practices." Esri User Conference Technical Workshop.

Content: These workshops consistently identify insufficient service instances as a common performance bottleneck. They illustrate that when the number of running instances hits the maxInstances setting

response times increase dramatically while server CPU and memory may remain low. The solution presented is to increase the maxInstances value

provided the server has adequate hardware resources

which is the case in the scenario.

The client's requirements necessitate two distinct capabilities: serving feature services and serving image services. While a standard GIS Server can serve feature services, publishing dedicated "image services" with capabilities for managing and serving cached raster data requires the ArcGIS Image Server license role. The Image Server license role includes all the capabilities of the GIS Server Advanced role, thereby fulfilling both requirements. It enables the publishing of image services from raster datasets and also supports publishing feature services from an enterprise geodatabase like PostgreSQL.

A. GIS Server: This role can serve feature services but lacks the specific capability to publish "image services." It can only publish map services containing raster layers, which is a different service type.

C. Mission Server: This is a specialized role for real-time situational awareness and collaborative mapping during missions; it is not designed for hosting general image or feature services.

D. GeoAnalytics Server: This role is for distributed processing and analysis of large-scale vector and tabular data, not for serving the specified service types.

1. Esri ArcGIS Enterprise Documentation. "ArcGIS Server licensing roles." ArcGIS Enterprise 11.2 Documentation. Accessed May 2024.

Reference Detail: In the section describing the ArcGIS Image Server role

the documentation states

"The ArcGIS Image Server license role allows you to publish image services from mosaic datasets

raster datasets

and raster products... An ArcGIS Image Server license also includes the capabilities of the ArcGIS GIS Server Advanced license." This directly confirms that the Image Server role fulfills both requirements in the question.

2. Esri ArcGIS Enterprise Documentation. "What is an image service?" ArcGIS Enterprise 11.2 Documentation. Accessed May 2024.

Reference Detail: This page clarifies that an image service is the primary mechanism for serving raster and imagery data and that "To publish an image service

you must have the ArcGIS Image Server role licensed for your ArcGIS Server site." This confirms the necessity of the Image Server role for the first requirement.

The standard and correct procedure for applying a new extension license, such as ArcGIS Data Interoperability, to an existing ArcGIS Server site is to use the Software Authorization Wizard. This utility is specifically designed to process the license file (.prvc) provided by Esri. After the wizard successfully applies the new license, the ArcGIS Server service must be restarted for the extension to be recognized and enabled. This process ensures the license is correctly registered with the software without risking corruption of the deployment.

A. Manually add the license to the JSON license file, and then reload it:

Manually editing ArcGIS Enterprise configuration or license files is not a supported method. This approach is error-prone and can lead to system instability or complete license invalidation.

C. Use the ArcGIS Server installation program to apply the license:

The installation program is used for the initial setup of the software. It is not the appropriate tool for managing licenses on an already installed and operational ArcGIS Server site.

---

1. Esri ArcGIS Enterprise Documentation

"Authorize ArcGIS Server": This document explicitly states the procedure for licensing. It says

"To apply an authorization file you received from Esri Customer Service

use the Software Authorization Wizard... You can also use this wizard to authorize additional extension licenses." It also notes the requirement to restart the service.

Source: Esri. (2022). ArcGIS Enterprise 11.0 Documentation

Installation and Deployment

Authorize ArcGIS Server. Retrieved from https://enterprise.arcgis.com/en/server/latest/install/windows/authorizing-arcgis-server.htm (Section: "Authorizing with a provision file").

2. Esri ArcGIS Enterprise Documentation

"About the Data Interoperability extension": The documentation for the extension itself confirms it is licensed as a standard ArcGIS Server role. The licensing process follows the general server authorization steps.

Source: Esri. (2022). ArcGIS Enterprise 11.0 Documentation

Extensions

Data Interoperability

About the Data Interoperability extension. Retrieved from https://enterprise.arcgis.com/en/server/latest/get-started/windows/about-the-data-interoperability-extension.htm (Section: "Licensing").

The architecture described places the ArcGIS Web Adaptors in a DMZ, acting as reverse proxies for the ArcGIS Enterprise components located on the internal network. For this configuration to function, the Web Adaptors must be able to forward incoming requests to the backend components. The ArcGIS Web Adaptor for Portal for ArcGIS communicates with the Portal component on its default HTTPS port, 7443. Similarly, the Web Adaptor for ArcGIS Server communicates with the ArcGIS Server component on its default HTTPS port, 6443. Therefore, the firewall between the DMZ and the internal network must permit traffic on these two ports.

B. 443 and 6443: Port 443 is for external traffic to the Web Adaptor, not for communication from the Web Adaptor to the internal network components.

C. 80 and 443: These are standard web ports for external access to the Web Adaptors, not for the required internal communication between the Web Adaptor and backend components.

D. 2443 and 6443: Port 2443 is not used by the core Portal for ArcGIS or ArcGIS Server components for this type of communication in a base deployment.

1. Esri ArcGIS Enterprise Documentation. "Ports used by ArcGIS Server." This document explicitly states that port 6443 is used for HTTPS communication and that "The ArcGIS Web Adaptor communicates with ArcGIS Server through this port."

Source: ArcGIS Enterprise 11.2 Documentation

ArcGIS Server > Reference > Ports used by ArcGIS Server.

2. Esri ArcGIS Enterprise Documentation. "Ports used by Portal for ArcGIS." This document specifies that port 7443 is used for HTTPS communication and notes

"The ArcGIS Web Adaptor communicates with Portal for ArcGIS through this port."

Source: ArcGIS Enterprise 11.2 Documentation

Portal for ArcGIS > Reference > Ports used by Portal for ArcGIS.

3. Esri ArcGIS Enterprise Documentation. "Using a reverse proxy server with ArcGIS Enterprise." This guide illustrates architectures where a reverse proxy (like the Web Adaptor in a DMZ) forwards requests to backend servers. The diagrams and text confirm that traffic is forwarded from the proxy to ArcGIS Server on port 6443 and to Portal for ArcGIS on port 7443.

Source: ArcGIS Enterprise 11.2 Documentation

Portal for ArcGIS > Administer > Security > Using a reverse proxy server with ArcGIS Enterprise.

When a 3D scene is published from ArcGIS Pro to ArcGIS Enterprise as a hosted scene layer, the data is stored in the tile cache data store. This data store is specifically configured to manage the caches for hosted scene layers and tile layers. Scene layers are pre-generated caches (in the I3S/SLPK format) optimized for fast visualization of large 3D datasets over the web. The tile cache data store provides a highly scalable, file-based storage solution required for these caches.

B. Relational: The relational data store is used for storing the data of hosted feature layers, not the caches for scene layers.

C. Raster: Raster is a data format, not a type of ArcGIS Data Store. While raster data can be published as a tile layer, its cache is stored in the tile cache data store.

1. Esri ArcGIS Enterprise Documentation. "An overview of ArcGIS Data Store." ArcGIS Enterprise 11.2 Documentation. This document explicitly states: "Tile cache data store—Stores caches for hosted scene layers."

2. Esri ArcGIS Enterprise Documentation. "Data stores used with ArcGIS Server." ArcGIS Enterprise 11.2 Documentation. This resource details the different data store types and their specific functions

clarifying that the tile cache data store is for scene layer caches.

3. Esri ArcGIS Enterprise Documentation. "Publish hosted scene layers." Portal for ArcGIS 11.2 Documentation. This guide explains the publishing workflow and notes: "The cache for the scene layer is stored in the tile cache data store that is registered with the portal's hosting server."

The standard feature analysis tools available in the Portal for ArcGIS website (e.g., in Map Viewer) create new hosted feature layers as their output. This functionality requires a federated ArcGIS GIS Server to be designated as the organization's hosting server. The hosting server provides the necessary data storage and processing environment for these outputs. Even if the SpatialAnalysisTools geoprocessing service is running on a federated server, if no server is configured as the hosting server, the analysis tools will be unavailable to all users in the portal, as there is no designated location to store the results.

A. The Creator user type is a prerequisite for using analysis tools, not the cause of the problem. A user must be a Creator (or GIS Professional) with appropriate role privileges to perform analysis.

C. The question explicitly states the service is "verified to be running." While a restart can resolve transient issues, it is a troubleshooting step, not the root configuration cause for the tools being unavailable.

D. SpatialAnalysisTools is a geoprocessing service, not a data layer. It is published as a service to a federated server and cannot be published as a hosted layer.

1. Esri ArcGIS Enterprise Documentation. "Configure a hosting server." ArcGIS Enterprise 11.1 Documentation. This document states

"A hosting server is required to... Perform feature analysis in Map Viewer and the portal website... The analysis tools create hosted feature layers as their output. Therefore

a hosting server is required to store the analysis results."

2. Esri ArcGIS Enterprise Documentation. "Organization roles." ArcGIS Enterprise 11.1 Documentation. Under the "Privileges" section

the table shows that the "Spatial analysis" privilege (required for using analysis tools) is available to roles like Publisher

which are assigned to Creator user types. This confirms that the user type is an enabler

not a blocker.

3. Esri ArcGIS Enterprise Documentation. "What is a hosting server?" ArcGIS Enterprise 11.1 Documentation. This page clarifies

"The hosting server hosts these layers and the data they contain

and it also keeps track of who has access to the layers." This reinforces the central role of the hosting server in managing content created through portal functions like analysis.

The Creator user type is specifically designed for members who need to create, edit, and share content, which includes publishing web layers. The default role associated with the Creator user type is the Publisher role. The Publisher role grants the specific privileges required to publish hosted web layers and other service types. This combination directly provides the necessary capabilities and privileges for a member to perform both publishing and editing workflows as required by the scenario.

A. The Data Editor role only grants privileges to edit features in existing layers; it does not include the privilege to publish new content.

B. The Editor user type is designed for editing existing data and does not include the fundamental capability to create new content or publish web layers.

1. Esri. (2024). User types

roles

and privileges for ArcGIS Enterprise. ArcGIS Enterprise Documentation.

Section: User types > Creator: "In addition to the capabilities of the Viewer and Editor

Creators can... Publish hosted web layers... Publish ArcGIS Server services from ArcGIS Pro or ArcMap... Create and share content..." This confirms the Creator user type has the required capabilities.

Section: User types > Editor: "The Editor user type is for users who need to view and edit data in existing maps and apps... They cannot analyze data

or create or share items." This confirms the Editor user type lacks publishing capabilities.

Section: Default roles > Publisher: "Members who are assigned the Publisher role have the same privileges as a User

plus the ability to publish hosted web layers..." This confirms the Publisher role grants the necessary privileges.

Section: Custom roles > General privileges > Content: The privilege "Publish hosted feature layers" is listed as a key publishing privilege

which is included in the Publisher role but not the Data Editor role.

The GIS Professional user type is the only option that fulfills all the stated requirements. This user type is specifically designed for individuals who use the complete ArcGIS system. It bundles the capabilities of the Creator user type—which includes creating and managing portal content items like ArcGIS StoryMaps—with a license for the ArcGIS Pro desktop application. Therefore, assigning the GIS Professional user type ensures users have access to ArcGIS Pro, can create StoryMaps, and can view, edit, and create other portal content.

A. Creator: This user type allows for content creation (e.g., ArcGIS StoryMaps) but does not include a license for ArcGIS Pro by default.

B. Editor: This user type is limited to editing existing data within shared maps and apps; it cannot be used to create new content or to license ArcGIS Pro.

1. Esri. (2024). ArcGIS Enterprise Documentation: User types

roles

and privileges. ArcGIS Enterprise 11.2 & later. In the "User types" section

the description for GIS Professional states: "The GIS Professional user type is designed for those who need to create

manage

and share content in a variety of ArcGIS apps

including ArcGIS Pro." The capabilities table on this page explicitly shows that the GIS Professional user type includes an ArcGIS Pro license

while the Creator and Editor types do not. Retrieved from https://enterprise.arcgis.com/en/portal/latest/administer/windows/user-types-roles-privileges.htm

2. Esri. (2023). ArcGIS Blog: Understanding User Types. This article clarifies the purpose of each user type. It states

"The GIS Professional User Type is for the true GIS professional... This User Type includes ArcGIS Pro... as well as all the capabilities of the Creator User Type." Retrieved from https://www.esri.com/arcgis-blog/products/arcgis-online/mapping/understanding-user-types/