[2025年最新] 高合格率な最新EGMP2201テストノートとEGMP2201高合格率な試験ガイドを試そう
EGMP2201実際の問題アンサーPDFには100%カバーリアル試験問題
ESRI EGMP2201認定試験は、エンタープライズ環境で地理空間データを扱う専門家にとって不可欠な資格です。この認定は、候補者がARCGISエンタープライズを使用して地理空間ソリューションを実装および管理するスキルと知識を持っていることを確認しています。これは、ジオーダタ管理におけるグローバルに認められている卓越性の基準であり、地理空間産業で雇用を求める専門家に競争上の優位性を提供します。
質問 # 12
A user plans to use a standard database view of a roads feature class from a geodatabase that is different from the primary enterprise geodatabase. Roads is frequently edited in the parent geodatabase, so the user needs to regularly synchronize and have the view recognize all incoming edits immediately.
Which replica type should be used?
- A. One-way replica with the simple model
- B. Two-way replication simple model
- C. One-way replica with the full model
正解：C
解説：
Scenario Overview:
* The user requires a standard database view of theroads feature classthat resides in a different geodatabase from the primary enterprise geodatabase.
* Theroads feature classis frequently edited, and the user needs the view to recognize updates immediately.
Replica Types in ArcGIS:
* One-way replicationwith thefull modelis suitable for scenarios where the parent geodatabase sends updates to the child geodatabase, and all schema and data changes are synchronized.
* In thefull model, the child database retains versioning and acknowledges updates as they occur in the parent database, enabling the user to see immediate updates in their standard view.(ArcGIS Documentation: Geodatabase Replication Types) Key Features of the Full Model:
* Synchronizesboth schema and datachanges.
* Suitable for feature classes withfrequent edits.
* Ensures that the standard database view reflects updates immediately upon synchronization.
Alternative Options:
* Option A:The simple model in one-way replication supports data-only synchronization and does not update schema changes, making it insufficient for dynamic environments.
* Option C:Two-way replication is unnecessary since the edits occur only in the parent geodatabase.
Thus,one-way replication with the full modelis the appropriate choice to meet the requirement.
質問 # 13
After running a Compress, the GIS administrator needs to check if the Adds and Deletes tables for Buildings are empty before unregistering as versioned.
What should be referenced by the GIS administrator?
- A. table_registry
- B. gdbjtems
- C. sdejayers
正解：C
解説：
To determine if theAddsandDeletestables for the "Buildings" dataset are empty before unregistering as versioned, the GIS administrator needs to reference thesde_layerstable.
1. Purpose of the sde_layers Table
* Thesde_layerstable tracks the relationship between base tables and the associated delta tables (Adds and Deletes).
* For each versioned dataset, the sde_layers table contains entries linking the dataset to its corresponding A and D tables (e.g., A_<ObjectID> and D_<ObjectID>).
2. Steps to Verify Adds and Deletes
* Identify theObjectIDof the Buildings dataset in thesde_layerstable.
* Query the Adds table (A_<ObjectID>) and Deletes table (D_<ObjectID>) associated with the Buildings dataset:
SELECT COUNT(*) FROM A_<ObjectID>;
SELECT COUNT(*) FROM D_<ObjectID>;
* If both queries return 0, the Adds and Deletes tables are empty, and it is safe to unregister the dataset as versioned.
3. Why Not Other Options?
* table_registry: This table tracks registered datasets but does not provide information about delta tables or their contents.
* gdb_items: This table stores metadata for datasets but does not have details on delta table contents.
References from Esri Documentation and Learning Resources:
* Compressing a Geodatabase-ArcGIS Pro Documentation
* Delta Tables in Versioned Geodatabases
Conclusion:
The GIS administrator must query thesde_layerstable to verify the Adds and Deletes tables before unregistering the dataset as versioned.
質問 # 14
A GIS data administrator needs to implement an offline mobile editing workflow that will include feature classes that participate in a geometric network.
Which versioning model should the data administrator use?
- A. Traditional versioning without move edits to base
- B. Traditional versioning with move edits to base
- C. Branch versioning
正解：A
解説：
Geometric networks are not supported inbranch versioningor workflows where edits are moved directly to the base table. Therefore,traditional versioning without move edits to baseis the only viable option for implementing an offline mobile editing workflow with feature classes that participate in a geometric network.
1. Why Use Traditional Versioning Without Move Edits to Base?
* Support for Geometric Networks:
* Geometric networks are only compatible with traditional versioning workflows. Branch versioning does not support geometric networks, and using the "move edits to base" option bypasses the versioning framework required for geometric networks.
* Offline Mobile Editing:
* Traditional versioning supports creating replicas that allow offline editing and subsequent synchronization. This workflow is critical for mobile editing scenarios.
2. Why Not Other Options?
* Branch Versioning:
* Branch versioning is designed for feature services and web-based workflows but does not support geometric networks.
* Traditional Versioning with Move Edits to Base:
* This option moves edits directly to the base table, which is incompatible with geometric networks and versioning workflows that require offline editing.
Steps to Configure Traditional Versioning Without Move Edits to Base:
* Register the feature classes and datasets (including geometric networks) with traditional versioning in ArcGIS Pro.
* Create a replica to support offline editing workflows.
* Synchronize edits back to the geodatabase after offline editing, reconcile, and post to integrate changes into the Default version.
References from Esri Documentation and Learning Resources:
* Traditional Versioning Overview
* Geometric Networks and Versioning
Conclusion:
Usingtraditional versioning without move edits to baseis the only method that supports offline mobile editing workflows while maintaining compatibility with geometric networks.
質問 # 15
A GIS analyst needs to share a large repository of lidar data with the organization. This lidar data will have surface constraints applied for breaklines.
Which type of dataset should the GIS analyst use?
- A. Feature dataset
- B. Mosaic dataset
- C. LAS dataset
正解：C
解説：
Understanding the Scenario:
* The GIS analyst needs to share a large repository oflidar data.
* The data includes surface constraints like breaklines, which are used to enforce terrain or surface rules.
Dataset Types Overview:
* Mosaic Dataset:Designed for managing large collections of raster data, such as imagery or elevation grids. It is not specifically optimized for lidar point cloud data.
* Feature Dataset:A container for related feature classes in a geodatabase. It is unrelated to managing lidar data or surface constraints.
* LAS Dataset:A specialized dataset designed for managing lidar point clouds. It supports point classification, surface constraints (like breaklines), and efficient querying or visualization of lidar data.
Steps to Create and Share a LAS Dataset:
* Create a LAS dataset in ArcGIS Pro and add lidar files (LAS or ZLAS format).
* Define surface constraints (breaklines) in the LAS dataset properties.
* Share the LAS dataset as a service or package for organizational access.
References:
* Esri Documentation: LAS Datasets.
* Managing Breaklines in LAS Datasets: Instructions for incorporating surface constraints.
Why the Correct Answer is C:LAS datasets are explicitly designed for managing and sharing lidar data with surface constraints like breaklines. Mosaic and feature datasets are unsuitable for this purpose.
質問 # 16
An editor connects to an enterprise geodatabase to edit a feature class that uses traditional versioning. The editor uses the following workflow:
* The Default version is set lo protected
* A new child version is created from Default
* The child version is set to protected
* Edits are saved to the child version
* The editor tries to reconcile and post to Default
The reconcile is successful, but the post operation fails with an error. What should the editor do?
- A. Create a one-way replica from the child version and synchronize to Default
- B. Ask the owner of Default to perform the reconcile and post for the editor
- C. Change the access level of the child version from protected to public
正解：B
解説：
In traditional versioning within an enterprise geodatabase, theDefaultversion often represents the published state of the database. Setting the Default version toprotectedensures that while all users can view it, only the geodatabase administrator or the version owner can edit it directly or post changes to it.
ArcGIS Pro
In the scenario provided, the editor follows these steps:
* Default Version Set to Protected:This restricts editing and posting privileges to the geodatabase administrator or the version owner.
* Creation of a Child Version from Default:The editor creates a new version branching from Default.
* Child Version Set to Protected:This means only the editor (as the owner) or the geodatabase administrator can edit this child version.
* Edits Saved to the Child Version:The editor makes and saves changes within this child version.
* Attempt to Reconcile and Post to Default:The editor successfully reconciles but encounters an error during the post operation.
The error during the post operation arises because, with the Default version set to protected, the editor lacks the necessary permissions to post changes directly to it. Only the geodatabase administrator or the owner of the Default version possesses the authority to perform this action.
ArcGIS Pro
Analysis of Options:
* Option A:Changing the access level of the child version from protected to public does not grant the editor the required permissions to post to the protected Default version.
* Option B:Requesting the owner of the Default version (typically the geodatabase administrator) to perform the reconcile and post is appropriate. This individual has the necessary permissions to post changes to the protected Default version.
* Option C:Creating a one-way replica and synchronizing is an unnecessary and complex approach for this situation.
Therefore, the editor shouldask the owner of Default to perform the reconcile and postto ensure the changes are integrated into the Default version.
質問 # 17
An organization needs to distribute data to a regional office. The regional office does not have ArcGIS Enterprise orArcGIS Online accounts. The regional office also does not have access to an enterprise geodatabase.
Which data distribution solution should be used?
- A. Geodatabase replication
- B. Partnered collaborations
- C. Distributed collaboration
正解：A
解説：
Understanding the Scenario:
* The regional office lacks access toArcGIS Enterprise,ArcGIS Online accounts, or anenterprise geodatabase.
* Data must be distributed in a format that the regional office can use independently of enterprise-level systems.
Data Distribution Solutions Overview:
* Geodatabase Replication:
* Geodatabase replication allows data to be exported and shared with external systems, such as file or personal geodatabases.
* Replicas can be set up in adisconnected mode, enabling regional offices to work with the data offline.
* Distributed Collaboration:Distributed collaboration facilitates sharing data and content between ArcGIS Enterprise and ArcGIS Online environments. It is unsuitable for offices without these systems.
* Partnered Collaborations:Partnered collaborations extend distributed collaboration to partner organizations, but they also require ArcGIS Online accounts, making them incompatible with this scenario.
Steps to Implement Geodatabase Replication:
* Create aone-way replicaof the data in a format compatible with the regional office's systems (e.g., file geodatabase).
* Transfer the replica to the regional office via portable media or secure file sharing.
* Set up periodic updates if the data needs to be refreshed.
References:
* Esri Documentation: Geodatabase Replication.
* Disconnected Workflows: Best practices for sharing data in offline environments.
Why the Correct Answer is A:Geodatabase replication is the most suitable solution for sharing data with a regional office that lacks enterprise-level systems. Distributed and partnered collaborations require ArcGIS Enterprise or ArcGIS Online accounts, which are unavailable in this scenario.
質問 # 18
A GIS administrator learns that geodatabase users report decreasing performance when adding data from child versions to their map.
* The organization uses a complex traditional version tree architecture
* Python script completes batch-reconcile/post operations, compresses the geodatabase, and data owners rebuild indexes and update statistics
* Python script runs overnight with little to no geodatabase connections being made Which Analyze Datasets parameter should be checked?
- A. Analyze Archive Tables For Selected Datasets
- B. Include System Tables
- C. Analyze Base Tables For Selected Datasets
正解：C
解説：
When users experience performance issues while adding data from child versions in a complex traditional version tree, it often indicates problems with thebase tables. TheAnalyze Base Tables For Selected Datasets parameter is the most relevant in this case.
1. Role of Base Tables in Traditional Versioning
* In traditional versioning, thebase tablestores the original data for the feature class or table. Changes made in child versions are tracked in delta tables (Adds and Deletes).
* If the base table is not optimized (e.g., outdated statistics, fragmented indexes), performance can degrade when querying or rendering data.
2. Why Analyze Base Tables?
* TheAnalyze Base Tables For Selected Datasetsparameter evaluates and updates the database statistics for the base tables to improve query optimization.
* This process ensures the database query optimizer can make efficient decisions when retrieving data.
3. Why Not Other Options?
* Include System Tables:
* This analyzes geodatabase system tables, which are crucial for administrative tasks but unrelated to performance issues with user datasets.
* Analyze Archive Tables For Selected Datasets:
* This is specific to datasets with archiving enabled. There is no mention of archiving being used in this scenario.
Steps to Analyze Base Tables:
* OpenArcGIS Proor use a Python script with theAnalyze Datasetstool.
* Specify the datasets with performance issues.
* Select theAnalyze Base Tables For Selected Datasetsparameter.
* Run the tool and monitor the updated statistics.
References from Esri Documentation and Learning Resources:
* Analyze Datasets Tool
* Improving Query Performance
Conclusion:
TheAnalyze Base Tables For Selected Datasetsparameter should be used to update statistics and improve performance when adding data from child versions in traditional versioning.
質問 # 19
A GIS administrator needs to facilitate the collaboration of two teams of GIS analysts in two different offices.
Each office needs a copy of the data in its own enterprise geodatabase. and analysts in both offices will edit the same feature classes. Changes will be synchronized nightly.
The GIS administrator needs to set up the information infrastructure so that both teams can work together.
What should the administrator use to meet the requirements?
- A. Geodatabase replication
- B. Database replication
- C. Distributed collaboration
正解：A
解説：
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.
質問 # 20
A GIS administrator needs all users to immediately see the edits that are made while editing a feature class.
Which configuration should be used?
- A. Traditional versioned editing
- B. Nonversioned editing
- C. Branch versioned editing
正解：B
解説：
Understanding the Scenario:
* Edits made to a feature class need to be immediately visible to all users.
* This indicates a requirement for direct edits to the base tables without any versioning overhead.
Editing Configuration Overview:
* Traditional Versioned Editing:Edits are made to delta tables and require version reconciliation and posting to be visible to other users. This introduces a delay and does not meet the requirement for immediate visibility.
* Nonversioned Editing:Edits are applied directly to the base table of the feature class, ensuring they are immediately visible to all users. This is the correct choice for the scenario.
* Branch Versioned Editing:Edits are made in a branch version and are not immediately visible to other users unless the edits are saved to the default branch. This is not the best choice for immediate visibility.
Steps to Configure Nonversioned Editing:
* Ensure the feature class is set to nonversioned editing mode in the enterprise geodatabase.
* Grant necessary permissions for all users to edit the base table.
* All edits made to the dataset will instantly reflect for all users.
References:
* Esri Documentation: Nonversioned Editing.
Why the Correct Answer is B:Nonversioned editing is the only configuration that ensures immediate visibility of edits to all users. Traditional and branch versioning involve workflows that delay edit visibility.
質問 # 21
A user accidentally deletes an enterprise geodatabase feature dataset.
Which technology should be used to resolve the issue?
- A. Backup
- B. High availability
- C. Archiving
正解：A
解説：
Understanding the Scenario:
* An enterprise geodatabase feature dataset is accidentally deleted.
* The organization needs to recover the dataset to its original state.
Available Technologies:
* High Availability:High availability setups (e.g., failover systems) ensure continuous access to geodatabases during hardware or software failures. However, high availability does not restore accidentally deleted data.
* Backup:A backup is a snapshot of the geodatabase taken at a specific point in time. It allows administrators to restore deleted datasets or recover from data loss scenarios.
* Archiving:Archiving tracks historical edits in versioned geodatabases but does not provide recovery for accidentally deleted datasets.
Steps to Recover the Dataset:
* Identify the most recent backup of the enterprise geodatabase.
* Restore the geodatabase or extract the specific feature dataset from the backup.
* Verify the restored data and synchronize it with ongoing updates if necessary.
References:
* Esri Documentation: Backup and Restore.
* Best Practices for Data Protection: Guidelines for implementing regular backups to prevent data loss.
Why the Correct Answer is B:A backup is the most reliable solution for recovering an accidentally deleted feature dataset. High availability ensures uptime but does not address data recovery, and archiving tracks edits rather than preserving entire datasets.
質問 # 22
A wells feature class has one row per well. A well_inspections table has one row for each time a well was inspected. All inspection dates need to be displayed as labels clustered around each well on the map.
Which kind of association should be used to meet this requirement?
- A. Relationship class
- B. Relate
- C. Join
正解：B
質問 # 23
A GIS administrator needs to simultaneously grant access for multiple users of a branch versioned feature class in an enterprise geodatabase.
How should permissions be granted?
- A. To a group
- B. To a role
- C. To a list
正解：B
解説：
Understanding the Scenario:The GIS administrator wants to simultaneously grant access to multiple users for a branch-versioned feature class in an enterprise geodatabase. Managing permissions for individual users can be inefficient, especially for larger teams, making roles a better solution.
Why Grant Permissions to a Role:
* Role-Based Access Control (RBAC):In enterprise geodatabases, assigning permissions to a role allows administrators to define access levels once and apply them to multiple users who are members of that role. This simplifies management and ensures consistent permission levels across users.
* Branch Versioning Considerations:In branch versioned datasets, role-based permissions ensure that all users working with the feature class can access, edit, or view data as needed without individual customization.
Steps to Assign Permissions to a Role:
* Create a role in the database or use an existing one.
* Assign permissions for the branch versioned feature class to the role (e.g., read, edit, or administrative permissions).
* Add users to the role.
* All users in the role inherit the permissions automatically.
References:
* Esri Documentation: Best practices for managing permissions in enterprise geodatabases: Managing Users and Roles.
* Branch Versioning Overview: Information on the unique requirements for branch versioned data:
Branch Versioning.
Why the Correct Answer is A:Using roles allows the GIS administrator to efficiently grant and manage access for multiple users at once. Options like lists or groups are not applicable in the context of enterprise geodatabases, as roles are the standard mechanism for assigning permissions.
質問 # 24
A GIS data administrator needs to store color, model, and size attributes for different kinds of valves. Pick lists should only show permitted combinations of color, model, and size.
Which geodatabase capability should be configured?
- A. Subtypes with domains
- B. Domains
- C. Contingent values
正解：C
解説：
Scenario Overview:
* The administrator needs to store attributes for valves (e.g., color, model, and size).
* Pick listsmust display only valid combinations of these attributes.
Why Contingent Values?
* Contingent valuesallow geodatabases to enforce specific, dependent attribute combinations.
* For example, if certain sizes are only valid for specific models and colors, contingent values ensure only permitted combinations are displayed in pick lists.(ArcGIS Documentation: Contingent Values) How Contingent Values Work:
* Attribute domains are defined for individual fields (e.g., color, model, size).
* Contingent value rules are configured to establish relationships between the fields, restricting invalid combinations.
* When editing data, pick lists dynamically adjust based on contingent value rules, showing only valid options.
Alternative Options:
* Option A: Domains
* Attribute domains enforce constraints on individual fields but cannot define dependencies between fields.
* Option B: Subtypes with domains
* Subtypes group features into categories with distinct domain rules but do not support interdependent attribute combinations.
Thus,contingent valuesare the appropriate geodatabase capability to configure pick lists for valid attribute combinations.
質問 # 25
A telecommunications company implements branch versioning for their organization. The default version is the published version that portal users see and editors can post edits to.
Which version access level should be set?
- A. Private
- B. Public
- C. Protected
正解：C
解説：
In a branch versioning workflow where thedefault versionis the published version that users see and editors can post edits to, setting the access level toProtectedis the best choice.
1. What Does the Protected Access Level Do?
* TheProtectedaccess level allows users to view and query the version but restricts editing to authorized users only.
* This ensures that only authorized editors can post changes to the default version, maintaining data integrity while allowing portal users to access the published version.
2. Why Not Other Options?
* Public:
* A public version allows anyone with appropriate permissions to edit the version. This could lead to uncontrolled changes and data integrity issues.
* Private:
* A private version restricts access to the version to only the owner and specific users, which is unsuitable when the default version is meant to be the published version visible to all portal users.
Steps to Configure Protected Access Level:
* OpenArcGIS ProorArcGIS Enterprise Manager.
* Navigate to the version management settings for the default version.
* Set theAccess LeveltoProtected.
* Ensure that editors with appropriate privileges are assigned to post changes to the default version.
References from Esri Documentation and Learning Resources:
* Version Access Levels in Branch Versioning
* Branch Versioning Workflows
Conclusion:
Setting the default version toProtectedensures a balance between providing access to portal users and restricting edits to authorized personnel.
質問 # 26
A GIS analyst needs to track feature class changes and keep the reconcile, post, and compress processes separate from the replica synchronization process.
What should the analyst do?
- A. Create a two-way replica using the archive option on Default
- B. Create a one-way replica using the archive option on a child version of Default
- C. Create a one-way replica using the archive option on Default
正解：C
解説：
To track feature class changes while keeping thereconcile, post, and compress processesseparate from the replica synchronization process, the best approach is tocreate a one-way replica using the archive option on Default.
1. Why Use a One-Way Replica on Default?
* One-Way Replication:
* Sends data changes from the parent (Default version) to the child geodatabase, ensuring that synchronization does not interfere with the parent geodatabase's versioning operations.
* Archive Option:
* Archiving captures all changes to the feature class, providing a history of edits without requiring versioning in the replica.
2. Why Choose the Default Version?
* Using the Default version as the parent ensures that all reconciled and posted changes are synchronized to the replica, making the synchronization independent of ongoing versioning workflows in the geodatabase.
3. Why Not Other Options?
* Create a One-Way Replica Using the Archive Option on a Child Version of Default:
* Replicating from a child version complicates workflows because the child version must be reconciled and posted to Default before updates are reflected in the replica.
* Create a Two-Way Replica Using the Archive Option on Default:
* Two-way replication synchronizes changes in both directions. This would integrate changes from the child geodatabase into Default, interfering with the reconciliation and posting processes.
Steps to Create the Replica:
* Ensure archiving is enabled for the feature classes in the Default version.
* Use theCreate Replicatool in ArcGIS Pro and selectOne-Way Replication.
* Configure the replica to include the archive option.
* Synchronize the replica as needed without affecting versioning processes in the parent geodatabase.
References from Esri Documentation and Learning Resources:
* One-Way Replication Overview
* Geodatabase Archiving
Conclusion:
To track changes while separating reconcile, post, and compress processes from synchronization, the GIS analyst shouldcreate a one-way replica using the archive option on Default.
質問 # 27
A GIS administrator receives reports of slowing performance across the entire geodatabase. Users report that the time for edits to be made and drawing are affected when adding 10.000 records. Traditional versioning is being used.
The following processes are completed weekly:
* Rebuilding of indexes and statistics
* Geodatabase compress
* Remove orphaned connections
Which action should be taken?
- A. Update records via Python
- B. Change to use Default version
- C. Reconcile and post versions
正解：C
解説：
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.
質問 # 28
A GIS administrator is investigating reports of slow performance in a map of complex polygons. The investigation finds the following:
* The feature class is in an enterprise geodatabase
* This data has been published as a map service in ArcGIS Enterprise
* The feature class is not versioned
* The map seems to perform slowly at several zoomed-out extents in the map
* Queries on the attributes perform quickly
Which recommendation should the GIS administrator make?
- A. Compress the enterprise geodatabase
- B. Show cached data for the zoomed extents
- C. Run the Analyze Datasets tool
正解：B
解説：
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.
質問 # 29
......
EGMP2201試験問題とアンサー：https://jp.fast2test.com/EGMP2201-premium-file.html