SAP Certified Application Associate - SAP Master Data Governance - C-MDG-90 Free Exam Questions

A. Use a separate change request type per material group and use a context-based adaptation (CBA) to control the user determination depending on the chosen material group and the current processor.

B. Use the same change request type and control the material group maintenance via authorizations and dynamic user agent determination.

C. Use the same change request type and use a custom feeder class to control the Material Group field in the user interface depending on the processor's authorizations.

D. Use a separate change request type per material group and implement validation checks, that only the dedicated material groups can be maintained in each change request type.

A. Pre-configured data models, user interface configurations, workflows, and data distribution are available

B. Tools allow you to define new objects and related processes in order to govern your own master data domains

C. You can extend existing models with your own master data attributes, change the UI configuration to the needs of your user, and customize the workflow and distribution to define your specific governance processes

A. Data in process is stored in a separated repository and will be transferred to operational database after final approval

B. Roles, responsibilities, and task authority (for example, create, change, and approve requests)

C. Provides the possibility to extend the process by adding business logic and thereby bringing in data quality

D. Flexible enough to respect the distributed responsibilities existing in a company across various business units

E. Linear or distributed and workflow based

F. Integrated object models can result in proven data models for operational and financial master data

G. Can be adapted and tailored based on customer needs

A. Role-derivations and role-transports

B. Personalization's and structural authorizations (for Organizational management)

C. Trace and deployment tools

D. User assignments and menu items

E. Authorization profiles (PFCG roles)

F. SAP MDG features available in the Authorization Management area.

A. They are NOT changeable in a mass change.

B. They are NOT displayed in the UI.

C. They can be replicated and exported.

D. They are temporarily removed from the data model.

A. Log on using the data provided in the MDG User Details table.

B. Choose b) Start SAP Logon. The system ZME should be in the list of Systems

C. Log on to the MDG system a) ZME Client 800 via SAP Logon.

D. Mark c) Public and choose Finish.

E. In the Windows Security dialog box, enter the data provided in the User Details table

A. Data models

B. Applicable enhancement

C. Data replication

D. Processes

E. User interfaces

A. Configure data replication to send master data from the SAP MDG hub to connected systems and optionally receive key mapping information

B. Define a process to provide customizing and non-governed reference data to the SAP MDG hub

C. Configure the workflow to distribute the data from SAP MDG to the system landscape

D. Configure the Uls so that systems in the landscape have the same view on the master data

A. Purchasing organization

B. Company code data

C. Vender master data

D. General data

A. Active data sets are removed from the SAP MDG staging area after change request activation.

B. Tables defined in the SAP MDG data model store the active data.

C. Active data sets are held in the SAP MDG staging area also after change request activation.

D. Existing ERP structures are used.

A. Change Requests (TA MDGIMG)

B. SOA Services (TA SOAMANAGER)

C. Business Functions (TA SFW5)

D. Services (TA SICF)

A. Loose inter locking locks only the next child element in the same change request.

B. Strict inter locking locks only the element assigned to the hierarchy in the same change request.

C. Strict inter locking locks the whole hierarchy in the same change request.

D. Loose inter locking locks only the next parent element in the hierarchy in the same change request.

A. Enhance: functionality Be able to enhance MDG functionality based on predefined content (for example, plant or sales data) or customer-specific extensions

B. Reuse Standard Content: Reuse existing data structures and functionality of SAP Business Suite

C. None of the above.

D. Reuse: the existing data structures and functionality of SAP Business Suite

A. UI consisting of all data (central data as well as organizational data) of a BP, customer, or supplier.
Separate pages for BP data,
central customer or supplier data, as well as organizational data.

B. UI consisting of all data (central data as well as organizational data) of a customer or a supplier. Look and feel is very similar to ERP-Customer or ERP-Vendor UI in ERP standard.

C. UI for business users with no or limited MDG knowledge for requesting the creation of a BP, customer, or supplier offering a limited number of fields identifying the BP. Implemented as a Fiori application on all devices.

D. UI for Sales, Purchasing, and Financial specialists consisting of organizational data for one organizational unit.

E. UI for business users with no or limited MDG knowledge for requesting the creation of a customer or supplier offering a limited number of fields identifying the BP.