Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Esri EAEP2201 Exam - Topic 1 Question 8 Discussion

Actual exam question for Esri's EAEP2201 exam
Question #: 8
Topic #: 1
[All EAEP2201 Questions]

A GIS administrator publishes a feature service that references user-managed data. The administrator wants users to add new features. Users should not make changes to attributes of existing features or delete features.

Which feature service operations should be set?

Show Suggested Answer Hide Answer
Suggested Answer: B

To allow users to add new features without the ability to modify or delete existing ones, the feature service should have the 'Create' and 'Query' operations enabled. The 'Create' operation permits users to add new features, while the 'Query' operation allows them to view existing features. By not enabling the 'Update' and 'Delete' operations, users are restricted from making changes to or removing existing features. This configuration is ideal for workflows where data integrity is crucial, and only the addition of new data is permitted.

Enabling 'Update and sync' (Option A) would allow users to modify existing features and synchronize changes, which is not desired in this scenario. 'Extract and create' (Option C) is not a standard combination of operations for controlling editing permissions in feature services.

Reference Source: ArcGIS Server documentation on editor permissions for feature services


Contribute your Thoughts:

0/2000 characters
Nathalie
12 days ago
Option C doesn’t fit. Extracting isn’t necessary for this task.
upvoted 0 times
...
Mari
17 days ago
Right! We want to avoid any changes to current attributes.
upvoted 0 times
...
Matilda
22 days ago
Agreed! Create and query makes sense. No edits to existing data.
upvoted 0 times
...
Loreen
28 days ago
I’m not sure about that, what if they need to edit something later?
upvoted 0 times
...
Flo
1 month ago
Definitely B! Keeps it simple and effective.
upvoted 0 times
...
Terina
1 month ago
Wait, can users really only add new features? Sounds limiting.
upvoted 0 times
...
Laurel
2 months ago
I agree, no need for updates on existing features.
upvoted 0 times
...
Selma
2 months ago
B) Create and query is the way to go!
upvoted 0 times
...
Gertude
2 months ago
Haha, I bet the GIS admin is just hoping the users don't accidentally delete everything. B) is definitely the safest option.
upvoted 0 times
...
Matt
2 months ago
Hmm, I'm not sure. Wouldn't C) Extract and create also work since it allows creating new features?
upvoted 0 times
...
Floyd
3 months ago
I agree, allowing users to add new features while preventing them from modifying existing ones sounds like the perfect use case for B.
upvoted 0 times
...
Sharika
3 months ago
B) Create and query seems like the right choice here.
upvoted 0 times
...
Virgilio
3 months ago
I thought about C) Extract and create, but that doesn't seem to fit the requirement of not allowing changes to existing features.
upvoted 0 times
...
Penney
3 months ago
I feel like the answer is definitely B) Create and query, but I’m a bit confused about the role of the other options.
upvoted 0 times
...
Dorinda
3 months ago
I'm not entirely sure, but I remember something about limiting operations in a similar practice question. Maybe A) Update and sync could be relevant?
upvoted 0 times
...
German
3 months ago
Hmm, I'm not totally sure. I'm leaning towards B, but I want to double-check that users really can't do any updates or deletions. I don't want to miss something important.
upvoted 0 times
...
Elke
4 months ago
I'm pretty confident this is option B. The question is specifically asking about the feature service operations, and create and query seems to match the requirements the best.
upvoted 0 times
...
Daisy
4 months ago
I'm a little confused on the difference between the options. Can users update existing features at all, or is it just creating new ones that's allowed? I'll need to review the details more closely.
upvoted 0 times
...
Avery
4 months ago
I think the answer might be B) Create and query since users need to add new features but not modify existing ones.
upvoted 0 times
...
Lucy
4 months ago
I think option B is the best choice. Users need to create new features.
upvoted 0 times
...
Mignon
5 months ago
Definitely B. Clear and straightforward for users to follow.
upvoted 0 times
...
Carmen
5 months ago
I feel like option A could lead to mistakes. Users might accidentally update.
upvoted 0 times
...
Romana
5 months ago
Okay, I think I've got this. The key is that users should only be able to add new features, not modify or delete existing ones. So I'd go with option B - create and query.
upvoted 0 times
...
Emily
5 months ago
Hmm, this seems like a tricky one. I'll need to think carefully about the different feature service operations and how they apply to the requirements.
upvoted 0 times
Adela
2 days ago
But what about updating? Isn’t that important too?
upvoted 0 times
...
Margart
7 days ago
Yeah, I agree. Users need to add new features only.
upvoted 0 times
...
Derick
4 months ago
I think option B is the best choice. Create and query sounds right.
upvoted 0 times
...
...

Save Cancel