GIS - Geographic Information System Geodatabase Design and Management Questions and Answers

Question 1

A GIS administrator is designing a geodatabase for a utilities company to manage water distribution assets.
To ensure data integrity, the design specifies that for any 'Water_Mains' feature, the 'Material' field (e.g., 'Ductile Iron', 'PVC') must dictate the valid range of values for the 'Diameter_Inches' field.
For instance, PVC pipes are only available in diameters from 4 to 12 inches, while Ductile Iron is available from 6 to 36 inches.
Which geodatabase mechanism is specifically designed to enforce this type of conditional attribute validation?

Accepted Answer

Contingent values

Answer

Subtypes with associated range domains

Answer

Relationship classes with rules

Answer

Coded value domains

Question 2

An enterprise geodatabase is experiencing performance degradation during periods of heavy editing by multiple concurrent users. A consultant has been hired to recommend maintenance tasks. Which of the following is a critical, routine maintenance operation for an enterprise geodatabase that removes unreferenced states and moves entries from delta tables into the base tables to improve query performance?

Accepted Answer

Compressing the geodatabase

Answer

Rebuilding spatial indexes

Answer

Shrinking the database files

Answer

Updating database statistics

Question 3

A county's planning department maintains separate feature classes for 'Parcels' and 'Zoning'. To enforce data integrity, they need to implement a rule ensuring that every parcel polygon must be completely contained within a single zoning polygon. Which of the following geodatabase components and rules would be most appropriate to enforce this spatial relationship?

Accepted Answer

A geodatabase topology with a 'Must Be Covered By' rule

Answer

A relationship class with 1:1 cardinality

Answer

A subtype on the 'Parcels' feature class

Answer

A range domain on the parcel area attribute

Question 4

Which of the following best differentiates geodatabase replication from versioning?

Accepted Answer

Replication creates full copies of data in different geodatabases for synchronization, while versioning manages multiple states of data within a single geodatabase.

Answer

Versioning is used for disconnected editing, while replication is for managing long transactions in a connected environment.

Answer

Versioning creates a parent-child relationship between geodatabases, while replication creates peer-to-peer connections.

Answer

Replication is only used for file geodatabases, while versioning is exclusive to enterprise geodatabases.

Question 5

When designing a geodatabase schema, a GIS analyst needs to categorize a 'Roads' feature class into 'Highway', 'Arterial', and 'Local' types. Each road type must have a different default value for the 'SpeedLimit' field and a different set of valid materials in the 'Pavement' field. What is the most efficient geodatabase design element to achieve this?

Accepted Answer

Implementing subtypes based on an integer 'RoadType' field.

Answer

Creating three separate feature classes, one for each road type.

Answer

Using a coded value domain on a 'RoadType' text field.

Answer

Establishing a relationship class linking roads to a road types table.

Question 6

A city manages its utility pole assets in a 'Poles' feature class and inspection records in a non-spatial 'Inspections' table. A key requirement is that if a utility pole is deleted from the geodatabase, all of its associated inspection records must also be automatically deleted. Which type of relationship class is required to enforce this behavior?

Accepted Answer

Composite relationship class

Answer

Simple relationship class

Answer

Many-to-many relationship class

Answer

Attributed relationship class