It’s time to put what you’ve learned to the test, get 8 questions right to pass this unit.
1.
Your organization is planning to upgrade SAP Service and Asset Manager from 2005 to 2205. However, you want a pilot group of users to test the App in production before you roll it out to the entire organization. You cannot run both Mobile Apps in parallel.
Choose the correct answer.
2.
Which of the following programs can be used to perform a Readiness check when upgrading the SAP Service and Asset Manager MAIF?
Choose the correct answer.
3.
When upgrading the SAP Service and Asset Manager Metadata if you have a custom MDK project, you must adjust the CIM file to ensure that the override path matches the new standard metadata and the custom metadata.
Choose the correct answer.
4.
You have extended the functionality of the SAP Service and Asset Manager and created localization files i18n. However, after deploying you observe that the language strings of customization are not displaying in the Mobile app. What must you do to fix the issue?
Choose the correct answer.
5.
When creating a .cim file, the application name and project name are important as they define the folder structure of where your component definitions are.
Choose the correct answer.
6.
You are implementing SAP Service and Asset Manager with Meter Management component for customer with SAP ISU. You want to create an incident related to the Mobile AddOn (back end). Which component must be selected when creating the incident?
Choose the correct answer.
7.
If you are changing the image of Action Bar, you must rebuild the app as opposed to just redeploy the bundle as Nativescript has limitations on the "ActionBar" and "Toolbar" customizations.
Choose the correct answer.
8.
If you are planning to use the standard version of the Asset Manager app from the App Store, you must ensure that the Automatic App Updates are turned ON on the mobile devices.
Choose the correct answer.
9.
When using target paths in metadata, be aware that an undefined target path result may cause unexpected results in the MDK rendering on the page.