Esri EGMP2201 Exam - Topic 2 Question 7 Discussion

Actual exam question for Esri's EGMP2201 exam

Question #: 7
Topic #: 2

An organization uses a two-way replica to share edits for a polygon feature class with a field office. After months of synchronizing edits, a schema change takes place using the following workflow;

* A new field called a legal_area is added to a polygon feature class in the parent geodatabase

* An editor uses the Calculate Geometry tool to calculate legal_area for each polygon

* The child geodatabase does not have the legal_area field in the polygon feature class

* The parent geodatabase synchronizes the replica to the child geodatabase

What happens during synchronization?

AAn error message occurs

BThe synchronization adds the missing field

CThe synchronization succeeds

Show Suggested Answer

Suggested Answer: A

Understanding the Scenario:

A two-way replica exists between a parent geodatabase and a child geodatabase to share edits.

A schema change (adding the legal_area field) occurs in the parent geodatabase but is not applied to the child geodatabase.

The parent synchronizes the replica, attempting to push changes that include edits to the new field.

Replica Synchronization Behavior:

Schema Changes and Replication: Replication does not automatically synchronize schema changes such as adding new fields. Schema updates need to be manually applied to both parent and child geodatabases before synchronization.

Conflict during Synchronization: If schema changes (like adding a field) are made in the parent geodatabase but not replicated in the child geodatabase, synchronization attempts to apply edits referencing the missing field. This results in an error because the child geodatabase does not recognize the new field.

Reference:

Esri Documentation: Schema Changes and Replication.

Error Handling in Synchronization: Guidance on managing synchronization issues due to schema mismatches.

Why the Correct Answer is A: During synchronization, an error occurs because the legal_area field does not exist in the child geodatabase. Synchronization cannot succeed unless both replicas have compatible schemas.

by Annette at Jan 11, 2025, 01:32 AM

Limited Time Offer

25%

Off

Get Premium EGMP2201 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Johanna

3 months ago

Surprised this isn't a bigger issue in geodatabase management!

upvoted 0 times

...

Dong

3 months ago

No way it adds the missing field automatically!

upvoted 0 times

...

Juan

3 months ago

I think it just succeeds, but I'm not sure.

upvoted 0 times

...

Tony

4 months ago

Definitely an error message! Can't sync missing fields.

upvoted 0 times

...

Sharmaine

4 months ago

The child geodatabase won't have the new field after sync.

upvoted 0 times

...

Fabiola

4 months ago

I thought that when a new field is added, it would automatically be created in the child geodatabase during sync, so option B seems possible, but I’m not completely confident.

upvoted 0 times

...

Eliz

4 months ago

If the field is missing in the child geodatabase, I feel like the synchronization might just skip that field and succeed, but I can't recall for sure.

upvoted 0 times

...

Candra

4 months ago

I think I practiced a similar question where a missing field led to a synchronization failure, so I’m leaning towards option A.

upvoted 0 times

...

Pearly

5 months ago

I remember something about schema changes causing issues during synchronization, but I'm not sure if it always results in an error.

upvoted 0 times

...

Shawn

5 months ago

I'm feeling pretty confident about this one. The question is clear that the child geodatabase doesn't have the new field, so the sync is going to fail and an error message will occur.

upvoted 0 times

...

Dianne

5 months ago

I think I've got a handle on this. The schema change introduces a new field, but the child geodatabase doesn't have it. So the sync is likely to fail and throw an error message.

upvoted 0 times

...

Pauline

5 months ago

Okay, let's see. The key here is that the child geodatabase doesn't have the new legal_area field. I'm guessing that's going to cause some issues during the sync process.

upvoted 0 times

...

Vi

5 months ago

Hmm, I'm a bit unsure about this one. The question is asking what happens during synchronization, so I'll need to carefully consider the steps involved and how the schema change could affect that.

upvoted 0 times

...

Rory

5 months ago

This seems like a tricky one. I'll need to think through the schema change and how that might impact the synchronization process.

upvoted 0 times

...

Denae

1 year ago

This is a tricky one, but I think the right answer is A. An error message is the only reasonable outcome when you try to sync a new field that doesn't exist on the other side.

upvoted 0 times

Erasmo

11 months ago

I'm not sure about that, but I think option C makes sense in this scenario.

upvoted 0 times

...

Evelynn

12 months ago

Actually, I believe the answer is C. The synchronization should succeed without any issues.

upvoted 0 times

...

Sarah

12 months ago

I agree with you, option B seems like the most logical outcome.

upvoted 0 times

...

Julio

12 months ago

I think the correct answer is B. The synchronization adds the missing field.

upvoted 0 times

...

Hailey

1 year ago

Haha, this is a classic case of 'you broke it, you bought it.' Of course the sync is going to fail! The child geodatabase needs to be updated first.

upvoted 0 times

Herman

1 year ago

Looks like someone forgot to update the child geodatabase before syncing.

upvoted 0 times

...

Penney

1 year ago

The sync will definitely fail, the child geodatabase needs to be updated first.

upvoted 0 times

...

Val

1 year ago

I'm going to go with option A. An error message is definitely the most likely outcome here. You can't just sync a new field like that.

upvoted 0 times

...

Carla

1 year ago

Hmm, I think the synchronization will fail and throw an error. You can't just add a new field to one side of a replica without that field existing on the other side.

upvoted 0 times

Lashonda

1 year ago

User 2

upvoted 0 times

...

Beatriz

1 year ago

User 1

upvoted 0 times

...

Breana

1 year ago

That makes sense, the workflow seems to indicate that the Calculate Geometry tool will populate the legal_area field for each polygon.

upvoted 0 times

...

Claribel

1 year ago

The synchronization should fail since the child geodatabase does not have the new field. The parent geodatabase can't just add a field to the child without any issues.

upvoted 0 times