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

XML I10-003 Exam - Topic 4 Question 14 Discussion

Actual exam question for XML's I10-003 exam
Question #: 14
Topic #: 4
[All I10-003 Questions]

A certain store engages in Internet commerce, managing customer information via XMLDB. Customers register as a user through a webpage, and are allowed to view their own information so they can edit their information themselves through a webpage interface. The store's Web application saves the customer information in an XMLDB, and retrieves data from the XMLDB as necessary. The XML data including customer information is as shown in [CUSTOMER.xml] referenced in a separate window.

The XMLDB account when the Web application connects to the XMLDB is WEBAPP.

A person at the store is in charge of processing payments (access to all registered customer information), and this person's XMLDB account is COUNTER.

A person at the store is in charge of product shipments (access to all registered customer information except for payment information ("payment element")), and this person's XMLDB account is SHIPPER.

Do not consider XMLDB accounts other than those noted above.

Each account authorization in the XMLDB is presently configured as follows: The WEBAPP account has permission to update and view [CUSTOMER xml]

Other accounts have permission to view [CUSTOMER.xml]

Which is the most appropriate method in this situation regarding XMLDB account authorizations'?

Assume that this XMLDB has a view creation function (function to show only certain XML data in response to a certain query)

Show Suggested Answer Hide Answer
Suggested Answer: D

Contribute your Thoughts:

0/2000 characters
Willie
4 months ago
Isn't encrypting everything a bit overkill?
upvoted 0 times
...
Silvana
4 months ago
Definitely agree with option D, keeps things secure!
upvoted 0 times
...
Belen
4 months ago
Wait, why would SHIPPER need to be blocked from CUSTOMER.xml?
upvoted 0 times
...
Phuong
5 months ago
I think option B makes the most sense here.
upvoted 0 times
...
Nobuko
5 months ago
Sounds like a solid setup for data privacy!
upvoted 0 times
...
Jerry
5 months ago
I thought we covered something about encrypting data, but I’m confused if that applies to all user elements or just payment info.
upvoted 0 times
...
Diego
5 months ago
I feel like creating views could be a good approach. Option D seems to align with what we practiced about limiting access.
upvoted 0 times
...
Pearly
5 months ago
I'm not entirely sure, but I think option B makes sense since only the COUNTER account should access payment info, right?
upvoted 0 times
...
Gail
5 months ago
I remember we discussed the importance of restricting access to sensitive information, especially payment details.
upvoted 0 times
...
Clement
5 months ago
I'm a little unsure about this one. The options seem to be describing different functionalities, and I'm not sure which one is the correct answer. I'll have to re-read the question and options carefully before making a decision.
upvoted 0 times
...
Frankie
5 months ago
I'm a little confused here. Is the Custom Script Extension the right choice, or should I be looking at the managed identity options? I'll need to review the details carefully before making a decision.
upvoted 0 times
...

Save Cancel