EGMP study guide
EGMP · Work through your exam, one topic at a time.
This independent study page provides practice for EGMP. Its editorial learning areas include Enterprise geodatabase data models, constraints and supported storage; Branch, traditional and disconnected geodatabase workflows; Geodatabase loading, performance and recoverable maintenance; ArcGIS Enterprise components, service roles and architecture boundaries; ArcGIS workload capacity, availability and recoverability; ArcGIS operational evidence, identity and controlled lifecycle changes. The EGMP study guide has 6 sections and about 2,149 words.
01Enterprise geodatabase data models, constraints and supported storage
A geodatabase design describes feature/table identity, attributes, relationships and intended spatial behavior. Identify key uniqueness, cardinality, required fields, coordinate reference and quality rules before choosing an implementation.
359 words, about 2 min02Branch, traditional and disconnected geodatabase workflows
Versioning supports relevant isolated editing workflows, but branch and traditional approaches have different service and administration models. Branch versioning supports long-transaction editing through web feature layers, with supported version-management capability and dataset requirements.
367 words, about 2 min03Geodatabase loading, performance and recoverable maintenance
Traditional versioning can accumulate states and delta-table rows referenced by active versions and transactions. Appropriate reconcile/post, obsolete-version handling and Compress can reduce eligible state lineage under the actual prerequisites.
345 words, about 2 min04ArcGIS Enterprise components, service roles and architecture boundaries
Begin with intended users, workflows, data, functional behavior and nonfunctional requirements. Availability, response time, growth, security and operational constraints shape architecture alongside the actual licensed capabilities.
360 words, about 2 min05ArcGIS workload capacity, availability and recoverability
Named users, active sessions, concurrent requests and throughput are not interchangeable counts. Record the relevant service mix, request cost, response size, peak demand and acceptable response time.
355 words, about 2 min06ArcGIS operational evidence, identity and controlled lifecycle changes
A client request can depend on DNS, TLS, a proxy/Web Adaptor, the portal or server, a service and its actual data source. An error at one layer does not uniquely identify every underlying cause.
363 words, about 2 min