EAEP2201 Exam Dumps - Esri Technical Certification Questions and Answers

To enable SAML-based SSO, the ArcGIS Enterprise portal acts as the Service Provider (SP). To link it to an Identity Provider (IdP), you must register the portal’s SP metadata with the IdP and configure the portal to trust it.

From Esri's documentation:

“To complete SAML configuration, register the portal’s SAML service provider metadata with your organization’s identity provider, then configure the portal with the IdP metadata.”

Option A is for IWA (Kerberos), not SAML.

Option C refers to LDAP but doesn’t configure SAML or SSO.

Option D is not a valid standalone action for SAML integration.

For multi-machine deployments, a Group Managed Service Account (gMSA) is the best option. It supports running services across multiple servers without requiring manual password updates, making it ideal for high-availability and enterprise security compliance.

From Esri’s deployment guidance:

“Use a group managed service account (gMSA) when installing ArcGIS Enterprise on multiple machines. gMSAs allow centralized password management and seamless cross-machine authentication.”

Option A could lead to password expiration issues.

Option C lacks centralized management and complicates maintenance.

The Spatiotemporal big data store is designed for massive datasets and optimized for high-speed visualization, time-enabled querying, and big data analytics. It is ideal for storing millions of point features such as sensors or oil rig locations, especially when performance and scalability are critical.

From ArcGIS documentation:

“The spatiotemporal big data store is designed for writing and querying large volumes of spatial and temporal data. It’s optimized for visualizing high-density datasets in web maps.”

Option B (Relational) works for moderate data volumes but may not scale well.

Option C supports cached tiles, not dynamic feature access.

A shared update group allows group members to edit each other’s items without needing to transfer ownership. This is ideal for collaborative editing and shared responsibility for applications, maps, or dashboards.

From Esri documentation:

“Shared update groups allow multiple members to update items shared with the group, even if they do not own the items.”

Option B doesn’t exist as a group type in ArcGIS Enterprise.

Option C allows viewing, but not editing others' content.

Option D applies to distributed collaboration, not shared editing.

For map services that are infrequently updated and contain numerous detailed features with complex symbology, configuring the service to use cached tiles is the most effective way to improve drawing performance. Cached map services pre-render map images at various scales and store them, allowing for faster display to users. This approach is particularly beneficial when the data does not change frequently, as it reduces the server's processing load during user interactions.​

Eliminating scale-dependent rendering (Option B) may lead to performance degradation, as it could result in rendering all features at all scales, increasing the amount of data processed and displayed unnecessarily.​

Switching to dedicated instances (Option C) can improve performance in some scenarios, but it also increases resource usage on the server. Given that the service is infrequently updated and the primary concern is drawing performance, caching is the more efficient and scalable solution.​

Reference Source: ArcGIS Enterprise documentation on optimizing map services for performance.​

During the upgrade from ArcGIS Enterprise 10.6.1 to 10.9.1, user type licensing is enforced. If the new license file includes more than one compatible user type (e.g., Creator and GIS Professional), existing members without a specified user type may be assigned temporary user types like "Standard (Temporary)" or "Lite (Temporary)." These temporary assignments prevent users from logging in until valid user types are manually assigned.​

This issue is not related to internet access (Option B) or the need to restart services (Option C).​

Reference Source: ArcGIS Enterprise documentation on user type licensing during upgrades

A distributed collaboration in ArcGIS Enterprise is designed to operate between two organizations only. Therefore, to collaborate with two separate ArcGIS Online organizations, the administrator must create separate collaborations between the Enterprise org and each ArcGIS Online org.

From Esri documentation:

“Each collaboration is established between two organizations. To collaborate with multiple organizations, you must set up multiple one-to-one collaborations.”

Option B is incorrect because adding external users from other orgs to a group doesn’t extend collaboration capabilities.

Option C is not supported — collaborations are strictly between two parties.