ABC Corp. uses Orade E-Business Suite Release 12 and wants to design an Order Status Web inquiry screen to make order statuses visible to its customers online. Hon can ABC Corp. ensure that…

Question

Options

• Aby securing attributes for each customer
• Bby excluding attributes for individual customers
• Cby assigning a separate attribute value for INTERBNAL_CONTACT_ID
• Dby assigning the same attribute value for CUSTOMER_CONTACT_ID

• A
  83% (24)
• B
  3% (1)
• C
  3% (1)
• D
  10% (3)

Explanation

Securing attributes in Oracle E-Business Suite is the mechanism that acts as a row-level filter - when a customer logs into the Order Status Web inquiry, the system checks their secured attribute (such as CUSTOMER_CONTACT_ID) and returns only records matching that value, ensuring data isolation between customers.

Why the distractors are wrong:

• B - Excluding attributes hides columns/fields, not rows of data; it would remove information from view for everyone, not restrict which orders each customer sees.
• C - INTERNAL_CONTACT_ID is intended for internal employees/staff, not external customers, so securing on this attribute would not properly isolate customer-facing order visibility.
• D - Assigning the same attribute value to all customers would do the opposite of the goal: every customer would see every other customer's orders, creating a data privacy breach.

Memory tip: Think of securing attributes as a personalized filter gate - like a lock keyed to each customer's ID. Only option A "locks" each customer to their own data. Any option that references "same value" (D) means shared access, and anything referencing internal IDs (C) or column removal (B) misses the row-level security concept entirely.

No community discussion yet for this question.