ArcGIS Enterprise doesn't currently offerautomated license expiration email alerts. However, administrators can useadministrative scriptsto query license status andgenerate reports that can be automated using task schedulers (e.g., Windows Task Scheduler).
From Esri guidance:
"Administrators can monitor license status using the ArcGIS REST API or scripting tools. Automating these checks allows timely action before licenses expire."
* OptionAis not a native capability of the portal.
* OptionCis not tied to licensing and is only useful as a passive alert.
* OptionDis not a valid license management option.
Reference:ArcGIS Enterprise -Managing License Expiry and Automating Admin Reports

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

Adistributed collaborationin ArcGIS Enterprise is designed to operatebetween two organizations only.
Therefore, to collaborate withtwo separate ArcGIS Online organizations, the administrator must create separate collaborationsbetween 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."
* OptionBis incorrect because adding external users from other orgs to a group doesn't extend collaboration capabilities.
* OptionCis not supported - collaborations are strictlybetween two parties.
Reference:ArcGIS Enterprise -Distributed Collaboration Limitations and Multi-Org Setup

These errors point toproblems accessing the configuration store, which is commonly stored on ashared file locationacross 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."
* OptionA(VM resources) might impact general performance butnot sync reliability.
* OptionC(patches) is important but doesn't fix shared drive instability.
* OptionDis not relevant in this context.
Reference:ArcGIS Server -High Availability Configuration Store Troubleshooting

After federating a GIS Server with the portal and registering a relational data store, the next step is to designate the GIS Server as thehosting serverin the ArcGIS Enterprise portal. This configuration enables the portal to support the publishing of hosted feature layers and hosted scene layers. The hosting server must have both a relational data store and a tile cache data store configured to support these functionalities.
Reference Source:ArcGIS Enterprise documentation on configuring a hosting server