EGMP flashcards
EGMP · Build recall with a focused review session.
24 cards. Read the term and the definition here. The deck at the top of this page is optional.
- Feature dataset
- A geodatabase grouping for compatible feature classes that can support relevant shared spatial behavior under actual dataset requirements.
- Coded value domain
- A constraint defining an allowed set of attribute values in its supported scope, distinct from arbitrary free-text labeling or a database user role.
- Subtype
- A supported classification of rows in a feature class or table that can apply relevant defaults/domains without creating a separate class for every category.
- Field map
- A supported correspondence between input and output fields during loading or transformation, which still requires checking types, units and intended meaning.
- Named branch version
- A supported isolated editing version created from default under the branch model’s hierarchy and lock rules, not an arbitrary independent database copy.
- Reconcile
- A version comparison operation under configured conflict rules, distinct from automatically choosing the correct business value or completing every post operation.
- Post
- The supported application of relevant reconciled edits to the target version under actual authority, distinct from merely saving a local screen or editing metadata.
- Retained historical moment
- A view of data history supported by records actually retained under the applicable temporal/versioning model, not a promise of every past state forever.
- Referenced state
- A traditional-versioning state still needed by relevant versions or transactions, which cannot simply be discarded because a cleanup was requested.
- Optimizer statistics
- Information describing relevant data distributions for query planning, which can become stale and differs from an index or actual performance measurement.
- Spatial index
- An access structure supporting relevant spatial predicates under the actual DBMS/type configuration, not a universal cure for every slow map or query.
- Controlled bulk load
- A supported large data transfer with justified mapping, privileges, validation and recovery arrangements, rather than permission to disable required constraints indiscriminately.
- Hosting server
- The designated supported ArcGIS GIS Server role supplying relevant hosted capabilities for a portal, distinct from every federated server site.
- Registered data
- A supported data source referenced by a service at its registered location, distinct from an automatically managed hosted copy or every portal item.
- Component instance
- A particular running installation or execution instance of a product component, distinct from the number of product-family names in an architecture list.
- Nonfunctional requirement
- A stated quality or operating constraint such as response time, availability or security, whose satisfaction requires actual design and validation evidence.
- Surviving capacity
- The usable resource capacity remaining under a specified failure or maintenance condition, which can be less than the total installed rating.
- Service demand
- The relevant resource work per request under a representative workload model, requiring explicit units and conditions when translating throughput into capacity.
- Recovery boundary
- The actual configuration, data, dependencies and time consistency covered by a recovery arrangement, not every external source merely referenced by the system.
- Shared failure dependency
- A resource or condition common to nominally redundant components, which can defeat the intended resilience when the modeled event affects it.
- Federation relationship
- A supported portal/server integration affecting relevant security and administration, distinct from assuming every service has the same underlying data permissions.
- Effective sharing
- The actual item/service access arising from relevant settings, identity and roles, which an item title or successful login does not establish alone.
- Version-specific upgrade path
- The supported sequence, compatibility and downtime conditions for an actual release/platform change, not a generic rolling-update recipe from another product.
- Diagnostic correlation
- Comparison of relevant logs, timestamps, paths and measured behavior to investigate a condition without treating one symptom as conclusive root-cause proof.