Discuss Esri EGMP2201 Exam Topic 4 Question 4

A GIS data manager needs to set up one-way parent-to-child replication to provide read-only copies of data to regional offices. The replication must be set up so that the parent geodatabase can be fully compressed, even if there are unacknowledged data change messages.

How should the replication be configured?

AReplicate only the base tables

BUse the Full replica access type

CUse the Archiving option

Suggested Answer: A

To ensure that the parent geodatabase can be fully compressed, even with unacknowledged data change messages, the replication must be configured to replicate only the base tables.

1. What Happens with Unacknowledged Messages?

In traditional one-way replication, unacknowledged data change messages in the delta tables (Adds and Deletes) prevent full compression of the parent geodatabase.

By replicating only the base tables, the replication avoids using delta tables entirely, allowing the geodatabase to be fully compressed.

2. Why Replicate Only the Base Tables?

No Dependency on Delta Tables: This configuration ensures that the replication is based directly on the base table contents. As changes are not recorded in delta tables for replication, the parent geodatabase can be fully compressed without any impact.

Read-Only Copies: The replicated data in the child geodatabase will be read-only, which aligns with the requirement for regional offices.

3. Why Not Other Options?

Use the Full Replica Access Type:

Full replica access allows editing in the child geodatabase, which is unnecessary for read-only requirements. It also uses delta tables, preventing full compression.

Use the Archiving Option:

Archiving tracks historical edits and is unrelated to the replication or compression process. It does not solve the problem of unacknowledged messages blocking compression.

Steps to Set Up One-Way Replication with Base Tables:

Open ArcGIS Pro and connect to the parent geodatabase.

Use the Create Replica tool and select One-Way Replication.

Choose the option to replicate base tables only during the configuration process.

Define the datasets to replicate and complete the replication setup.

Reference from Esri Documentation and Learning Resources:

One-Way Replication Overview

Compressing Enterprise Geodatabases

Conclusion:

Configuring replication to replicate only the base tables ensures that the parent geodatabase can be fully compressed, even with unacknowledged data change messages.

Get Premium EGMP2201 Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test

37 comments · newest first

Walker 11 months ago

Full replica access type seems too heavy for read-only needs.

Abel 11 months ago

I’m leaning towards option A, just replicate the base tables.

Rex 11 months ago

Wait, can you really compress with unacknowledged changes? Sounds risky.

Alida 12 months ago

Totally agree, archiving helps with compression!

Darrin 12 months ago

I think option C is the way to go with archiving.

Basilia 12 months ago

I practiced a similar question on replication types, and I recall that the access type can really affect how data is managed in the child geodatabase.

Hyman 1 year ago

The Archiving option sounds familiar; I feel like it could help with managing unacknowledged messages, but I need to double-check its implications on compression.

Nina 1 year ago

I think the Full replica access type might allow for more flexibility, but I’m not confident it would meet the compression requirement.

Maryanne 1 year ago

I remember something about one-way replication, but I'm not entirely sure if replicating only the base tables is enough for read-only copies.

Kent 1 year ago

This seems straightforward enough. I'd go with replicating just the base tables and using the Full replica access type. That should give me the read-only copies I need at the regional offices without any issues.

Laura 1 year ago

Okay, I think I've got this. The key is using the Archiving option to handle the unacknowledged changes while still allowing for full compression of the parent geodatabase. That sounds like the right approach to me.

Carman 1 year ago

Hmm, I'm a bit confused by the requirements here. I'll need to review the details on one-way parent-to-child replication and how the compression and unacknowledged changes factor in. Might be good to consult the documentation.

German 1 year ago

This sounds like a tricky replication setup, but I think I have a strategy. I'll need to look into the different replica access types and see which one allows for full compression even with unacknowledged changes.

Yolande 2 years ago

The Full replica access type is the way to do it. Imagine if your regional offices were like hungry toddlers, and you're the parent geodatabase. You gotta make sure they get the full meal, not just the scraps, right?

Margarita 2 years ago

↳ replying to Yolande

B: That's true, it's like making sure the hungry toddlers get a full meal from the parent geodatabase.

Edda 2 years ago

↳ replying to Yolande

A: But wouldn't using the Full replica access type ensure that the regional offices get all the data they need?

Ezekiel 2 years ago

↳ replying to Yolande

C: Use the Archiving option

Jackie 2 years ago

↳ replying to Yolande

B: Use the Full replica access type

Ines 2 years ago

↳ replying to Yolande

A: Replicate only the base tables

Queenie 2 years ago

Replicate only the base tables? Psh, that's like only bringing half your luggage on a trip - you're just asking for trouble. Go big or go home, I say. Full replica all the way!

Theodora 2 years ago

↳ replying to Queenie

C: Use the Archiving option

Terina 2 years ago

↳ replying to Queenie

B: Use the Full replica access type

Whitley 2 years ago

↳ replying to Queenie

A: Replicate only the base tables

Beata 2 years ago

I think we should consider using the Archiving option for better data management.

Scarlet 2 years ago

I agree with Mel, using the Full replica access type would be more efficient.

Mel 2 years ago

I disagree, I believe we should use the Full replica access type.

Hana 2 years ago

I'd go with the Archiving option. That way, you can track all the changes that have been made, just in case you need to roll back or review something later on. It's like having a little data diary, you know?

Barrett 2 years ago

↳ replying to Hana

Markus 2 years ago

↳ replying to Hana

C) Use the Archiving option

Lucy 2 years ago

↳ replying to Hana

B) Use the Full replica access type

Leanna 2 years ago

↳ replying to Hana

A) Replicate only the base tables

Nieves 2 years ago

I think we should replicate only the base tables.

Brittni 2 years ago

The Full replica access type is the way to go. It ensures the child geodatabases stay fully in sync, even with unacknowledged changes. Plus, it's like having a backup version of your data - you never know when you might need it!

Mertie 2 years ago

↳ replying to Brittni

Pok 2 years ago

↳ replying to Brittni

C) Use the Archiving option

Marylou 2 years ago

↳ replying to Brittni

B) Use the Full replica access type

Yolando 2 years ago

↳ replying to Brittni

A) Replicate only the base tables

Esri EGMP2201 Exam - Topic 4 Question 4 Discussion