The WebSphere Commerce Payments architecture includes a Payment Servlet and a Payment Engine. The Payment Engine is the ONLY component that：（）

A . drop and re-create the WebSphere Commerce Payments database. B . stop and start the Payment Engine. C . configure WebSphere Commerce Server communication with WebSphere Commerce Payments Server. D . specify what type of Database software will be used for the WebSphere Commerce Payments database.

A . Auctions B . Database replication C . E-mail notifications D . Discounts E . Marketing campaig

A . The installation log files B . The Commerce tools can be launched and logged into properly C . User ’wpadmin’ has been created D . The structure of the installation directory E . The WebSphere Application Server database schema

A . Open/Close B . Change Profile C . Change Flow D . Change Name E . Change Tax

A . Account Representative B . Customer Service Representative C . Logistics Manager D . Customer Service Supervisor

A . Merchant Administrator B . Payment Administrator C . Payment Processor D . Supervisor E . Clerk

A . Lotus QuickPlace B . Lotus SameTime C . WebSphere Business Integrator D . DB2 E . WebSphere Application Server

A . The site does not need a cassette， unless the site requires real-time credit card validation. B . A cassette is a piece of plug-in software that provides support for a specific payment system. C . The CyberCash cassette is installed by default， with the installation of WebSphere Commerce Payments. D . Third party companies can create custom cassettes that will work with WebSphere Commerce Payments. E . Cassettes convert the merchant payment request to the payment protocol of the local payment system.

A . Create tax codes. Create sales tax categories. Enter rates for each combination of tax code and category. Create jurisdictions. Assign the jurisdictions to the codes. Assign tax categories to the SKUs. B . Create tax categories. Create sales tax codes. Enter rates for each combination of tax category and code. Create jurisdictions. Assign the jurisdictions to the categories. Assign tax codes to the SKUs. C . Create jurisdictions. Create sales tax codes. Create shipping tax codes. Create tax categories. Define tax category display names. Define tax rates. Assign categories to codes. D . Create jurisdictions. Create tax codes. Enter rates for each combination of tax code and jurisdiction. Create sales tax categories. Assign the categories to the codes. Assign tax categories to the SKUs.

A . DataSource B . Virtual Hosts C . Server Group D . The selected JDBC Driver E . Remote Servlet Redirector

A . Address line 1 B . City C . Last name D . Last visit date E . Marital status F . Previously purchased SKU

A . WebSphere Commerce Configuration Manager B . WebSphere Application Server Administrative Console C . WebSphere Commerce Administration Console D . WebSphere Commerce Accelerator E . Command line

A . There is a section for downloading current documentation. B . There is a chat section where you can talk with a support representative. C . The latest fixpacks can be downloaded. D . The most current IBM Redbooks are displayed on the homepage. E . There is a direct link to the Product Introduction Center website.

A . Open and close a store B . List distributors for the hub C . Broadcast e-mail to customers of the hub D . Manage campaigns E . Create new users or change user attribute

A . this is a multi-node installation B . this is a single node installation. C . each hardware and software component is a single point of failure. D . this is an example of load balancing.

A . XML Transformer B . Message Mapper C . Commerce Studio D . DTD Generator E . MQSeries Integrator

A . Advertise Discount B . Let the system suggest products on auction C . Cross-sell products based on contents of the customer’s wish list D . Up-sell products based on the contents of the current page

A . Customized price list B . Display customization C . Invoice format D . Order approval E . Predefined purchase orders F . Return charge

A . The web server was not started B . The Payments Engine was not started C . The WebSphere Commerce Payments instance was not started D . The WebSphere Commerce application server was not started E . The Configuration Manager service was not started

A . Available to Promise B . Collaborative workspaces C . Contract-based purchasing D . Rule-based discounts E . Request for Quote

A . Command Line B . WebSphere Commerce Configuration Manager C . WebSphere Commerce Administration Console D . WebSphere Commerce Accelerator

A . Member subsystem B . Analytics subsystem C . Merchandising subsystem D . Catalog subsystem E . Organization subsystem

A . <WAS_installdir>\logs\log.txt  B . <WC_installdir>\logs\install_date_time.log  C . <WAS_installdir>\logs\<WC_instance_name>\SystemOut.log  D . <WC_installdir>\instances\<instance_name>\xml\<instance_name>.xml  E . <WAS_installdir>\logs\serverStatus.log

A . Consumer direct store model B . Advanced B2B direct store model C . Demand chain store model D . Advanced Demand chain store model E . Marketplace hub store model