Free and Premium Esri EGMP2201 Dumps Questions Answers

To create database connection files that point to a specific edit version for users, theGeodatabase Connection Propertiesoption should be used.

1. What are Geodatabase Connection Properties?

This option allows you to set specific connection details, such as the target version (edit version) within a traditionally versioned geodatabase.

It ensures that each user connects directly to their designated version, isolating edits and preventing conflicts in multi-user environments.

2. Why Use Geodatabase Connection Properties?

Provides control over which version of the geodatabase the user accesses.

Ensures security and consistency by directing users to their designated edit versions rather than the default version.

Allows administrators to pre-configure connection files for distribution to users.

3. Why Not Other Options?

Connection Properties:

Refers to general connection details like username, password, and server but does not allow specifying a particular version.

Database Properties:

Refers to database-level settings but does not configure specific user-level connection details, such as the target version.

Steps to Use Geodatabase Connection Properties:

InArcGIS Pro, go to theCatalog Pane.

Create a new database connection by selectingAdd Database.

In the connection properties dialog, specify:

The user’s credentials.

Thespecific versionthe user will edit under the Geodatabase Connection Properties section.

Save the connection file and distribute it to the user.

References from Esri Documentation and Learning Resources:

Database Connections in ArcGIS Pro

Versioned Database Connections

Conclusion:

UsingGeodatabase Connection Propertiesensures that each database connection file is pre-configured to point to the appropriate edit version for the user, enhancing security and workflow efficiency.

To restrict access to specific fields in a feature class, the GIS data administrator should use adatabase view.

1. What is a Database View?

Adatabase viewis a virtual table created by a SQL query. It displays data from one or more tables or feature classes, but only the specified fields and rows are accessible.

Views allow the administrator to control the fields and records visible to users without altering the underlying data.

2. Why Use a Database View?

Provides fine-grained control over data access by limiting which fields (or rows) are visible to specific users.

Helps enforce data security policies in multi-user environments.

Can be shared as a read-only layer or with restricted update permissions, depending on the use case.

3. Why Not Other Options?

Layer File:

A layer file (*.lyr) only defines how data is symbolized and displayed. It does not restrict field access at the database level. Unauthorized users can still access hidden fields through direct database connections.

Query Layer:

A query layer allows for custom SQL queries when displaying data in ArcGIS but is not a security measure. Users can modify or bypass the query to access all fields.

Steps to Create a Database View:

Use SQL to define the view, specifying only the required fields:

CREATE VIEW restricted_view AS

SELECT field1, field2

FROM feature_class

WHERE ;

Grant permissions to the view for authorized users while restricting access to the base table.

Publish the view in ArcGIS as a read-only layer if needed.

References from Esri Documentation and Learning Resources:

Creating and Using Database Views

Data Security in Enterprise Geodatabases

Conclusion:

Adatabase viewis the most effective method to restrict access to specific fields in a feature class, ensuring data security while providing flexibility in data sharing.

Scenario Overview:

An editor updates500,000 recordsin achild versionof the Default version using a field calculation.

Another editor updates the Default version, and thechild version is reconciledwith Default.

What Happens During Reconciliation?

In traditional versioning, edits to feature classes are stored in theAddsandDeletes tables.

During reconciliation:

Changes in the child version that differ from the Default version areduplicatedin the Adds and Deletes tables to track the differences.

This allows conflicts to be detected and resolved while preserving all edits.(ArcGIS Documentation: Traditional Versioning Workflow)

Alternative Options:

Option B: They will be migrated to the Base table

Migration to the base table occurs only when changes are posted and the geodatabase is compressed.

Option C: They will be removed from the States repository table

The States repository table tracks state transitions and is unaffected during reconciliation.

Thus, during reconciliation, the500,000 records are duplicated in the Adds and Deletes tablesto manage and detect conflicts.

Scenario Overview:

The GIS administrator needs to create asynchronized copyof a branch versioned dataset.

Both copies must allowediting.

Why Geodatabase Replication?

Geodatabase replicationsupports the creation of synchronized copies of datasets while allowing edits in both the parent and child geodatabases.

Forbranch versioned data, replication ensures that edits made in either the parent or child geodatabase can be synchronized using a two-way replica.(ArcGIS Documentation: Geodatabase Replication)

Key Features of Geodatabase Replication for This Scenario:

Two-way replicationenables editing on both sides while synchronizing changes.

Supportsbranch versioning, ensuring versioned workflows remain intact.

Maintains schema consistency across both geodatabases.

Alternative Options:

Option A: Distributed Collaboration

Collaboration is suitable for sharing data across ArcGIS Enterprise environments but does not support active synchronization for editing on both sides.

Option C: DBMS Replication

DBMS-level replication handles raw data replication but does not preserve geodatabase-specific functionalities, such as branch versioning.

Thus,geodatabase replicationis the correct method for synchronizing and editing branch versioned datasets in both geodatabases.

Scenario Overview:

Multiple editors need tocollaboratively editthe same dataset using a web application.

Requirements:

Editors work inisolationuntil they reach a stopping point.

Edits are shared with others at the stopping point.

Editors can view shared edits without sharing their own.

Branch Versioning in Enterprise Geodatabases:

Branch versioning is specifically designed for collaborative editing inweb-based workflows.

It supportsisolated editingby creating branches for each editor and allows users to reconcile and post changes at their discretion.

Editors canchoose to reconcile shared changes without posting their own edits, fulfilling the requirement to view shared edits without sharing their own.(ArcGIS Documentation: Branch Versioning)

Key Features of Branch Versioning:

Supports Web Applications:Designed to work seamlessly with feature services, enabling real-time collaborative editing.

Isolation:Each editor can edit independently in their branch.

Reconciliation:Editors can reconcile and view changes made by others without posting their edits.

Flexible Sharing:Editors control when to post edits.

Alternative Options:

Option B: Traditional versioned with editor tracking enabled:

Traditional versioning supports isolated editing, but it does not provide the flexibility to view shared changes without posting your own edits.

It is also not as well-suited for web-based collaborative workflows.

Option C: Traditional versioned with the option to move edits to base:

Moving edits to base bypasses versioning workflows entirely and is not designed for collaborative editing.

Thus,branch versioningis the optimal solution for the requirements of this collaborative editing workflow in a web application.

Scenario Overview:

Editors are spending multiple hours resolving conflicts during reconciliation.

Key points:

Conflicts are detected by attribute (not by object).

Traditional versioning is used.

Weekly compression and weekly reconcile/post workflows are in place.

Why Reconcile and Post Daily?

Conflicts occur when multiple editors make overlapping edits. The longer versions remain unreconciled, the more conflicts accumulate, leading to time-consuming resolution.

Daily reconciliation and posting minimizes the number of changes between the parent and child versions, reducing the likelihood and volume of conflicts.

(ArcGIS Documentation: Reconcile and Post)

Key Benefits of Daily Reconciliation:

Fewer Changes to Compare: With fewer edits accumulated in each version, conflict detection is faster.

Less Complex Conflicts: Simplifies resolution since changes are smaller and more recent.

Improved Editor Productivity: Editors spend less time resolving conflicts, freeing up time for other tasks.

Alternative Options:

Option A: Detect conflicts by object

While this may reduce conflict granularity, it can lead to overwriting valid edits at the object level, which may not be acceptable in collaborative workflows.

Option B: Compress the geodatabase daily

Compression reduces the state tree and improves performance but does not directly reduce the number of conflicts during reconciliation.

Therefore, implementing daily reconciliation and posting is the most effective way to reduce conflicts and improve editing efficiency.

To move an enterprise geodatabase to a new server while keeping it intact, theRDBMS export/importprocess is the appropriate method.

1. Why Use RDBMS Export/Import?

Enterprise geodatabases are tightly integrated with the underlying RDBMS (e.g., SQL Server, PostgreSQL, Oracle). Exporting and importing the entire database ensures that:

All geodatabase configurations (e.g., tables, indexes, metadata) are preserved.

No data integrity is lost during the migration process.

This method maintains the geodatabase’s structure and relationships.

2. Why Not Other Options?

Export to File Geodatabase:

While exporting to a file geodatabase allows for data transfer, it does not preserve the enterprise geodatabase structure, including user permissions, versioning, and replication configurations.

Two-Way Replication:

Replication is designed for synchronizing data changes between geodatabases, not for moving an entire geodatabase to a new server. It may also leave some administrative configurations behind.

3. Steps for RDBMS Export/Import

Export the Database:

Use the RDBMS tools (e.g., pg_dump for PostgreSQL, SQL Server Management Studio) to create a full backup of the geodatabase.

Ensure all related schemas, indexes, and metadata are included.

Import to the New Server:

Set up the RDBMS on the new server and configure it for enterprise geodatabases.

Import the backup file to restore the geodatabase on the new server.

Post-Migration Steps:

Reconfigure connections in ArcGIS Pro or ArcGIS Server to point to the new geodatabase.

Test to ensure all functionality works as expected.

References from Esri Documentation and Learning Resources:

Backing Up and Restoring an Enterprise Geodatabase

RDBMS Tools for Backup and Restore

Conclusion:

TheRDBMS export/importprocess ensures a complete migration of the enterprise geodatabase to a new server while preserving all configurations and data integrity.

To facilitate collaboration between two teams of GIS analysts located in different offices, each requiring a copy of the data in their own enterprise geodatabase with the ability to edit the same feature classes and synchronize changes nightly, geodatabase replication is the appropriate solution.

Understanding Geodatabase Replication:

Geodatabase replication is a data distribution method in ArcGIS that allows you to create copies of data across two or more geodatabases. This enables multiple users to work with the same datasets in different locations, with the ability to synchronize changes to ensure consistency.

ARCGIS PRO

Types of Geodatabase Replication:

There are three types of geodatabase replication:

One-Way Replication: Changes are sent in a single direction—from the parent to the child replica.

Two-Way Replication: Changes are synchronized in both directions between the parent and child replicas. This is suitable when multiple editors need to update the same datasets in different locations.

Checkout/Check-in Replication: Data is checked out to a child replica for editing and then checked back in to the parent replica.

In this scenario, two-way replication is ideal, as it allows both teams to edit the same feature classes and synchronize changes nightly, ensuring that both geodatabases remain consistent.

ARCGIS PRO

Alternative Options:

Database Replication: This refers to replicating entire databases at the DBMS level. While it can synchronize data, it doesn't account for the geodatabase-specific behaviors, rules, and relationships managed by ArcGIS. Therefore, it may not be suitable for scenarios requiring synchronization of geodatabase-specific functionalities.

Distributed Collaboration: This is a framework in ArcGIS Enterprise that allows sharing of content, such as maps, layers, and apps, across multiple ArcGIS Enterprise deployments or between ArcGIS Enterpriseand ArcGIS Online. However, it doesn't provide the fine-grained control over data editing and synchronization required in this scenario.

GEODATABASE RESOURCES

Therefore, to meet the requirements of both teams being able to edit the same feature classes in their respective enterprise geodatabases and synchronize changes nightly, geodatabase replication is the most appropriate solution.

When a database view performs poorly in a map, registering it with the geodatabase can significantly improve performance.

1. Why Register with the Geodatabase?

Registering a database view with the geodatabase integrates it into the geodatabase system, enabling:

Proper use of spatial indexes.

Optimization of queries by the geodatabase.

Improved handling of large datasets by leveraging geodatabase-specific performance enhancements.

2. Why Not Other Options?

Export to Shapefile:

Shapefiles are a flat file format that lacks indexing and performance optimization. Using shapefiles is not suitable for complex queries or large datasets.

Join to Another Feature Class:

Joining data does not address the root cause of performance issues in the view and may further degrade performance if the join adds complexity.

Steps to Register a Database View with the Geodatabase:

OpenArcGIS Proand connect to the database.

Use theRegister with Geodatabasetool, specifying the database view.

Configure the registration to include spatial indexes if the view contains spatial data.

Save and test the performance of the registered view in a map.

Additional Notes:

If the database view includes complex SQL logic, simplify the query if possible to further improve performance.

Ensure that the underlying tables in the view are properly indexed.

References from Esri Documentation and Learning Resources:

Registering Views with a Geodatabase

Improving Map Performance with Views

Conclusion:

Registering the database view with the geodatabase enables spatial indexing and geodatabase optimization, addressing performance issues and ensuring efficient rendering and querying.

 Understanding the Scenario:

The enterprise geodatabase receives regular updates through a "push" SQL process from a federated database.

Business rules require transformations or corrections to attribute values during the data insertion process.

The GIS administrator needs a mechanism to ensure that attribute values adhere to these rules.

 Options Overview:

Attribute Rule:

Attribute rules can enforce data integrity by applying calculations or constraints during data editing.

With calculation rules, attribute values can be automatically derived based on specific logic, ensuring that values comply with business rules.

DBMS Trigger:DBMS triggers execute procedures when database events occur (e.g., an insert). However, they are managed outside of the geodatabase environment, making them less integrated with ArcGIS workflows.

Spatial View:A spatial view combines spatial and nonspatial data but does not enforce or modify attribute values during data loading or editing.

 Steps to Configure an Attribute Rule:

Define acalculation attribute ruleon the field requiring transformation.

Specify the logic to derive or validate the attribute value based on the business rules.

Apply the rule to the dataset.

As data is inserted, the rule ensures values are updated or corrected automatically.

 References:

Esri Documentation: Attribute Rules.

Attribute Rule Types: Best practices for using calculation and validation rules in enterprise geodatabases.

 Why the Correct Answer is A:Attribute rules are specifically designed to manage attribute values and ensure compliance withbusiness logic during data editing. DBMS triggers are external and less geodatabase-centric, while spatial views do not support value transformations during insertion.

 Understanding the Scenario:

Records are being appended to a child version of a feature class registered as versioned.

Reconcile and post are taking longer than expected, suggesting complications during version synchronization.

 Key Considerations for Reconciliation Performance:

Conflicting Edits (Option A):Reconciliation time increases if there are many conflicts to resolve. However, the question does not mention concurrent edits in Default or other child versions, making conflicts less likely to be the main issue.

Updates in Default (Option B):If Default has been updated since the child version was created, the reconcile process must account for changes in Default. This can significantly increase processing time as it integrates the child version changes with the modifications in Default.

Compress Operation (Option C):The Compress operation removes redundant states in the geodatabase but does not directly affect reconciliation speed. The question does not indicate that the child version is excluded from compression or that compression is related to the delay.

 Steps to Improve Reconciliation Performance:

Minimize edits to Default during the child version's workflow.

Reconcile frequently to avoid large differences between Default and the child version.

Ensure that Compress operations are run regularly to optimize geodatabase state management.

 References:

Esri Documentation: Reconcile and Post.

Versioning Best Practices: Guidance on managing Default and child versions to minimize reconcile conflicts.

 Why the Correct Answer is B:The delay occurs because Default was updated after the child version was created. The reconciliation process must merge changes from Default with those in the child version, increasing processing time. Conflicts (A) are not mentioned, and compress operations (C) do not directly cause reconciliation delays.

Scenario Overview:

Editors reconcile and post daily, but read-only versions created for analysis are not reconciled or posted.

The geodatabase is compressed nightly, but performance continues to degrade.

Cause of the Problem:

Unreconciled versions, including read-only ones, persist in the state tree, preventing the geodatabase compression from fully collapsing unused states.

Over time, this results in a bloated state tree and worsened performance.

Solution:

Reconciling and posting the read-only versions ensures that the state tree is cleared of unnecessary versions, enabling compression to collapse the database to its optimal state.

(ArcGIS Documentation: Reconcile and Post)

Alternative Options:

Option B: Creating a database view provides a read-only representation of data but does not address the underlying issue of unresolved states in the state tree.

Option C: Disabling editor tracking is unrelated to state tree performance issues and has no impact on the reconciliation or compression processes.

Therefore, reconciling the read-only versions will significantly improve performance.

 Understanding the Scenario:

The organization requires feature classes to beeditable in mobile and web apps.

Performance optimization through indexing is also needed for common queries.

 Feature Class Storage Options:

Enterprise Geodatabase:

Supports multiuser environments, making it suitable for mobile and web app editing.

Allows indexing at the database level, which improves query performance for large datasets.

Provides robust versioning, replication, and sync capabilities for mobile workflows.

File Geodatabase:

Supports single-user access and lacks enterprise-grade indexing and multiuser editing capabilities.

Does not meet the requirements for web and mobile app editing.

Mobile Geodatabase:

Optimized for mobile apps but does not support the enterprise-level indexing and multiuser workflows required for this scenario.

 Steps for Storing and Optimizing Feature Classes:

Store the feature classes in an enterprise geodatabase.

Create indexes on frequently queried columns to optimize performance for mobile and web app queries.

Use tools likeArcGIS Proto publish feature services for mobile and web app editing.

 References:

Esri Documentation: Enterprise Geodatabases Overview.

Indexing for Performance Optimization: Guidelines for improving query performance in enterprise environments.

 Why the Correct Answer is A:Enterprise geodatabases are the only storage option that supports multiuser editing in mobile and web apps and provides advanced indexing capabilities. File and mobile geodatabases lack the necessary functionality for this use case.

Scenario Overview:

Users experienceslowing performanceacross the geodatabase, particularly for edits and drawing when adding 10,000 records.

The organization performs weekly maintenance tasks:

Rebuilding indexes and statistics

Compressing the geodatabase

Removing orphaned connections

Why Reconcile and Post Versions?

Slow performance in traditional versioning often results from excessive unreconciled versions and a bloatedstate tree.

Reconciling and posting versions reduces the number of states, enabling geodatabase compression to fully collapse redundant states and improve performance.(ArcGIS Documentation: Reconcile and Post)

Alternative Options:

Option A: Change to use Default version

This bypasses versioning workflows and does not address the root cause of performance degradation.

Option B: Update records via Python

Using Python to update records does not resolve issues caused by unreconciled versions or state tree inefficiencies.

Thus, the correct action is toreconcile and post versions, ensuring the geodatabase state tree is optimized and performance is restored.

Amosaic datasetis the most appropriate storage mechanism for visualizing and managing a centralized folder of imagery, especially when the imagery is to be accessed across an organization through an enterprise geodatabase.

1. What is a Mosaic Dataset?

A mosaic dataset is a geodatabase structure optimized for managing and serving large collections of raster data, such as satellite imagery or aerial photographs.

It provides dynamic mosaicking, rendering, and query capabilities.

2. Why Use a Mosaic Dataset?

Centralized Management: A mosaic dataset can reference multiple images stored in a folder without duplicating the data, maintaining a centralized source of imagery.

Scalability: It supports large collections of raster data and allows for efficient querying, rendering, and analysis.

On-the-Fly Processing: Provides options to apply image processing and rendering rules without modifying the source data.

Enterprise Access: Mosaic datasets stored in an enterprise geodatabase can be published as image services for access across the organization.

3. Why Not Other Options?

Raster Dataset:

This option is for storing a single image or raster layer in the geodatabase, not suitable for managing multiple images.

Raster Catalog:

Raster catalogs organize rasters but lack dynamic mosaicking, rendering, and query optimization capabilities. They are less efficient and are now considered outdated in favor of mosaic datasets.

Steps to Create and Use a Mosaic Dataset:

OpenArcGIS Proand connect to the enterprise geodatabase.

Create a new mosaic dataset using theCreate Mosaic Datasettool.

Add rasters to the mosaic dataset using theAdd Rasters to Mosaic Datasettool, pointing to the centralized folder of imagery.

Publish the mosaic dataset as an image service in ArcGIS Enterprise for organization-wide access.

References from Esri Documentation and Learning Resources:

Mosaic Datasets Overview

Managing Imagery with Mosaic Datasets

Conclusion:

Amosaic datasetprovides the best functionality for managing, visualizing, and sharing multiple images from a centralized folder within an enterprise geodatabase.

The issue arises becauseOne-way, parent to child replicationis being used. In this type of replication, changes from the parent replica (production server) overwrite the data in the child replica (consultant's server) during synchronization, regardless of edits made in the child replica.

1. One-way Replication Workflow

Parent to Child: Changes are pushed from the parent to the child. The child can make local edits, but these edits are not sent back to the parent, and they can be overwritten when synchronizing.

In this case, the consultant's edits are overwritten because the synchronization is unidirectional from the production server to the consultant's server.

2. Issue with Conflicting Edits

SinceOne-way, parent to childreplication does not support bi-directional synchronization or conflict detection, local changes in the child replica are not preserved if the parent replica pushes updates that conflict with them.

3. Why Not Other Options?

Checkout/check-in:

This replication type allows edits to be made in the checkout replica and reconciled back to the parent during check-in. This ensures that conflicting edits are addressed.

One-way, child to parent:

In this replication, edits flow from the child replica to the parent replica. The issue described does not align with this setup.

References from Esri Documentation and Learning Resources:

Geodatabase Replication—ArcGIS Pro Documentation

Understanding One-Way Replication

Conclusion:

The issue occurs becauseOne-way, parent to child replicationis being used, where edits made on the child replica are overwritten by updates from the parent replica during synchronization.

 Understanding the Scenario:

The request involves creating a view that dynamically combines data from aversioned feature classand anonspatial table.

The data needs to be from achild versionand updated dynamically.

 Key Considerations:

Versioned Feature Class:Standard feature classes in versioned geodatabases store edits in delta tables (adds and deletes). Accessing data from a specific version requires using theversioned view, which includes these edits.

Dynamic Updates:Views created on the versioned view ensure that the data reflects the most current version edits.

 Steps to Create the View:

Identify the versioned view for the feature class (created automatically during versioning).

Create a SQL query to join the versioned view and the nonspatial table on the appropriate key(s).

Save the SQL query as a database view.

 References:

Esri Documentation: Versioned Views.

Creating Views with Versioned Data: Guidelines for joining versioned views with other tables in SQL.

 Why the Correct Answer is C:Using the versioned view ensures that data reflects edits from the specified child version. Joining this view with the nonspatial table meets the requirement for dynamic updates. Options A and B would not provide data from the versioned child version dynamically.

Comprehensive Detailed Step-by-Step Explanation with All Enterprise Geodata References:

AnEnterprise geodatabaseis the most appropriate choice for this scenario due to the following reasons:

1. Requirement to Store Data Locally on Organization's Servers

AnEnterprise geodatabaseallows organizations to store GIS data locally in their own database management systems (DBMS), such as PostgreSQL, SQL Server, or Oracle.

This meets the requirement of maintaining control over data storage and ensuring the data resides within the organization's infrastructure.

2. Editing GIS Data via Web Services

Enterprise geodatabases seamlessly integrate with ArcGIS Server, enabling data editing via web services.

Organizations can publish feature services to allow authorized users to edit GIS data in real-time or in a disconnected environment (via sync).

These services support advanced editing workflows, including versioning and conflict resolution.

3. Indexing Specific Business Fields for Performance

Enterprise geodatabases offer robust indexing options to enhance query and editing performance.

You can:

Create attribute indexeson fields that are frequently queried.

Usespatial indexesto improve the speed of spatial queries.

This level of customization helps meet the performance demands of specific business workflows.

4. Advantages Over Other Storage Options

File Geodatabase:

While it is suitable for smaller datasets and local storage, it does not support multi-user editing, integration with web services, or advanced indexing for business fields.

Hosted Relational Database:

This option is part of ArcGIS Online or ArcGIS Enterprise managed services and stores data in the cloud, which contradicts the requirement for local storage.

It also does not provide the same level of control or indexing capabilities as an enterprise geodatabase.

References from Esri Documentation and Learning Resources:

Enterprise Geodatabases—ArcGIS Pro Documentation

Configuring Indexes in Geodatabases

Publishing Feature Services for Editing

Conclusion:

AnEnterprise geodatabasenot only meets all the stated requirements (local storage, web service editing, and indexed fields for performance) but also provides additional scalability, security, and multi-user editing capabilities.

The slow performance at zoomed-out extents is likely caused by the rendering of complex polygon geometries in real time, which can be computationally intensive. Using cached data is the best approach to improve performance in this situation.

1. Reason for Slow Performance at Zoomed-Out Extents

Complex polygons require significant processing power to render at smaller scales due to the high number of vertices and complex geometry.

When users zoom out, the number of features being displayed increases, causing additional strain on the map service.

Attribute queries are not affected because they do not involve rendering the geometries.

2. Advantages of Using Cached Data

Cached tiles are pre-rendered images of the map at specific scales, stored on the server.

When cached data is used, the server simply retrieves and displays these images instead of dynamically rendering the features.

This drastically reduces server load and improves map performance at zoomed-out extents.

3. Why Not Other Options?

Run the Analyze Datasets Tool:

This tool checks for issues like invalid geometries, missing spatial indexes, or improper field types. While useful for general data health, it does not directly address rendering performance.

Compress the Enterprise Geodatabase:

Compression improves performance for versioned data by consolidating states and cleaning up the database. However, in this case, the feature class is not versioned, so compression would not resolve the rendering issues.

Steps to Implement Caching:

Open ArcGIS Server Manager and navigate to the map service configuration.

Enable tile caching and define the scales at which tiles should be created (include the problematic zoomed-out extents).

Generate the cache using the "Manage Map Server Cache Tiles" tool.

Test the map to ensure performance improvements.

References from Esri Documentation and Learning Resources:

Map Caching in ArcGIS Enterprise

Best Practices for Map Services

Conclusion:

The GIS administrator should recommend enablingcached data for the zoomed extentsto significantly improve map performance.