Practice Free EGMP2201 Exam Online Questions
An organization has ArcGIS Enterprise. A new project requires versioned editing with the ability to show which user deleted a feature from the default version.
Which editing workflow should be used?
- A . Branch versioned editing
- B . Traditional versioned editing
- C . Nonversioned editing
A
Explanation:
Scenario Overview:
The organization has ArcGIS Enterprise and requires versioned editing.
The project mandates tracking which user deleted a feature from the default version.
Why Branch Versioned Editing?
Branch versioning supports versioned editing workflows and integrates seamlessly with editor tracking, including operations like tracking who deleted a feature.
It is ideal for web-based workflows in ArcGIS Enterprise and allows for direct interaction with feature services.
The default version remains accessible for analysis while enabling the organization to track user edits, including feature deletions.
(ArcGIS Documentation: Branch Versioning)
Alternative Options:
Option B: Traditional versioned editing supports versioned workflows but does not inherently track who deletes features unless additional workflows are implemented (e.g., custom fields or triggers). Option C: Nonversioned editing does not support versioning workflows or user tracking.
Thus, branch versioned editing is the best workflow to support versioned editing while tracking deleted features.
An organization has ArcGIS Enterprise. A new project requires versioned editing with the ability to show which user deleted a feature from the default version.
Which editing workflow should be used?
- A . Branch versioned editing
- B . Traditional versioned editing
- C . Nonversioned editing
A
Explanation:
Scenario Overview:
The organization has ArcGIS Enterprise and requires versioned editing.
The project mandates tracking which user deleted a feature from the default version.
Why Branch Versioned Editing?
Branch versioning supports versioned editing workflows and integrates seamlessly with editor tracking, including operations like tracking who deleted a feature.
It is ideal for web-based workflows in ArcGIS Enterprise and allows for direct interaction with feature services.
The default version remains accessible for analysis while enabling the organization to track user edits, including feature deletions.
(ArcGIS Documentation: Branch Versioning)
Alternative Options:
Option B: Traditional versioned editing supports versioned workflows but does not inherently track who deletes features unless additional workflows are implemented (e.g., custom fields or triggers). Option C: Nonversioned editing does not support versioning workflows or user tracking.
Thus, branch versioned editing is the best workflow to support versioned editing while tracking deleted features.
An organization has ArcGIS Enterprise. A new project requires versioned editing with the ability to show which user deleted a feature from the default version.
Which editing workflow should be used?
- A . Branch versioned editing
- B . Traditional versioned editing
- C . Nonversioned editing
A
Explanation:
Scenario Overview:
The organization has ArcGIS Enterprise and requires versioned editing.
The project mandates tracking which user deleted a feature from the default version.
Why Branch Versioned Editing?
Branch versioning supports versioned editing workflows and integrates seamlessly with editor tracking, including operations like tracking who deleted a feature.
It is ideal for web-based workflows in ArcGIS Enterprise and allows for direct interaction with feature services.
The default version remains accessible for analysis while enabling the organization to track user edits, including feature deletions.
(ArcGIS Documentation: Branch Versioning)
Alternative Options:
Option B: Traditional versioned editing supports versioned workflows but does not inherently track who deletes features unless additional workflows are implemented (e.g., custom fields or triggers). Option C: Nonversioned editing does not support versioning workflows or user tracking.
Thus, branch versioned editing is the best workflow to support versioned editing while tracking deleted features.
An organization has ArcGIS Enterprise. A new project requires versioned editing with the ability to show which user deleted a feature from the default version.
Which editing workflow should be used?
- A . Branch versioned editing
- B . Traditional versioned editing
- C . Nonversioned editing
A
Explanation:
Scenario Overview:
The organization has ArcGIS Enterprise and requires versioned editing.
The project mandates tracking which user deleted a feature from the default version.
Why Branch Versioned Editing?
Branch versioning supports versioned editing workflows and integrates seamlessly with editor tracking, including operations like tracking who deleted a feature.
It is ideal for web-based workflows in ArcGIS Enterprise and allows for direct interaction with feature services.
The default version remains accessible for analysis while enabling the organization to track user edits, including feature deletions.
(ArcGIS Documentation: Branch Versioning)
Alternative Options:
Option B: Traditional versioned editing supports versioned workflows but does not inherently track who deletes features unless additional workflows are implemented (e.g., custom fields or triggers). Option C: Nonversioned editing does not support versioning workflows or user tracking.
Thus, branch versioned editing is the best workflow to support versioned editing while tracking deleted features.
AGIS data administrator needs to migrate the enterprise geodatabase to another server and wants to have the following changes:
• New enterprise geodatabase name
• Changed Repository tables owner from SDE to DBO Which migration workflow should be used?
- A . Restore a database backup
- B . Create a new enterprise geodatabase
- C . Migrate Storage geoprocessing tool
B
Explanation:
To migrate an enterprise geodatabase to another server while changing its name and repository table owner, creating a new enterprise geodatabase is the most appropriate workflow.
AGIS data administrator needs to migrate the enterprise geodatabase to another server and wants to have the following changes:
• New enterprise geodatabase name
• Changed Repository tables owner from SDE to DBO Which migration workflow should be used?
- A . Restore a database backup
- B . Create a new enterprise geodatabase
- C . Migrate Storage geoprocessing tool
B
Explanation:
To migrate an enterprise geodatabase to another server while changing its name and repository table owner, creating a new enterprise geodatabase is the most appropriate workflow.
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 . Public
- B . Protected
- C . Private
B
Explanation:
In a branch versioning workflow where the default version is the published version that users see and editors can post edits to, setting the access level to Protected is the best choice.
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 . Public
- B . Protected
- C . Private
B
Explanation:
In a branch versioning workflow where the default version is the published version that users see and editors can post edits to, setting the access level to Protected is the best choice.
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 . Public
- B . Protected
- C . Private
B
Explanation:
In a branch versioning workflow where the default version is the published version that users see and editors can post edits to, setting the access level to Protected is the best choice.
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 . Public
- B . Protected
- C . Private
B
Explanation:
In a branch versioning workflow where the default version is the published version that users see and editors can post edits to, setting the access level to Protected is the best choice.