Question1:

Which tools provided by Informatica Intelligent Cloud that can satisfy your master datmanagement business needs?

 Answer:

•Projects

•Assets

•Explore page

Question2:

What is Business360 ?

 Answer:

This tool is used to do all development and configuration work related to IDMC MDM. It contains predefined assets that all business applications can use. You can create folders within this project and add custom assets to them.

Question3:

What is Customer360?

 Answer:

It is having predefined data models needed for Customer master MDM implementations, it contains predefined assets specific to MDM - Customer 360 SaaS. You can see this project only if you have the Customer 360 license. You can create folders within this project and add custom assets to them.

Question4:

What is MultidomainMDM ?

 Answer:

It is blank box in Informatica MDM where we can define any data models from scratch. It contains predefined assets specific to Multidomain MDM SaaS. You can see this project only if you have the Multidomain MDM license. You can create folders within this project and add custom assets to them.

Question5:

Define Reference360

 Answer:

It contains lookup kind of datasets which will not change frequently like Gender info, Country info etc. it contains predefined reference data assets that you can use in any business application. You Can create folders within this project and add custom reference data assets to them.

Question6:

Define Product360

 Answer:

It contains data model needed to implement Product master in MDM. It contains predefined assets specific to MDM - Product 360 SaaS. you can see this project only if you have the Product 360 license. You can create folders within this project and add custom assets to them.

Question7:

Define Supplier360

 Answer:

It contains data model needed for Supplier master MDM implementations. It contains predefined assets specific to MDM - Supplier 360 SaaS. You can see this project only if you have the Supplier 360 license. You can create folders within this project and add custom assets to them

Question8:

How we define Assets In Business 360 Console?

Answer:

In Business 360 Console, the core assets are business entities, source systems, business applications, pages, and components. You can create rule specification assets in Data Quality for operations such as data standardization, data cleansing, and data validation. Also, you can create process assets in Application Integration to automate business processes such as file import, task triggers, and match and merge. Additionally, Business 360 Console includes predefined assets, such as business entities, user interface components, and pages, to help you get started with using business applications.

You can't move, copy, or delete any asset. Create the assets you need to satisfy your business needs. You can use the assets in multiple projects. All assets must be part of at least one project. If you create an asset without specifying a project, the asset is created in the Default project.

Question9:

The GET request contains which parameters with description ?

 Answer:

businessEntity - Internal ID of the business entity for which you want to retrieve the source record.

sourceSystem- Internal ID of the source system to which the record belongs.

sourcePKey- The primary key of the source record.

_resolveCrosswalk- Indicates whether to standardize picklist values based on the source system configuration.

Set to true to standardize the picklist values. When you specify this parameter, you must set

the sourceSystem parameter. Default is false.

For more information about standardizing picklist values, see Define Source Systems.

Question10:

The GET response includes the following _meta parameters with which description?

 Answer:

Parameter                               Type               Description

businessId                               String              Unique identifier of the business entity record.

Id                                               String              Unique identifier of the business entity record. Do not use.

businessEntity                       String              Internal ID of the business entity from which you retrieved the master record. 

created                              String              Name of the person that created the record.    

creationDate                        String              Date when the record was created.

updated                             String               Name of the user who last updated the record.

lastUpdateDate                   String                Date when the master record was last updated.

sourceLastUpdatedDate   String            ate when the source record was last updated.

States                                     Sting                      The different statuses of the active source record.

                                                                         Source records can have the following statuses:

                                                                         -base. The current status of the source record. The base value is ACTIVE.

                                                                         -consolidation. The status of the source record in the match and merge process.

                                                                       o -MATCH_DIRTY. Indicates that the source record is a new record

                                                                       that didn't undergo the match process.

                                                                      o -MATCH_INDEXED. Indicates that the record is indexed and can be

                                                                         matched. During indexing, match candidates are generated for use in

                                                                         the match process.

                                                                     o -MATCHED. Indicates that the record is matched and ready to be

                                                                        merged.

                                                                     o -CONSOLIDATED. Indicates that the source record is merged

                                                                       determined to be unique, and represents the best version of the truth.

                                                                        -search Index. Indicates that the record is in a SEARCH_DIRTY state and is not

                                                                       searchable. In the current release, source records are not searchable.

                                                                       -validation. Indicates the validation status of the record.

                                                                       o -PENDING. Indicates that the record is not yet validated.

                                                                       o -PASSED. Indicates that the record is validated and has no errors.

                                                                       o -FAILED. Indicates that the record is validated and has validation

                                                                       and data quality errors.

Question11:

Example of GET API?

 Answer:

You might use the following request to retrieve the source record for the Person business entity

associated with the c360.default. system source system and the primary key 611d13e9e6dbd16ffa69a143:

GET /business-entity/public/api/v1/entity-

xref/c360.person/c360.default.system&_resolveCrosswalk=true/611d13e9e6dbd1

6ffa69a143 HTTP/1.1

IDS-SESSION-ID: XXXXXXXXXXXXXXXXXXXXXX

Content-Type: application/json

Question12:

Explain list of dependent privileges for record-level privileges?

 Answer:

Type of                                      Privilege                                   Requires

Privilege

Attribute-                                Create                                        Create or update to records.

Level

Attribute-                                 Read or update                        Read or update to records.

Level

Attribute-                                  Delete                                        Update to records.

Level

Attribute-                                Read or update to child           Read or update to parent field groups and to records.

Level                                         fields or nested field groups.

Question13:

How can we define relationships to define and visualize relationships between business entity records in Supplier360 ?

 Answer:

Supplier to Contact- Represents relationship between Supplier and Contact business entities where a contact

belongs to a supplier. Sub-Supplier- Represents relationships between two supplier business entities where one supplier is a

parent to another supplier from a different organization. Subsidiary- Represents relationship between two supplier business entities where one supplier is a parent to another supplier in the same organization. Supplier to Contact Hier- Represents relationship between the contact associated with the supplier. This relationship is used in the supplier hierarchy. Supplier to Supplier Hier- Represents relationship between a supplier associated with another supplier. This

relationships is used in the supplier hierarchy.

 Question14:

Define rule specifications for Supplier 360 SaaS?

 Answer:

Supplier 360 SaaS uses predefined rule specifications, such as DUNS and SSN validation that validate DUNS numbers and SSNs of supplier and contact records in the predefined business entities. The Dun and Bradstreet number or DUNS number is a unique identifier assigned to businesses across the globe. Similarly, the Social Security Number (SSN) is a unique identifier assigned to the citizens of the United States of America.

Question15:

How to Monitor MDM SaaS jobs?

 Answer:

When you monitor MDM SaaS jobs, you can view a summary of jobs, and view all job instances and job schedules. You can also view key metrics for each job type. You can monitor the data that each job processes or compare the metrics of various jobs. For example, you can compare the number of records processed by two or more ingress jobs to determine the number of records that were imported from source systems.

Contact:+91-98219-31210

Know about us: https://youtu.be/6MHU33tSkmM