Free C_MDG_90 – SAP Certified Application Associate - SAP Master Data Governance Practice Test Question

Select all that apply, then click Submit answer.

• ○

  Simple check and selection lists.
  

• ○

  Integration with content provided by SAP Data Services.
  

• ○

  Automatically adding Tax Jurisdiction Code re-using existing interfaces/providers.
  

• ○

  Address enrichment
  
  
  

Select all that apply, then click Submit answer.

• ○

  CHECK_CREQUEST_START
  

• ○

  CHECK_CREQUEST (once for each entity type of the changed master data in the change request)
  

• ○

  CHECK_CREUQEST_FINAL
  

• ○

  None of the above.
  
  
  

Select all that apply, then click Submit answer.

• ○

  Configure the required BAdl call in Business Rule Framework plus.
  

• ○

  Define the enrichment spots.
  

• ○

  Define the derivation rules.
  

• ○

  Adapt the relevant check and validation method.
  
  
  

Select all that apply, then click Submit answer.

• ○

  Material
  

• ○

  Business Partner (EHP6)
  

• ○

  Financials
  

• ○

  Individual transactions
  

• ○

  Enterprise Asset Management (by Utopia)
  

• ○

  Vendor
  
  
  

Select all that apply, then click Submit answer.

• ○

  Search and display.
  

• ○

  Create, Change, Multi-record processing, Mass Change, Parallel Change Requests, Mark for Deletion.

• ○

  Worklists (My Change Request, Display Change Re.
  

• ○

  None of the above.
  
  
  

Select all that apply, then click Submit answer.

• ○

  Built-in guidance, monitoring and reporting using a standard workflow tool provides process and data governance

• ○

  The data maintenance activities are bundled via a change request that is linked to a workflow

• ○

  Integrated tool for keeping data, processes and issue resolution in one place
  

• ○

  Enhanced flexibility by integrated rules management
  
  
  

Select all that apply, then click Submit answer.

• ○

  If reference data only exists in the SAP MDG system, this reference data CANNOT be chosen within the SAP MDG change request processing
  

• ○

  If reference data only exists in the SAP MDG system, the replication to the target system(s) can fail
  

• ○

  If reference data only exists in the target system, this reference data CANNOT be chosen within the SAP MDG change request processing
  

• ○

  If reference data only exists in the target system, the corresponding attributes are automatically removed from the governance scope
  
  
  

Select an option, then click Submit answer.

• ○

  SAP MDG for consistent.
  

• ○

  SAP MDG for standardized.
  

• ○

  SAP MDG for material.
  

• ○

  SAP MDG for collaborative.
  
  
  

Select an option, then click Submit answer.

• ○

  Entity Storage/Use Type 1- Changeable via Change Request; generated data tables
  

• ○

  Entity Storage/Use Type 3 - NOT changeable via SAP MDG; no generated tables
  

• ○

  Entity Storage/Use Type 2 - Changeable w/o Change Request; generated check/text tables
  

• ○

  Entity Storage/Use Type 4 - Changeable via other entity type; generated database table
  
  
  

Select an option, then click Submit answer.

• ○

  The first data set is updated with the data of the second data set
  

• ○

  The first data set is marked for deletion and a second data set is created (from 01.01.2018)
  

• ○

  The first data set is restricted in its validity (until 31.12.2017) and the second data set is created {from 01.01.2018)
  

• ○

  A second data set is created {from 01.0 1.2018) and the first data set is NOT updated
  
  
  

Select an option, then click Submit answer.

• ○

  During the material creation process until the material group of the materials maintained
  

• ○

  During the material creation process until all mandatory fields of the material are maintained
  

• ○

  During the material creation process until the material is saved/submitted
  

• ○

  During the whole material creation process until final approval (activation)
  
  
  

Select an option, then click Submit answer.

• ○

  Define which fields should be governed in which change request step of your process
  

• ○

  Define which fields are required to be maintained in the governance processes
  

• ○

  Define which processes for your SAP MDG applications should be executed
  

• ○

  Define which fields are governed in the data model for your SAP MDG application
  
  
  

Select an option, then click Submit answer.

• ○

  A leading relationship
  

• ○

  Consider Data Export and Data Import via Transfer
  

• ○

  Different and commonly used replication technologies
  

• ○

  Support for peer-to-peer or mediated communication
  
  
  

Select an option, then click Submit answer.

• ○

  Optimize procurement decisions for example, when you have visibility across the enterprise what you purchase from which supplier and at what quantities.
  

• ○

  Streamline your go to market activities when your product data is consistent across your application landscape.
  

• ○

  Optimize business analytics and decision making processes when you can base your strategic business decisions on solid master data.
  

• ○

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

Select an option, then click Submit answer.

• ○

  It defines the user interface on the change request step level, enabling process flexibility.
  

• ○

  This definition overrules the configuration on the logical action and business activity level
  

• ○

  Overall, three entity types are created. One for the design study name (ZHRCHNAME), one for the work packages (ZWPHIER), and one for the year (ZYEAR).

• ○

  Additional UI elements are available that can be added to the single item maintenance UI in order to maintain information on higher level nodes and predecessors