ArcGIS Branch Versioning – Key Concepts and Workflows

0.0(0)
studied byStudied by 0 people
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
Card Sorting

1/52

flashcard set

Earn XP

Description and Tags

These flashcards cover the essential ideas, workflows, and administration tasks for implementing, sharing, editing, reconciling, and synchronizing branch-versioned data in ArcGIS Enterprise and ArcGIS Pro, including permission models, conflict detection, and offline editing.

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

53 Terms

1
New cards

What is branch versioning in ArcGIS?

A service-based versioning model in ArcGIS Enterprise that lets multiple users edit the same enterprise geodatabase data through feature services while maintaining isolated versions and supporting Web GIS workflows.

2
New cards

Which tables store edits in branch versioning?

A single business table with editor-tracking fields; no delta or state/timestamp tables are used.

3
New cards

How many levels can a branch version tree have below DEFAULT?

Only one; all named versions are children of DEFAULT and cannot be children of other named versions.

4
New cards

Give three general benefits of branch versioning.

No compress needed, highly scalable service architecture, always records who changed what and when.

5
New cards

Name two editing capabilities available only with branch versioning.

Utility Networks and Parcel Fabrics support, trace networks or LRS (linear referencing system).

6
New cards

Which three steps enable branch versioning on a feature class?

1) Register as versioned; 2) Add GlobalIDs; 3) Enable editor tracking (all done automatically when branch versioning is applied).

7
New cards

Where do you set the branch workspace property in ArcGIS Pro?

In the Geodatabase Connection Properties of the database connection.

8
New cards

Which ArcGIS Server instance type must be used when publishing branch versioned data?

Dedicated Instance pooling.

9
New cards

Which feature-layer capability must be checked to allow web-based version creation and management?

Version Management capability.

10
New cards

What two portal items are created when you share branch-versioned data?

A Map Image Layer (view) and a Feature Layer (edit) with an accompanying Version Management Service.

11
New cards

What operations can be allowed when enabling editing on a feature layer?

Add, Delete, and Update (Attributes Only or Attributes And Geometry).

12
New cards

Which dialog in ArcGIS Pro is used to auto-assign unique numeric IDs before publishing?

Share As Web Layer analyzer – Auto-Assign IDs Sequentially option.

13
New cards

What is the purpose of registering a data store with ArcGIS Enterprise?

To inform the server how to access user-managed enterprise geodatabase data so services can reference, not copy, the data.

14
New cards

List the five default ArcGIS Enterprise user types.

Viewer, Editor, Mobile Worker, Creator, GIS Professional.

15
New cards

Why might you create a custom portal role for an editor lead?

To grant specific privileges such as Manage All versions without giving full administrator rights.

16
New cards

Who can act as a branch version administrator?

(1) Layer owner, (2) portal admins, (3) members with a custom role that includes Manage All version privilege, or (4) members of a shared-update group containing the layer.

17
New cards

What are the three access permission settings for a branch version?

Public, Protected, Private.

18
New cards

What does setting DEFAULT to ‘Protected’ do?

Only version administrators can edit DEFAULT or post changes to it; others must post through a version administrator.

19
New cards

Which account can change DEFAULT’s access type?

The geodatabase administrator (SDE).

20
New cards

What two portal mechanisms are commonly used to control branch-layer access?

Groups (for membership) and Roles (for privileges).

21
New cards

Define ‘Update-Update’ conflict.

Two editors modify the same feature/row in different ways before one reconciles with DEFAULT.

22
New cards

Define ‘Update-Delete’ conflict.

One editor updates a feature while another deletes the same feature before reconcile.

23
New cards

What two rules can be used to define conflicts during reconcile?

By Row (Object) or By Column (Attribute).

24
New cards

Name the three versions displayed in the Conflicts view.

Current (edit) version, Target (DEFAULT) version, Common Ancestor version.

25
New cards

Which reconcile option keeps edits from the named version when conflicts occur?

Resolve in favor of the Edit/Current version.

26
New cards

How does ArcGIS Pro lock a named version during editing?

The first user to connect places a write lock; other users cannot connect until the lock is released.

27
New cards

What are the basic steps in the offline editing workflow in ArcGIS Pro?

Download Map -> Work Offline & Edit -> Sync Changes (optionally Delete Download).

28
New cards

What data requirement is mandatory for features to be edited offline?

Global IDs must exist on all editable tables/feature classes.

29
New cards

Which feature-service operation enables offline sync?

Sync capability (enabled under Feature Access settings).

30
New cards

What advanced sync option creates a separate version per download?

‘Create a version for each downloaded map’ (requires replica tracking).

31
New cards

Which geoprocessing tool must be run before per-replica versions can be created?

Enable Replica Tracking (run by the data owner).

32
New cards

Where are downloaded offline edits stored on disk?

In a mobile geodatabase (.geodatabase file) saved within the project’s \OfflineEdits folder.

33
New cards

After removing an offline map in ArcGIS Pro, what happens to the map’s layer sources?

They automatically refresh to reference the original service/DEFAULT data.

34
New cards

Which editor-tracking fields record who made and last edited a feature?

CreatedUser and LastEdited_User (plus corresponding date fields).

35
New cards

What two analyzer errors are common when publishing branch-versioned data?

Data source not registered with server, and unique numeric IDs not assigned.

36
New cards

How can you share user-managed data with other publishers?

Share the registered enterprise data store item with those users or a publishing group.

37
New cards

What is a ‘replica version’?

A uniquely named branch version automatically created during map download to isolate offline edits until sync.

38
New cards

When does ArcGIS Pro automatically delete a mobile geodatabase?

When the user clicks Remove Download and chooses to delete it.

39
New cards

Which column in a branch-versioned layer’s attribute table shows who last edited a feature?

LASTEDITEDUSER (or LastEditedUser).

40
New cards

Which two service items must be shared with viewers who need read-only access?

Typically only the Map Image Layer, but Feature Layer can also be shared if edit privileges are withheld.

41
New cards

What does checking ‘Shared Update’ when creating a group allow?

Group members can update (overwrite, delete, share) each other’s items; cannot be disabled later.

42
New cards

How can a layer owner restrict non-admins from posting directly to DEFAULT but still let them edit?

Set DEFAULT to Protected and require version administrators to post on behalf of editors.

43
New cards

What button opens the Conflicts view in ArcGIS Pro after reconcile detects conflicts?

Yes button in the Reconcile Results dialog or the View Conflicts button on the Versioning tab.

44
New cards

How are write locks released on a named version?

When the user who opened the version closes the connection (e.g., closes ArcGIS Pro or changes version).

45
New cards

What happens if you attempt to post to DEFAULT when it is Protected and you lack privileges?

ArcGIS Pro returns a ‘Version is read-only’ or ‘Cannot post, version protected’ error.

46
New cards

Which map property indicates you are working in an offline state?

The ‘Map Offline’ badge/icon and layer sources pointing to a mobile geodatabase.

47
New cards

Why is branch versioning considered ‘SOA-oriented’?

All version management and editing operations occur through RESTful web services adhering to a service-oriented architecture.

48
New cards

Which capability removes the need for database compress operations in branch versioning?

Edits are stored directly in the business table without delta tables, eliminating compress requirements.

49
New cards

Can traditional and branch versions coexist in the same enterprise geodatabase?

Yes; each feature class/table can be registered as traditional, branch, or left non-versioned independently.

50
New cards

Name three dataset types that require branch (not traditional) versioning.

Utility Networks, Parcel Fabrics, Trace Networks (also LRS networks).

51
New cards

What is required to publish a network dataset with versioning?

Traditional versioning (network datasets are not yet supported with branch).

52
New cards

Which privilege must be added to allow a custom role to manage all versions?

Version Management – Manage All privilege.

53
New cards

How can you verify whether a feature class is already versioned in ArcGIS Pro?

Open its Properties > Source tab and check the Versioning entry.