ArcGIS Enterprise Architecture and Components
What this domain tests
Domain 1 asks you to reconstruct a base ArcGIS Enterprise deployment from memory and reason about what changes when you add servers, high availability, or a new capability.
The base deployment
Since 10.6, the base deployment must be installed on a single machine and consists of exactly four components: Portal for ArcGIS, ArcGIS Server configured as the portal's hosting server, ArcGIS Data Store, and ArcGIS Web Adaptor. Everything else is an addition:
- extra federated servers, including specialized roles such as image, GeoEvent, GeoAnalytics, notebook, knowledge, workflow manager and mission servers;
- a second portal machine plus a load balancer and highly available configuration store for portal high availability;
- ArcGIS Monitor, and ArcGIS License Manager only where concurrent-use licensing is used.
Federation and the Web Adaptor
Federation binds a server to a portal over HTTPS at a well-known URL, so each server must be reachable through a Web Adaptor or load balancer whose hostname matches the URL registered with the portal. After federation, ArcGIS Server administration is delegated to portal accounts; the primary site administrator survives only as a recovery account. Exactly one federated server is designated the hosting server, and only it writes to the ArcGIS Data Store.
Ports worth memorizing
7443 Portal for ArcGIS, 6443 ArcGIS Server (HTTPS), 6080 ArcGIS Server (HTTP), 2443 ArcGIS Data Store, and 80/443 for the Web Adaptor. End users should reach only the Web Adaptor or load balancer.
Worked example
Requirement: a portal at gis.example.com that publishes hosted feature layers and lets anonymous users read one web map. Reasoning: hosted feature layers need the hosting server plus the relational data store, so all four base components are required. The Web Adaptor answers on 443 for gis.example.com and proxies /portal and /server. Anonymous reading means the Web Adaptor must not enforce Windows authentication on portal URLs. Nothing in the requirement exceeds one machine, so no additional server is needed.
Traps
Treating ArcGIS Data Store as optional (hosted layers break without it); assuming a portal can have two hosting servers; federating a server that is not reachable at the registered URL; confusing a standalone ArcGIS Server with an Enterprise deployment.