ArcGIS GeoAnalytics Server is designed to perform distributed analysis on large volumes of spatial and temporal data. It is particularly suited for workflows that involve analyzing patterns over time and space, such as identifying interstates with the most incidents over decades and correlating vehicle behavior (like speeding and braking) with accident locations.
GeoAnalytics Server provides tools for aggregating data, detecting incidents, and reconstructing tracks, which are essential for understanding complex transportation datasets. Its distributed computing framework allows for efficient processing of big data, making it the appropriate choice for the described workflow.
GeoEvent Server (Option B) is primarily used for real-time data processing and event detection, which is not the focus of this analysis. Notebook Server (Option C) supports interactive data science and analysis workflows using Jupyter notebooks but does not provide the same level of performance and scalability for big data analysis as GeoAnalytics Server.
Reference Source:ArcGIS Enterprise documentation on GeoAnalytics Server capabilities and use cases.

ForIWA authentication, Active Directory users arenot automatically addedto the ArcGIS Enterprise portal.
They must either be:
* Manually added as members, or
* Automatically created at first loginif auto-creation is enabled.
Since the new users are assigned to the gisusers group but cannot sign in or create content, it's clear that their accounts have not yet been added to the portal.
From ArcGIS Enterprise documentation:
"Integrated Windows Authentication (IWA) allows users to sign in with their Windows credentials. However, users must still be members of the portal. You can manually add users or enable automatic account creation during login."
* OptionBis invalid since default user type settings do not prevent login.
* OptionCis incorrect because synchronization is not time-based-it's account-creation dependent.
Reference:ArcGIS Enterprise -Managing Portal Members and Identity Store Integration

Theprimary site administrator accountin ArcGIS Server is abuilt-in accountthat bypasses external identity store configurations. To ensureonly users from a configured identity store(e.g., Active Directory) can administer the site, the primary site admin account must bedisabledafter alternative administrative access has been confirmed.
From ArcGIS Server documentation:
"After you configure your ArcGIS Server to use users and roles from an identity store (LDAP or Active Directory), you can disable the primary site administrator account to prevent bypassing the identity store."
* OptionBrelates to token security, not access control.
* OptionCis about running the service securely, not defining user permissions.
Reference:ArcGIS Enterprise -Managing Access Using Identity Stores and Disabling the Primary Site Administrator Account

To performincremental backupsusing thewebgisdr tool,point-in-time recoverymust 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."
* OptionAis unrelated to backup functionality.
* OptionCis not required unless performance tuning is needed.
Reference:ArcGIS Enterprise -Enabling Point-in-Time Recovery in ArcGIS Data Store for Incremental Backups

For ArcGIS Enterprise deployments on Microsoft Azure that were initially installed manually, the recommended approach for upgrading is to manually upgrade each component. This involves downloading the latest installers for each component (Portal for ArcGIS, ArcGIS Server, ArcGIS Data Store, etc.) and following the standard upgrade procedures for each. This method ensures that each component is properly updated and configured according to the organization's specific setup.
Using ArcGIS Enterprise Builder (Option B) is intended for new installations and is not suitable for upgrading existing deployments. ArcGIS Enterprise Cloud Builder for Microsoft Azure (Option C) is designed for deployments that were originally created using Cloud Builder; it cannot be used to upgrade deployments that were installed manually.
Reference Source:ArcGIS Enterprise documentation on upgrading manually installed deployments