Free IBM C2090-420 Exam Dumps Questions & Answers

You built a new data addition called "Xaddition?which has "one-to-many" relationships to the existing ContractComponent" data entity for a client. The relationship between
"ContractComponent" and "Xaddition" is parent-to-child. The client wants the InfoSphere MDM Server to be able to handle the data elements residing in the Xaddition?by invoking the out-of-thebox Contract related services such as addContract? And getContract? Which solution do you propose to the client that will satisfy the requirement?

• A.Build an event behavior extension at the pre-transaction level.
• B.Build an event behavior extension at the post-transaction level.
• C.Build an event behavior extension at the post-action level.
• D.Build an event behavior extension at the pre-action level.

You use the InfoSphere MDM Server Workbench to define a new code table named
"CreaditApplicarionStatus Type" with database table "cdcreditappstatustp" containing two fields.
The two fields are "appl_status_tp_cd" and "appl_status_name" which are the type code and value respectively.
What will constitute the primary key of the database table "cdcreditappstatustp"?

• A.appl_status_tp_cd
• B.lang_tp_cd and appl_status_name
• C.appl_status_tp_cd and appl_status_name
• D.lang_tp_cd and appl_status_tp_cd

You are required to store the history of any errors generated for reporting at a later time.
Which statement is correct?

• A.Write a custom business rule to save error data in the custom history tables.
• B.Generate a report on sample error tables.
• C.Enable transactions in the Transaction Audit Information Log(TAIL).
• D.History is configured during installation; so this will be implemented.

A granular composite Java proxy, CompositePartAddressTxnBP.java, is created to process (search, inquiry, persist) partyAddress records In InfoSphere MDM Server Application.
Which PartyInquiryLevel should be chosen in this composite transaction that meets both your functional and your performance requirements?

• A.Level 2 -- returns level 1 data plus all party relationship data.
• B.Level 0 -- returns Party data only including name, identifications, and party data.
• C.Level 3 -- returns level 2 data plus all party bank account, party charge card, and income source data
• D.Level 1 -- returns level 0 data plus all party addresses, contact methods.

The addPerson and updatePerson services are taking a long time to execute. When you examine the log files, you notice that the Match Rule is running over 10,000 times each request but a Suspect is only found 0.1% of the time.
What would be the cause of the performance issue?

• A.The party match rule is comparing too many attributes.
• B.The suspect duplicate party search rule is finding too many parties.
• C.The C suspect action rule is not adding suspects to the database.
• D.The database contains many similar customer records.