Thewebgisdrutility is the official tool used to both back up and restore ArcGIS Enterprise deployments.
When restoring a backup, this tool ensures all components-Portal for ArcGIS, ArcGIS Server (federated), ArcGIS Data Store, and associated configurations-are restored in the correct sequence and with integrity.
The utility reads from a configuration file that defines the backup location, type, and parameters.webgisdr orchestrates the entire restoration process automatically. Runningrestoredatastore(Option B) individually is not required and may only restore part of the deployment, such as the relational store.Restore(Option C) is not a valid utility for ArcGIS Enterprise.
Reference Source:ArcGIS Enterprise documentation - Web GIS Disaster Recovery tool (webgisdr)

To enableSAML-based SSO, the ArcGIS Enterpriseportal acts as the Service Provider (SP). To link it to an Identity Provider (IdP), you mustregister the portal's SP metadatawith 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."
* OptionAis for IWA (Kerberos), not SAML.
* OptionCrefers to LDAP but doesn't configure SAML or SSO.
* OptionDis not a valid standalone action for SAML integration.
Reference:ArcGIS Enterprise -Configuring SAML Identity Providers for Single Sign-On

ArcGIS GeoAnalytics Server is designed to perform distributed analysis on largevolumes of spatial and temporal data. To efficiently process large datasets, it is recommended that each machine in the GeoAnalytics Server site has at least 16 GB of RAM and 4 CPU cores. However, for optimal performance, especially when handling very large datasets, increasing the available RAM can significantly improve processing times.
In this scenario, the machine already has 16 GB of RAM and 4 cores. Adding more RAM would allow the GeoAnalytics Server to allocate more memory per job, enhancing its ability to process large datasets efficiently. Therefore, the recommended action is to add 16 GB of RAM to the GeoAnalytics Server machine.
Reference Source:ArcGIS Enterprise documentation on GeoAnalytics Server system requirements and performance optimization.

Custom cached basemaps are stored as tile cache files on disk and are not included in backups created by the webgisdr tool or the ArcGIS Data Store backup utility. Therefore, to ensure these basemaps can be restored in the event of a disaster, it's essential to manually back up the cache directories where these tiles are stored.
This involves copying the cache folders to a secure backup location and ensuring they are kept in sync with any updates made to the basemaps.
The webgisdr tool (Option A) is used for backing up and restoring the ArcGIS Enterprise configuration and content but does not include custom tile caches. The ArcGIS Data Store backup utility (Option C) is used for backing up hosted feature layers and other data managed by the ArcGIS Data Store, not custom cached basemaps.
Reference Source:ArcGIS Enterprise documentation on backup and restore best practices

Theconfiguration store and server directoriesfor ArcGIS Enterprise should be placed in a partition with ample disk spaceandstable read/write performance, as these directories store logs, cache, uploads, and critical site configuration information.
In this scenario:
* The /home partition (20 GB) is insufficient for growth and operational overhead.
* The /opt partition (75 GB) is moderately sized but still smaller than the /data partition.
* The /data partition (150 GB) provides the most space, making it the best choice to ensure scalability and system reliability.
Best practicefrom ArcGIS Enterprise documentation recommends placing server directories and configuration stores on high-capacity partitions like /data when available.
Reference Source:ArcGIS Enterprise Installation Guide - File system and storage planning on Linux