Oracle 1Z0-510 Online Practice Questions and Exam Preparation

Oracle 1Z0-510 Online Questions & Answers

• Question 61:

  In a multisite environment, what is the default sharing behavior of user profiles?

  A. They are shared across all the sites.
  B. They are not shared and hence are separate across the sites.
  C. They can be configured into groups that specify the sharing behavior.
  D. There is no default behavior. It needs to be custom designed and implemented.
  A. They are shared across all the sites.

  ---

  User profiles (and therefore logins) are always shared across all sites in the application.

  Note: In the simplest case, these sites may share only user profiles, so a customer registered on one site is also registered on the other. In more complex implementations, the sites may share shopping carts, so a customer can include items from both sites in a single order. The bargain-brand site might also include upsell recommendations for (and links to) items on the luxury brand site, or the sites might share gift lists.

• Question 62:

  What is the resulting outcome when the statements below are executed without a transaction?

  repositoryItem.setPropertyValue("name", "John"); repositoryItem.setPropertyValue("lastName", "Doe")

  A. For each setProperty value, ATG begins a JTA transaction, calls setPropertyValue, and commits the JTA transaction. At this point, SQL is issued and the changes are committed.
  B. Before the 1st setPropertyValue is executed, a JTA transaction begins. After the 2nd setProperty Value is called, ATG commits the JTA transaction. At this point, SQL is issued and the changes are committed.
  C. ATG throws an error as multiple setPropertyValue have to be executed within a transaction.
  D. Before the 1st setPropertyValue is executed, a JTA transaction begins. The SQL is issued when you call updateItem.
  E. All setPropertyValue method calls must be wrapped in a JTA Transaction.
  A. For each setProperty value, ATG begins a JTA transaction, calls setPropertyValue, and commits the JTA transaction. At this point, SQL is issued and the changes are committed.

• Question 63:

  The default Task for a merchandiser in ATG workflow after production deployment is complete is____________.

  A. Verify Production Deployment
  B. Approve Production Deployment
  C. Close Project
  D. Revert Deployment
  E. Commit updates
  A. Verify Production Deployment

  ---

  The default Manage Commerce Assets workflow includes the following tasks:

  Author Content Review Approve for Production Deployment Wait for Production Deployment Completion Verify Production Deployment

• Question 64:

  How many current and saved orders does ATG allow a user profile to have?

  A. ATG allows one current order and one saved order per user profile.
  B. ATG allows one current order and a collection of saved orders per user profile.
  C. ATG allows multiple current orders and a collection of saved orders per user profile.
  D. Only one order can exist for a Give user profile in ATG. There is no support for saved orders.
  B. ATG allows one current order and a collection of saved orders per user profile.

  ---

  Note: loadShoppingCarts

  public void loadShoppingCarts(RepositoryItem pProfile,

  OrderHolder pShoppingCart)

  throws CommerceException

  Parameters:

  pProfile - the user profile

  pShoppingCart - the OrderHolder component for this user Throws:

  CommerceException - is any errors occur while loading the shopping carts

  This method finds all the shopping carts for the user and places them into the session-scope OrderHolder component. "Shopping Carts" are defined to be orders whose state is INCOMPLETE. The orders are sorted by last activity date, and

  the last order touched is made the current order. This method will optionally merge the current shopping cart for the session (from the OrderHolder.current property) with the first persistent order loaded from the database. This functionality is

  toggeled through the mergeOrders property of this form handler. NOTE: This method used to acquire a transaction lock, but we've found deadlock issues and have decided to remove the locks. See bug 146012. This method now performs its

  actions without a lock.

• Question 65:

  What does the following item-descriptor demonstrate?

  "enumerated">

  type = "string">

  A. Transient properties
  B. Item descriptor inheritance
  C. On-to-many relationship
  D. One-to-one relationship
  D. One-to-one relationship

  ---

  Auxiliary Tables

  You can handle some data relationships using auxiliary attribute tables. For example, you could store users and their addresses in two related database tables, as described in the following piece of an XML repository definition:

  Each user has a single address. For the purposes of this example, the user information is stored in a separate table from the user's address information.

  Note: Primary and Auxiliary Tables

  Each item descriptor must have one and only one primary table. The primary table is specified using the type="primary" XML attribute in a

  tag. The primary table must define a column or columns that store the repository ID. This

  column is specified using the id-column-names attribute. For example:

  properties...

• Question 66:

  Identify three methods that are supported by the Out of the Box Form handler RepositoryFormHandler.

  A. RepositoryFormHandler does not provide any methods.
  B. Create
  C. Delete
  D. Select
  E. Update
  F. Select All
  B. Create
  C. Delete
  E. Update

  ---

  RepositoryFormHandler Submit Operations

  The RepositoryFormHandler supports the following operations for form submission:

  *

  create

  Creates a repository item based on the value set in the form and adds it to the repository. If the repositoryId property is specified in the form, the new item is created with the given repository ID; otherwise, an auto-generated ID is used.

  *

  delete

  Deletes from the repository the item specified by repositoryId.

  *

  update

  Updates the item described by repositoryId from the form values.

  Note: RepositoryFormHandler

  Web application forms are commonly used to view and update database data. The atg.repository.servlet.RepositoryFormHandler class provides methods and properties for working with repository items. You can use a component of this class to add, update, and delete repository items that use the same item descriptor. A RepositoryFormHandler can be used with any repository type: HTML, XML, LDAP, and SQL.

• Question 67:

  Identify two functions of the Nucleus.

  A. Nucleus resolves component names to components.
  B. Nucleus provides commerce-specific functionality such as catalog and cart.
  C. Nucleus creates and initializes components.
  D. Nucleus provides application logging capability such as debug, warning, info, error, and trace
  A. Nucleus resolves component names to components.
  C. Nucleus creates and initializes components.

  ---

  A: Nucleus performs one basic operation: resolving component names. Given the name of a component, Nucleus does its best to find or create that component and return it.

  C: Name resolution is not a difficult task. Nucleus shows its real power by creating components and hooking them up to other components automatically. This function is invoked when Nucleus is asked to resolve a name of a component that does not yet exist. In this case, Nucleus looks for the appropriate configuration file that describes how to create that component and any other components that it requires.

  Note: Nucleus is the Dynamo Application Framework's component model for building applications from JavaBeans. Nucleus lets you assemble applications through simple configuration files that specify what components are used by the application, what parameters are used to initialize those components, and how those components hook up to each other. The ATG Control Center Components window provides a handy way to create, modify, and manage Nucleus components.

  Nucleus by itself provides no application-specific functions. The JavaBean components implement all of an application's functionality. Nucleus is the mechanism that gives those components a place to live, and a way for those components to find each other.

• Question 68:

  What do you need to do to disable ATG's Out-of-the-Box behavior of persisting order change?

  A. Set /atg/commerce/order/OrderTools.persistOrders = false
  B. Set/atg/commerce/order/OrderManager.persistOrders=false
  C. Set /atg/commerce/ShoppingCart.persistOrders = false
  D. ATG does not allow you to modify this behavior.
  C. Set /atg/commerce/ShoppingCart.persistOrders = false

  ---

  Understanding the ShoppingCart Component The ShoppingCart component is responsible for storing and managing a customer's shopping carts. It maintains the customer's current shopping cart that is used during the purchase process, and it stores any other shopping carts that have been persisted by that customer. These shopping carts are represented as atg.commerce.order.Order objects in the ATG Commerce object model, and represented as order items in the Order Repository.

• Question 69:

  What is the likely outcome when a product's end date is set in the past?

  A. ATG automatically stops showing the product when category.ChildProducts is invoked.
  B. Developer of the site has to have a rule to check the date and decide if the product can be displayed.
  C. ATG deletes the product and hence is never shown on the site.
  D. END date is a display only field and has no impact on the product's visibility.
  A. ATG automatically stops showing the product when category.ChildProducts is invoked.

  ---

  Note:

  * End date

  Date the product is no longer available, if a collection filter is implemented to use this property.

• Question 70:

  Each of the stock levels has a threshold associated with it. When a stork level reaches the threshold, what is the default behavior?

  A. An event is generated.
  B. ATG stops any customer from checking out the SKU.
  C. ATG stops showing the SKU as orderable.
  D. Thresholds are not used in ATG. They are legacy code for backward compatibility.
  A. An event is generated.

  ---

  Every inventory item in the repository must have a Long property attached to it that represents the item's stock level threshold. If the stocklevelfalls below this value, an event is triggered.