New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Esri EGMP2201 Exam - Topic 4 Question 5 Discussion

Actual exam question for Esri's EGMP2201 exam
Question #: 5
Topic #: 4
[All EGMP2201 Questions]

A user wants to share a frequently edited points feature class as a web layer. The points contain sensitive attributes and will be read-only for online viewers.

The following workflow is applied:

* Points is registered as versioned

* A standard database view is created for points, which hides the sensitive attributes

* The view is published as a web layer from the Default version

As the points feature class is edited throughout the week, edits are not visible in the web layer.

What should the GIS administrator do?

Show Suggested Answer Hide Answer
Suggested Answer: C

The issue arises because the standard database view is based on the base table of the points feature class, which does not include edits made in child versions. To resolve this, the database view must reference a versioned view to reflect changes in the Default version.

1. What Is a Versioned View?

A versioned view is created when a feature class is registered as versioned.

It allows querying and editing versioned data, including edits made in the Default version and child versions.

A standard database view does not account for the Adds and Deletes delta tables used in versioning, which is why edits are not visible.

2. Why Alter the View to Use a Versioned View?

By modifying the standard database view to reference the versioned view, the published web layer will reflect changes made in the Default version, including ongoing edits.

This ensures that updates to the points feature class are visible in the web layer without requiring manual intervention.

3. Why Not Other Options?

Have All Editors Reconcile and Post Points Edits to Default:

While this ensures edits are moved to the Default version, it requires continuous manual reconciliation and posting, which is impractical for a frequently edited dataset.

Rebuild Indexes and Calculate Database Statistics on Points:

These actions improve query performance but do not address the core issue of the standard view not reflecting versioned edits.

Steps to Alter the View:

Identify the versioned view associated with the points feature class. It typically has a name like points_EVW.

Modify the SQL for the existing view to reference the versioned view:

CREATE OR REPLACE VIEW points_web AS

SELECT <fields> FROM points_EVW;

Update the web layer to use the modified view as the data source.

Test the web layer to confirm that edits made to the Default version are now visible.

Reference from Esri Documentation and Learning Resources:

Publishing Data from Views

Conclusion:

To ensure edits made to the points feature class are visible in the web layer, the database view should be altered to reference the versioned view, which accounts for edits in the Default version.


Contribute your Thoughts:

0/2000 characters
Vincenza
3 months ago
Definitely agree with the need for a versioned view here.
upvoted 0 times
...
Kizzy
3 months ago
Wait, why aren't the edits showing up in the web layer? That's odd!
upvoted 0 times
...
Fausto
3 months ago
Rebuilding indexes? That seems like overkill for this issue.
upvoted 0 times
...
Glendora
4 months ago
I think altering the view to a versioned one makes more sense.
upvoted 0 times
...
Melodie
4 months ago
Sounds like they need to reconcile and post those edits to Default.
upvoted 0 times
...
Douglass
4 months ago
Rebuilding indexes sounds like something we did in class, but I don't see how that would help with the visibility of edits in this case. B feels less relevant to me.
upvoted 0 times
...
Leota
4 months ago
I practiced a similar question where we had to deal with versioning issues. I think it was important to reconcile and post edits, which makes me lean towards A again.
upvoted 0 times
...
Reena
4 months ago
I'm not entirely sure, but I think if the view is based on a versioned feature class, it might need to be altered to reflect those changes. C could be a possibility.
upvoted 0 times
...
Claribel
5 months ago
I remember that for versioned data, edits need to be reconciled and posted to the Default version to be visible. So, A seems like the right choice.
upvoted 0 times
...
Buddy
5 months ago
I'm pretty confident option C is the right answer here. Altering the view to use a versioned view as the source should fix the issue and make sure the edits get reflected in the web layer.
upvoted 0 times
...
Ardella
5 months ago
This seems straightforward to me. The edits aren't showing up because the view isn't connected to the versioned data correctly. Option C is definitely the way to go - we just need to update the view to use the versioned source.
upvoted 0 times
...
Theola
5 months ago
I'm a little confused on the versioning part. Does that mean we need to have all the editors reconcile and post their edits to the Default version first? Option A seems like it could work, but I'm not sure.
upvoted 0 times
...
Gerry
5 months ago
Okay, let me think this through. I'm guessing option C is the way to go here - we need to alter the view to use a versioned view as the source, so the edits get pulled through properly.
upvoted 0 times
...
Erick
5 months ago
Hmm, this is a tricky one. I think the key is understanding how the versioning and views are set up. If the edits aren't showing up in the web layer, it sounds like the view isn't properly connected to the versioned data.
upvoted 0 times
...
Glenna
1 year ago
Ah, the joys of working with GIS data. I'd say C is the way to go, but I can't help but chuckle at the thought of the user trying to pull a fast one on the online viewers.
upvoted 0 times
Tracey
1 year ago
User 3: User Comment: Ah, the joys of working with GIS data. I'd say C is the way to go, but I can't help but chuckle at the thought of the user trying to pull a fast one on the online viewers.
upvoted 0 times
...
William
1 year ago
User 2: A) Have all editors reconcile and post points edits to Default
upvoted 0 times
...
Geoffrey
1 year ago
User 1: C) Alter the view to use a versioned view as the source
upvoted 0 times
...
...
Cecil
1 year ago
But wouldn't altering the view to use a versioned view as the source also solve the issue?
upvoted 0 times
...
Regenia
1 year ago
Haha, I feel like the user wants to have their cake and eat it too. They want to share the data, but keep the sensitive bits hidden. I'd go with C as well.
upvoted 0 times
Celia
1 year ago
C) Alter the view to use a versioned view as the source
upvoted 0 times
...
Ammie
1 year ago
B) Rebuild indexes and calculate database statistics on points
upvoted 0 times
...
Bobbie
1 year ago
A) Have all editors reconcile and post points edits to Default
upvoted 0 times
...
...
Nada
1 year ago
I agree, having all editors reconcile and post points edits to Default seems like the best solution.
upvoted 0 times
...
Beckie
1 year ago
I think the GIS administrator should choose option A.
upvoted 0 times
...
Kirby
1 year ago
Wow, this is a tricky one. I'm torn between B and C, but I think C might be the best solution to keep the sensitive attributes hidden.
upvoted 0 times
Jerrod
1 year ago
You make a good point, C does seem like the best solution for this scenario.
upvoted 0 times
...
Joni
1 year ago
That's true, but altering the view to use a versioned view as the source might be more efficient in the long run.
upvoted 0 times
...
Bulah
1 year ago
But wouldn't having all editors reconcile and post points edits to Default also update the web layer?
upvoted 0 times
...
Tien
1 year ago
I think C is the way to go, it will keep the sensitive attributes hidden.
upvoted 0 times
...
...
Deandrea
1 year ago
I think option C is the way to go. Using a versioned view as the source will ensure that the edits are visible in the web layer.
upvoted 0 times
Nelida
1 year ago
User 4: Definitely, altering the view to use a versioned view is the way to go.
upvoted 0 times
...
Nu
1 year ago
User 3: It's important to have the edits visible for online viewers.
upvoted 0 times
...
Anabel
1 year ago
User 2: Agreed, using a versioned view will keep the web layer up to date.
upvoted 0 times
...
Sunny
1 year ago
User 1: Option C is the best choice.
upvoted 0 times
...
...

Save Cancel