I85PREP
⌘ K
EGMP study materials
EGMP study resources

EGMP practice questions

One question at a time. Build your EGMP understanding.

First 50 of 190 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.

Continue in the practice tool above to load more questions, 50 at a time.

Question 1Enterprise geodatabase data models, constraints and supported storage

A design team must decide between a single spatially enabled database (a database) and a full enterprise geodatabase. Which capability is available ONLY with a full enterprise geodatabase, not a plain spatial database?

  1. Connecting from ArcGIS Pro
  2. Geodatabase versioning, archiving, topology, and the geodatabase system tables Correct answer.
  3. Storing point, line, and polygon geometry
  4. Running SQL queries against spatial columns

Explanation

Geodatabase-specific behaviors such as versioning, archiving, topology, networks, and the geodatabase system tables require enabling the enterprise geodatabase. A plain spatial database can store geometry and be queried but lacks these geodatabase functions.

Question 2Enterprise geodatabase data models, constraints and supported storage

An organization needs many feature classes that share the same spatial reference and must participate together in a topology. Which geodatabase object should the design use to group them?

  1. A mosaic dataset
  2. A relationship class
  3. An attribute index
  4. A feature dataset Correct answer.

Explanation

A feature dataset groups feature classes that share a common spatial reference and is required to build datasets such as topologies, networks, and parcel fabrics that span multiple feature classes.

Question 3Enterprise geodatabase data models, constraints and supported storage

Which design choice enforces that a field accepts only a fixed set of valid values, such as a list of pipe materials?

  1. A coded value domain Correct answer.
  2. A range domain
  3. A subtype default only
  4. A spatial index

Explanation

A coded value domain restricts a field to a defined list of permitted codes and descriptions, enforcing data integrity for categorical attributes such as material type.

Question 4Enterprise geodatabase data models, constraints and supported storage

A design must automatically calculate a field value, restrict a constraint, or validate edits as they occur on a branch versioned feature class. Which capability is intended for this?

  1. Map topology
  2. Attribute rules Correct answer.
  3. Geometric networks
  4. Mosaic datasets

Explanation

Attribute rules (calculation, constraint, and validation rules written in Arcade) enforce data integrity and automate behaviors during editing. Several attribute rules require branch versioning in an enterprise geodatabase.

Question 5Enterprise geodatabase data models, constraints and supported storage

Which design pattern best separates production editing from public read access while keeping the published data current?

  1. Disable versioning and have all users share one edit session
  2. Store all data in a single file geodatabase on a network share
  3. Edit in a versioned production geodatabase and one-way replicate or publish to a read-only distribution geodatabase Correct answer.
  4. Let the public edit DEFAULT directly in the production geodatabase

Explanation

A common enterprise pattern is to edit in a versioned production database and push changes via one-way replication (or a published copy) to a read-only distribution database. This isolates editing load and protects the public-facing data.

Question 6Enterprise geodatabase data models, constraints and supported storage

An administrator must decide how to associate data with the geodatabase so a single feature class is owned and managed by one database user. What is this owner of the data called?

  1. The sde administrative user only
  2. Any viewer who has SELECT privilege
  3. The ArcGIS Server account
  4. The data owner (the database user that owns the dataset's tables) Correct answer.

Explanation

Each dataset is owned by the database user that created it, the data owner. Only the data owner can register the dataset as versioned, alter its schema, and grant or revoke privileges on it.

Question 7Enterprise geodatabase data models, constraints and supported storage

Which storage configuration mechanism lets an administrator control parameters such as table and index storage (for example tablespaces or filegroups) for newly created geodatabase datasets?

  1. The geometric network connectivity table
  2. The replica log file
  3. The Arcade expression library
  4. The DBTUNE (or DBTUNE-equivalent) configuration table and keywords Correct answer.

Explanation

The DBTUNE table stores configuration keywords that define how new geodatabase tables and indexes are created, including storage parameters such as tablespaces or filegroups. Administrators tune these keywords to optimize storage.

Question 8Enterprise geodatabase data models, constraints and supported storage

An organization needs to distribute authoritative data to many external partners who only consume it and never edit. Which approach minimizes maintenance overhead while keeping partners current?

  1. Two-way replication with each partner
  2. Giving each partner an editing connection to the production DEFAULT version
  3. Manually emailing file geodatabase copies each week
  4. One-way parent-to-child replication to read-only partner geodatabases with periodic synchronization Correct answer.

Explanation

One-way parent-to-child replication pushes changes repeatedly to read-only child geodatabases and persists between synchronizations, which is efficient for consumers who never edit. It avoids the conflict handling of two-way replication.

Question 9Branch, traditional and disconnected geodatabase workflows

A utility company plans to edit feature services through ArcGIS Enterprise web feature layers and needs full multiuser web editing with named versions. Which versioning type should the geodatabase administrator choose?

  1. Branch versioning Correct answer.
  2. Traditional versioning
  3. No versioning (non-versioned editing)
  4. Historical archiving only

Explanation

Branch versioning is designed for the Web GIS model: it supports multiuser editing through web feature layers (feature services) and uses named versions managed via services-based architecture. It is the required choice for service-based web editing workflows.

Question 10Branch, traditional and disconnected geodatabase workflows

Which dataset types in an enterprise geodatabase can ONLY be registered as branch versioned (not traditional versioned)?

  1. Network datasets and terrain datasets
  2. Utility networks, parcel fabrics, and trace networks Correct answer.
  3. Mosaic datasets and raster catalogs
  4. Feature classes with attachments only

Explanation

Utility networks, parcel fabrics, trace networks, and the linear referencing system require branch versioning. These advanced datasets depend on the services-based, web GIS editing model that only branch versioning supports.

Question 11Branch, traditional and disconnected geodatabase workflows

A geodatabase design calls for a flat version tree so that reconcile operations remain predictable. Which statement best describes this best practice?

  1. Only one version (DEFAULT) is ever created and no named versions are allowed
  2. Each version is created from a different base table to isolate edits
  3. All named versions are created as children of DEFAULT so DEFAULT is the common ancestor Correct answer.
  4. Versions are chained sequentially so each child branches from the previous child version

Explanation

A flat version tree keeps DEFAULT as the common ancestor of all named versions. This simplifies reconcile and post, reduces conflicts, and keeps the state lineage shallow, which is an Esri best practice.

Question 12Branch, traditional and disconnected geodatabase workflows

An organization must distribute editable data to a remote office that is permanently disconnected from the central network. Edits must flow in both directions and synchronize by exchanging files. Which replication type fits?

  1. One-way parent-to-child replication
  2. Checkout/check-in replication
  3. Branch version reconcile/post
  4. Two-way replication in a disconnected environment Correct answer.

Explanation

Two-way replication lets changes flow from parent to child and child to parent. In a disconnected environment, synchronization is performed by exporting data-change messages to files and importing them at the other replica.

Question 13Branch, traditional and disconnected geodatabase workflows

When designing two-way geodatabase replication, what is a requirement for both the parent and child replicas?

  1. Both must be enterprise geodatabases Correct answer.
  2. The child must be a file geodatabase
  3. Both must use branch versioning
  4. Neither may be registered as versioned

Explanation

Two-way replication requires that both the source (parent) and destination (child) be enterprise geodatabases because edits and conflict tracking flow in both directions and rely on enterprise geodatabase versioning.

Question 14Branch, traditional and disconnected geodatabase workflows

A design requires sending data changes repeatedly in a single direction from a production parent geodatabase to a read-only publication child geodatabase. Which replication type is appropriate?

  1. Branch versioning
  2. One-way parent-to-child replication Correct answer.
  3. Two-way replication
  4. Checkout/check-in replication

Explanation

One-way replication sends changes repeatedly in a single direction. In parent-to-child one-way replication the child is treated as read-only, which suits a publication or distribution database.

Question 15Branch, traditional and disconnected geodatabase workflows

Which statement correctly contrasts where editing occurs in branch versus traditional versioning?

  1. Both branch and traditional versioning require a feature service for editing
  2. Both branch and traditional versioning forbid direct database connection editing
  3. Branch versioned data is edited only through a feature service; traditional versioned data can be edited via a direct database connection Correct answer.
  4. Branch versioned data is edited only via direct database connection; traditional versioned data is edited only through services

Explanation

Branch versioned data must be edited through a feature service (services-based architecture) and cannot be edited directly via a database connection. Traditional versioned data can be edited through a direct connection to the enterprise geodatabase.

Question 16Branch, traditional and disconnected geodatabase workflows

An administrator wants to retain a queryable record of all changes (a full history) to branch versioned feature classes so users can view the data at any past moment. Which capability provides this?

  1. A two-way replica
  2. A non-versioned table copy
  3. A spatial index on the OBJECTID field
  4. Branch versioning's built-in archiving (moment-in-time queries) Correct answer.

Explanation

Branch-versioned temporal/history capabilities can support queries of retained historical states under the actual product and data model. They do not promise every past moment forever:retention, pruning, supported operations and recorded history constrain what remains queryable. Versioning is not an independent complete backup.

Question 17Branch, traditional and disconnected geodatabase workflows

When planning to serve enterprise geodatabase data to web clients for editing, which serving method is required for branch versioned editing?

  1. A direct OLE DB connection from the browser
  2. A static shapefile download
  3. A WMS image service
  4. A published feature service from ArcGIS Enterprise (a feature layer) Correct answer.

Explanation

Branch versioned editing is performed through a published feature service (feature layer) hosted by ArcGIS Enterprise. The services-based architecture mediates all branch version edits.

Question 18Branch, traditional and disconnected geodatabase workflows

Which statement about concurrent editing of a single named branch version is correct?

  1. Only one editor can edit a given named version at a time; an exclusive lock is acquired when editing begins Correct answer.
  2. Unlimited editors can edit the same named branch version simultaneously without locks
  3. Branch versions never acquire locks under any circumstance
  4. Editing a branch version automatically posts to DEFAULT immediately

Explanation

In branch versioning, when an editor begins editing a named version an exclusive lock is obtained, so only one editor can edit that version at a time while others may read. This prevents conflicting concurrent edits within the same version.

Question 19Branch, traditional and disconnected geodatabase workflows

A design must support disconnected field crews who check out a subset of data to a file geodatabase, edit it offline, and synchronize once when they return. Which replica type is most appropriate?

  1. Historical archive query
  2. Checkout/check-in replication Correct answer.
  3. Two-way connected replication
  4. Branch versioning with named versions

Explanation

Checkout/check-in replication lets a child (which may be a file geodatabase) take a subset offline, edit it, and synchronize once; after synchronization the checkout replica is unregistered. This matches a one-time field collection round trip.

Question 20Branch, traditional and disconnected geodatabase workflows

Which is a valid reason to choose traditional versioning over branch versioning for a particular workflow?

  1. The workflow needs moment-in-time archiving without any setup
  2. The workflow needs service-based web editing of feature layers
  3. The data must participate in geodatabase replication, which is supported only with traditional versioning Correct answer.
  4. The data is a utility network, which requires versioning

Explanation

Geodatabase replication (checkout, one-way, two-way) is supported only with traditional versioning, so workflows requiring those replicas must use traditional versioning. Network datasets and terrain datasets also require traditional versioning.

Question 21Branch, traditional and disconnected geodatabase workflows

In a traditional-versioning design with referenced states and delta tables, which listed maintenance practice can help reduce eligible state-tree growth over time?

  1. Reconcile and post child edits to DEFAULT regularly and run Compress Correct answer.
  2. Never run Compress so all states are preserved
  3. Create deeply nested child-of-child versions
  4. Disable the geodatabase system tables

Explanation

Regularly reconciling and posting edits to DEFAULT and then running Compress trims unreferenced states from the state tree and moves edits from delta tables into the base tables, keeping the geodatabase performant.

Question 22Branch, traditional and disconnected geodatabase workflows

Which design decision best supports a parcel fabric in an enterprise geodatabase?

  1. Store the parcel fabric in a file geodatabase for multiuser web editing
  2. Register the data as branch versioned and edit through feature services Correct answer.
  3. Register the data as traditional versioned and edit through a direct connection
  4. Keep the data non-versioned with single-session editing

Explanation

The parcel fabric requires branch versioning and is edited through feature services in the web GIS model. This enables the multiuser, services-based editing that the modern parcel fabric depends on.

Question 23Branch, traditional and disconnected geodatabase workflows

Which statement about one-way replication and archiving is correct?

  1. Checkout replication requires archiving to be enabled
  2. Archiving is only available for non-versioned data
  3. For one-way replication you can use archiving instead of versioning to track changes, keeping reconcile/post/compress separate from synchronization Correct answer.
  4. Two-way replication can use archiving instead of versioning

Explanation

For one-way replication, archiving can be used in place of versioning to track changes to replicate. This decouples the reconcile, post, and compress maintenance from the synchronization process and can simplify administration.

Question 24Branch, traditional and disconnected geodatabase workflows

An organization wants to estimate how a branch versioned dataset will grow because edits are retained in the base table with editor tracking. Which underlying model explains this growth?

  1. Branch versioning's temporal model retains rows for each edit moment in the base table rather than deleting them Correct answer.
  2. Branch versioning stores all edits in separate A and D delta tables that are deleted on compress
  3. Branch versioning never retains superseded rows
  4. Branch versioning writes edits only to a file geodatabase

Explanation

The branch temporal model records relevant edit history in its supported tables, which can increase storage. Actual retention and supported history-pruning/maintenance affect what remains;the model does not mean rows can never be removed or that every earlier state is guaranteed indefinitely. Plan capacity and retention under actual requirements.

Question 25Branch, traditional and disconnected geodatabase workflows

A geodatabase design must support both occasional cartographic editors using ArcGIS Pro and field crews using mobile apps with offline maps. Which combination best satisfies both?

  1. Static shapefile exports distributed by email
  2. Branch versioning with feature services that have offline (sync-enabled) capability for the field crews Correct answer.
  3. Traditional versioning edited only through direct database connections for everyone
  4. Non-versioned editing with no feature services

Explanation

Branch versioning published as sync-enabled feature services lets office editors work through services while mobile crews take offline maps (areas) and synchronize. This single services-based model serves both audiences in the web GIS pattern.

Question 26Branch, traditional and disconnected geodatabase workflows

Which is the correct order to fully reconcile and post a child version's edits so they appear in DEFAULT in traditional versioning?

  1. Compress first, then reconcile, then never post
  2. Delete DEFAULT and recreate it from the child
  3. Reconcile the child version against DEFAULT, resolve conflicts, then post to DEFAULT Correct answer.
  4. Post to DEFAULT first, then reconcile afterward

Explanation

You reconcile the edit version against the target (DEFAULT) to pull in DEFAULT's changes and detect conflicts, resolve any conflicts, and then post to push the child's edits into DEFAULT. Posting before reconciling is not allowed.

Question 27Branch, traditional and disconnected geodatabase workflows

Which factor most strongly favors branch versioning when designing a new multiuser editing system in 2026?

  1. The intent to edit through the ArcGIS Enterprise web GIS using feature services Correct answer.
  2. A requirement to use geodatabase replication
  3. A requirement to edit a legacy geometric network
  4. A requirement to use a network dataset for routing edits

Explanation

Branch versioning is the recommended model when editing occurs through ArcGIS Enterprise feature services in the web GIS pattern. Esri positions branch versioning as the modern approach for service-based multiuser editing.

Question 28ArcGIS operational evidence, identity and controlled lifecycle changes

Which is a recommended security best practice when configuring connections for a published ArcGIS Server feature service to an enterprise geodatabase?

  1. Register the data store using a least-privilege service account that has only the access the service needs Correct answer.
  2. Register the data store with the sde administrator account so the service can do anything
  3. Embed each end user's personal credentials in the service
  4. Allow anonymous database authentication for the service

Explanation

Registering the data store with a dedicated least-privilege service account limits the blast radius if the service is compromised. The service should hold only the privileges it requires to read or edit its datasets.

Question 29Enterprise geodatabase data models, constraints and supported storage

Which geoprocessing tool creates a new enterprise geodatabase, including the sde repository, in a supported DBMS that does not yet host a geodatabase?

  1. Register With Geodatabase
  2. Create Enterprise Geodatabase Correct answer.
  3. Enable Enterprise Geodatabase
  4. Create Database Connection

Explanation

Create Enterprise Geodatabase provisions a new geodatabase, creating the sde repository (geodatabase system tables) in a supported DBMS in one operation. It is the standard tool for first-time geodatabase creation.

Question 30Enterprise geodatabase data models, constraints and supported storage

An administrator is provisioning a geodatabase in a managed cloud database (for example Azure SQL Database). Which tool must be used to add geodatabase functionality?

  1. Upgrade Geodatabase
  2. Compress
  3. Enable Enterprise Geodatabase Correct answer.
  4. Create Enterprise Geodatabase

Explanation

For managed cloud databases, you must use Enable Enterprise Geodatabase on the already-provisioned database because the cloud service, not ArcGIS, creates the database itself. Create Enterprise Geodatabase is not used for managed cloud services.

Question 31Enterprise geodatabase data models, constraints and supported storage

Which collation and isolation settings does SQL Server require for a database that will host an enterprise geodatabase used with branch versioning?

  1. A case-insensitive collation with READ_COMMITTED_SNAPSHOT and ALLOW_SNAPSHOT_ISOLATION set ON Correct answer.
  2. A case-sensitive collation with snapshot isolation OFF
  3. Binary collation with all isolation disabled
  4. Any collation and isolation; SQL Server has no requirements

Explanation

Esri requires the SQL Server instance/database to use a case-insensitive collation, and branch versioning requires READ_COMMITTED_SNAPSHOT and ALLOW_SNAPSHOT_ISOLATION to be ON. These settings ensure correct concurrency for geodatabase operations.

Question 32Enterprise geodatabase data models, constraints and supported storage

Which database user typically must be used to create or enable the geodatabase repository in Oracle or PostgreSQL?

  1. The ArcGIS Server service account only
  2. A user named sde (the geodatabase administrator) Correct answer.
  3. The default DEFAULT version owner
  4. Any read-only viewer account

Explanation

In Oracle, PostgreSQL, Db2, and SAP HANA the geodatabase repository is created in the schema of a user named sde, the geodatabase administrator. The sde user owns the geodatabase system tables.

Question 33Enterprise geodatabase data models, constraints and supported storage

An administrator wants users to connect to the enterprise geodatabase from ArcGIS Pro. Which object stores the connection properties (instance, database, authentication) for reuse?

  1. A project package (.ppkx)
  2. A geoprocessing model (.tbx)
  3. A database connection file (.sde) Correct answer.
  4. A layer file (.lyrx)

Explanation

A database connection file (.sde) stores the server/instance, database, and authentication details needed to connect to an enterprise geodatabase. It is created with Create Database Connection and shared with users.

Question 34Enterprise geodatabase data models, constraints and supported storage

Which authentication option lets the operating system validate a user's identity for the geodatabase connection rather than storing a database username and password?

  1. Database authentication with saved credentials
  2. Anonymous public access
  3. Token-only authentication with no account
  4. Operating system (Windows/OS) authentication Correct answer.

Explanation

Operating system authentication uses the logged-in OS account to authenticate to the database, avoiding stored database credentials in the connection. Database authentication, by contrast, stores a database username and password.

Question 35Enterprise geodatabase data models, constraints and supported storage

A data owner must give an editing group permission to insert, update, and delete features in a feature class. Which privilege must also be granted for editing to work?

  1. The select (view) privilege, in addition to insert/update/delete Correct answer.
  2. Only the delete privilege
  3. The schema-alter privilege on the geodatabase
  4. The compress privilege

Explanation

To edit a dataset, users need select (view) in addition to insert, update, and delete. When you grant edit privileges the view privilege must also be granted so the editor can read the data being changed.

Question 36Enterprise geodatabase data models, constraints and supported storage

In the ordinary ArcGIS dataset-privilege management workflow for a dataset, which listed account is required to connect to grant or revoke its privileges through the data-owner tool?

  1. Every member of the editor group
  2. Only the dataset's owner (the user who owns the tables) Correct answer.
  3. Any user with select privilege
  4. Only the ArcGIS Server account

Explanation

The dataset owner is the relevant connection identity for the supplied ArcGIS privilege-management workflow. This does not assert that an underlying DBMS administrator lacks all independent grant authority. Use supported tools, effective permissions and actual database governance rather than treating two administrative scopes as identical.

Question 37Enterprise geodatabase data models, constraints and supported storage

When granting edit privileges on a feature class that belongs to a feature dataset, what is true about the other feature classes in that feature dataset?

  1. Privileges cannot be granted on feature classes inside a feature dataset
  2. Only the first feature class created receives privileges
  3. All feature classes in the feature dataset must have the same privileges applied Correct answer.
  4. Each feature class can have completely independent privileges

Explanation

All feature classes within a feature dataset must share the same privileges. Granting an edit privilege on one effectively requires the same privileges across the dataset to maintain integrity of datasets like topologies and networks.

Question 38Enterprise geodatabase data models, constraints and supported storage

Which tool registers an existing DBMS table or view (created with SQL) so that ArcGIS treats it as a geodatabase dataset with an ObjectID?

  1. Create Enterprise Geodatabase
  2. Analyze Datasets
  3. Rebuild Indexes
  4. Register With Geodatabase Correct answer.

Explanation

Register With Geodatabase registers a database table, view, or query layer with the geodatabase, assigning an ObjectID and enabling geodatabase behaviors. This is how SQL-created content participates in the geodatabase.

Question 39Enterprise geodatabase data models, constraints and supported storage

An administrator wants new feature classes to be created with a specific storage keyword controlling tablespace and index placement. Where is this configured?

  1. In the DBTUNE configuration keywords applied at dataset creation time Correct answer.
  2. In the layer's symbology properties
  3. In the replica synchronization log
  4. In the map's coordinate system definition

Explanation

DBTUNE configuration keywords define the storage parameters (tablespaces, filegroups, index options) used when a dataset is created. Choosing a configuration keyword at creation applies those storage settings.

Question 40Enterprise geodatabase data models, constraints and supported storage

An administrator must restrict a group of users to read-only access on a published dataset while a separate group edits it. Which configuration achieves this with least privilege?

  1. Grant insert/update/delete to both groups
  2. Make all users the data owner
  3. Grant the read-only group the schema-alter privilege
  4. Grant select only to the read-only group and select plus insert/update/delete to the editor group Correct answer.

Explanation

Following least privilege, viewers receive only select, while editors receive select plus insert, update, and delete. This separates read access from edit access cleanly.

Question 41Enterprise geodatabase data models, constraints and supported storage

Which statement about the geodatabase system tables (the sde repository) is correct?

  1. They store metadata about datasets, versions, states, and configuration, and should not be edited directly with SQL Correct answer.
  2. They are optional and can be deleted to save space
  3. They store only the map symbology
  4. They are recreated automatically on every connection

Explanation

The geodatabase system tables track datasets, versions, states, locks, and configuration keywords. They are essential and must be managed through ArcGIS tools, not edited directly with SQL, to avoid corruption.

Question 42Enterprise geodatabase data models, constraints and supported storage

When configuring a geodatabase in Oracle, what must be set up before geodatabase functionality can use the Esri spatial type?

  1. All indexes must be disabled
  2. The st_geometry shape library must be configured for the Oracle instance Correct answer.
  3. A two-way replica must be defined
  4. The DEFAULT version must be deleted

Explanation

In Oracle you must configure the st_geometry library so the database can store and operate on ST_Geometry. Without it, the geodatabase cannot enable ST_Geometry storage.

Question 43Enterprise geodatabase data models, constraints and supported storage

Which configuration object lets an administrator partition features of one feature class into categories that can each carry distinct default values and domains, without creating separate feature classes?

  1. Mosaic datasets
  2. Map topology
  3. Spatial indexes
  4. Subtypes Correct answer.

Explanation

Subtypes divide features of a single feature class into categories (for example pipe types) that can have their own default values and attribute domains. This improves data integrity and editing efficiency without extra feature classes.

Question 44Branch, traditional and disconnected geodatabase workflows

To support disconnected mobile data collection from a branch versioned feature service, which capability must be enabled on the published feature layer?

  1. KML network link output
  2. Sync (offline) capability so map areas can be taken offline and synchronized Correct answer.
  3. WMS image rendering
  4. Geocoding capability

Explanation

Enabling the sync capability lets field apps take map areas offline and later synchronize edits with the branch versioned data. Without sync, the feature layer cannot support offline mobile workflows.

Question 45Branch, traditional and disconnected geodatabase workflows

Which step is required to register a dataset as branch versioned in an enterprise geodatabase?

  1. The dataset must have all indexes dropped first
  2. The dataset must be unregistered from the geodatabase
  3. The dataset must have GlobalIDs and editor tracking enabled before registering as branch versioned Correct answer.
  4. The dataset must be stored in a file geodatabase

Explanation

Branch versioning requires GlobalIDs and editor tracking on the dataset, because the temporal model identifies and tracks each feature's edits by GlobalID and edit moment. These must be enabled before registering as branch versioned.

Question 46Branch, traditional and disconnected geodatabase workflows

Which approach lets an administrator centrally configure organization-wide editing through ArcGIS Enterprise rather than per-user direct connections?

  1. Email a file geodatabase to each editor
  2. Give every editor the sde administrator password
  3. Publish branch versioned data as feature services and manage access through the portal and feature service capabilities Correct answer.
  4. Distribute individual .sde connection files to every editor for direct database editing of branch versioned data

Explanation

Branch versioned editing is centralized through published feature services in ArcGIS Enterprise, where portal sharing and service capabilities govern access. This avoids managing many direct database connections.

Question 47Branch, traditional and disconnected geodatabase workflows

Which configuration enables ArcGIS to record who created or last edited each feature, supporting auditing and branch versioning?

  1. A relationship class to a log table
  2. Editor tracking (creator, creation date, editor, last-edit date fields) Correct answer.
  3. A range domain
  4. A spatial index on GlobalID

Explanation

Editor tracking adds and maintains fields recording the creator, creation date, last editor, and last-edit date. It supports auditing and is required for branch versioning's temporal model.

Question 48Branch, traditional and disconnected geodatabase workflows

An administrator must configure a geodatabase so that two editors in different named branch versions can work concurrently without blocking each other. What enables this isolation?

  1. Editors must coordinate manually because versions cannot isolate edits
  2. All edits are immediately visible to every user as they are typed
  3. Each editor works in a separate named version, and edits are isolated until reconciled and posted to DEFAULT Correct answer.
  4. Both editors share DEFAULT and rely on row locks

Explanation

Named versions isolate each editor's work; changes are not visible in DEFAULT until reconciled and posted. This lets multiple editors work concurrently in their own versions without blocking each other.

Question 49Geodatabase loading, performance and recoverable maintenance

An administrator must update an older enterprise geodatabase so it supports new client and dataset capabilities. Which tool performs the in-place schema update of the geodatabase system tables?

  1. Create Enterprise Geodatabase
  2. Compress
  3. Rebuild Indexes
  4. Upgrade Geodatabase Correct answer.

Explanation

Upgrade Geodatabase updates the geodatabase system tables and schema to a newer release, enabling new functionality. It is run by the geodatabase administrator after the DBMS client and ArcGIS are at compatible versions.

Question 50Enterprise geodatabase data models, constraints and supported storage

Which geoprocessing tool appends features from a source dataset into an existing target feature class, matching fields by name or a field map?

  1. Append Correct answer.
  2. Create Enterprise Geodatabase
  3. Compress
  4. Reconcile Versions

Explanation

The Append tool loads features from one or more sources into an existing target dataset, using a field map to control how source fields map to target fields. It is a primary tool for incremental data loading.