An organization configures an ArcGIS Enterprise portal to allow single sign-on using Integrated
Windows Authentication (IWA). Configuration includes:
All accounts in the Active Directory group gisusers are added to the portal
Existing users can sign in without entering credentials
However, new employees assigned to the same gisusers group cannot log in, create content, or join
groups.
What is causing this issue for the new employees?
B
A portal administrator is trying to enable web-tier authentication (IWA) for the ArcGIS Enterprise
portal using Active Directory and IIS.
Steps taken:
Configured portal with Microsoft version of ArcGIS Web Adaptor
Set identity store to Active Directory
Added AD users to the portal
Disabled anonymous access in Portal
Users are not prompted to sign in and are not automatically logged in.
What should the administrator do next?
A
Explanation:
When using IWA through the Web Adaptor (IIS), the IIS server itself must be configured to deny
anonymous access and allow Windows Authentication. Simply disabling anonymous access within
the Portal settings is not enough.
From Esri’s web-tier authentication guide:
“For IWA to function as expected, anonymous access must be disabled in IIS for the ArcGIS Web
Adaptor, and Windows Authentication must be enabled. If IIS still allows anonymous access, users
will bypass authentication prompts.”
Option B is irrelevant here—user types don’t affect login behavior.
Option C is a content sync feature, not related to authentication.
Option D (Enable Windows Authentication) is correct only if it hasn't already been done, but the
missing step is disabling anonymous access in IIS.
Reference:
ArcGIS Enterprise – Configuring Web-Tier Authentication with IIS
An ArcGIS Enterprise administrator wants to publish their feature classes as layers in bulk from a
registered geodatabase.
Which action should the administrator perform?
A
Explanation:
To publish feature classes as services in bulk from an enterprise geodatabase, it must first be
registered with the ArcGIS Server site. This registration tells ArcGIS Server where to access the data
directly for referenced service publishing. The proper way to do this is through ArcGIS Server
Manager.
From ArcGIS Enterprise documentation:
“To publish layers directly from a registered enterprise geodatabase without copying data, you must
register the geodatabase with your ArcGIS Server site using ArcGIS Server Manager.”
Option B is used for hosted services, not referenced publishing.
Option C is not the correct interface for registering data sources.
Option D involves hosting data, which is not applicable for referenced layers from a geodatabase.
Reference:
ArcGIS Server – Registering Data Stores for Publishing Referenced Services
=====================
A client has an internet-accessible ArcGIS Enterprise deployment with the Web Adaptors in the DMZ,
and the remaining components are on an internal network behind a firewall. A user on the internet
must access a web map in that environment.
Which ports must be open in the firewall between the DMZ and the internal network?
C
An organization experiences a temporary loss of service for its ArcGIS Enterprise deployment due to
expired licenses.
What should the administrator have done to prevent this issue?
A
In a multi-machine ArcGIS Server site, the following is observed:
Random services missing on one server but reappear later
Intermittent service failures
Warnings and severe errors like:
Failed to write heartbeat
Error synchronizing with config store
Failed to return all folder configurations
Failed to return all services configurations in folder
What should the administrator review?
B
Explanation:
These errors point to problems accessing the configuration store, which is commonly stored on a
shared file location across ArcGIS Server machines. Intermittent access, latency, or I/O issues with
the shared drive can cause synchronization failures and service visibility problems.
From Esri documentation:
“If ArcGIS Server cannot reliably access the configuration store, errors such as heartbeat failure, sync
issues, and missing service configurations may occur. Always ensure the shared file location is on a
reliable, supported file system with proper permissions and stability.”
Option A (VM resources) might impact general performance but not sync reliability.
Option C (patches) is important but doesn't fix shared drive instability.
Option D is not relevant in this context.
Reference:
ArcGIS Server – High Availability Configuration Store Troubleshooting
An organization wants to use the standard feature analysis tools available in ArcGIS Enterprise to
create hosted feature layers for planning and design.
Which data store is required for this work?
B
Explanation:
The standard feature analysis tools in ArcGIS Enterprise (e.g., buffer, overlay, aggregate points)
require hosted feature layers, which depend on the relational data store (a component of ArcGIS
Data Store). The relational data store is the default location for hosting feature layers.
From ArcGIS Enterprise documentation:
“To use the standard spatial analysis tools and create hosted feature layers, the ArcGIS Data Store
(relational) must be configured and set as the default hosting location.”
Option A (spatiotemporal big data store) is used for real-time and big data feeds, not standard
analysis.
Option C supports cached tiles, not feature layers.
Reference:
ArcGIS Enterprise – Configuring the Relational Data Store for Hosting Feature Layers
=====================
A GIS administrator has a group of users who share maintenance responsibilities for a critical
application. The administrator needs to allow all users to edit the application without transferring
ownership.
Which option should the administrator use?
A
Explanation:
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.
Reference:
ArcGIS Enterprise – Group Settings for Collaborative Management
=====================
A client wants to perform incremental webgisdr backups daily and full backups weekly. They store all
data in the relational ArcGIS Data Store, with no tile or map caches.
Which action is required to enable incremental backups?
B
Explanation:
To perform incremental backups using the webgisdr tool, point-in-time recovery must be enabled on
the relational data store. This creates transaction logs needed for differential backups and aligns with
best practices for enterprise-level backup strategies.
From Esri documentation:
“Incremental backups can only be used with a relational data store when point-in-time recovery is
enabled. This enables transaction log capture needed for delta backups.”
Option A is unrelated to backup functionality.
Option C is not required unless performance tuning is needed.
Reference:
ArcGIS Enterprise – Enabling Point-in-Time Recovery in ArcGIS Data Store for Incremental Backups
=====================
After upgrading, a GIS administrator tries to log in to Portal for ArcGIS using admin credentials. The
portal site doesn't display correctly and an error is shown. Login fails.
What should the administrator do?
C
Explanation:
After an upgrade, Portal for ArcGIS often changes web elements, scripts, and cached content. If the
browser is using old cached files, the portal page may not render correctly, and authentication may
fail. Clearing the browser cache ensures that new files are loaded.
From Esri documentation:
“After upgrading ArcGIS Enterprise, clear the browser’s cache to ensure that all updated components
and scripts are loaded properly.”
Option A is a diagnostic tool, not a fix.
Option B may be excessive if the issue is simply browser cache.
Option D is not a standard troubleshooting step.
Reference:
ArcGIS Enterprise – Post-Upgrade Troubleshooting and Web Adaptor Behavior