Esri EAEP2201 Exam With Confidence Using Practice Dumps

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.

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​

Map image layers (map services) do not automatically detect schema changes, especially in registered enterprise geodatabases. Even with schema locking disabled, services cache the original schema at the time of publishing. To reflect the new field, you must overwrite the existing service.

From ArcGIS Server documentation:

“If the schema of a dataset is changed after a service is published (such as adding a field), the change is not automatically reflected in the service. You must overwrite the service or republish the map to reflect schema updates.”

Option B is not applicable; field visibility in the portal reflects what's in the published service definition.

Option C is related to editing access, not field visibility.

Option D is not a valid administrative action in this context.