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/