To set up a scenario for regular maintenance, the first event should take place after 1 year, and after that, it is a regular cycle of 6 months, you have to use the maintenance package offset parameter to map this in the system. The maintenance package offset is used to define the time interval between the start of the maintenance plan and the first call date of the maintenance package1. A maintenance package is a set of data that defines the frequency and scope of the maintenance tasks2.
For example, if you want to create a maintenance plan with two maintenance packages, one for annual inspection and one for semi-annual inspection, you can use the following settings:
Maintenance package 1: Cycle length = 12 months, Offset = 0 months, Scheduling indicator = Time-based Maintenance package 2: Cycle length = 6 months, Offset = 12 months, Scheduling indicator = Time-based This means that the first maintenance package will be called at the start of the maintenance plan, and then every 12 months thereafter. The second maintenance package will be called after 12 months from the start of the maintenance plan, and then every 6 months thereafter.
The other parameters that are not relevant for this scenario are:
Package hierarchy: This is used to define the relationship between different maintenance packages within a maintenance plan. It allows you to create nested or parallel maintenance packages that are dependent on each other3.
Scheduling indicator: This is used to define the type of scheduling for the maintenance package, such as time-based, performance-based, or condition-based4.
Cycle modification factor: This is used to modify the cycle length of the maintenance package by a certain percentage or factor5.
References: 1: SAP Help Portal - Maintenance Package Offset 2: SAP Help Portal - Maintenance Package 3: SAP Help Portal - Package Hierarchy 4: SAP Help Portal - Scheduling Indicator 5: SAP Help Portal - Cycle Modification Factor

A . An Inspection Plan and a technical object must be assigned to the same class. This is true because the inspection plan and the technical object must have matching classification characteristics for the inspection checklist generation. The class defines the characteristics that are relevant for the inspection plan and the technical object1.
B . A PM task list with inspection point type must be assigned to the maintenance order. This is false because the inspection checklist generation does not depend on the PM task list. The inspection checklist is based on the QM inspection plan, which is a different type of task list2.
C . An object list must have been generated manually or automatically. This is true because the object list contains the technical objects that will be checked for matching inspection plans. The object list can be generated from the header object of the order, and objects from the maintenance plan item3.
D . A checklist type must be assigned to the maintenance order header. This is false because the checklist type must be assigned to the maintenance order operation, not the header. The checklist type defines the inspection lot origin and the inspection type for the inspection checklist4. References: 1: Explaining Inspection Checklists 2: Inspection Lot 3: Object List and Inspection Checklist 4: Checklist Type in Task List Operation

The Report and Repair Malfunction app is a Fiori app that uses SAPUI5 as the UI technology. SAPUI5 is a modern, HTML5-based, JavaScript UI library that enables developers to create rich and responsive web applications. Web Dynpro, SAP GUI for HTML, and Business Server Pages are older UI technologies that are not used for Fiori apps. References:
Report and Repair Malfunction | SAP Help Portal
First Fiori App for Maintenance Technician: "Report and Repair Malfunction" for SAP S/4HANA Cloud 1708 and 1709 | SAP Blogs

Explanation
A counter is a device that measures the performance or usage of a technical object, such as a machine, a vehicle, or a pump. A counter replacement is a process that involves replacing a defective or outdated counter with a new one. A counter replacement can affect the maintenance planning and scheduling of the technical object, as some maintenance tasks may depend on the counter readings1.
To map a counter replacement in SAP S/4HANA Asset Management, you need to create a new measurement document and assign a valuation code for counter replacement. A measurement document is a record that contains the measurement readings of one or more counters or measuring points. A valuation code is a key that indicates the quality or validity of the measurement reading, such as OK, Not OK, Estimated, or Counter Replacement2.
By creating a new measurement document and assigning a valuation code for counter replacement, you can inform the system that the counter has been replaced and the previous counter readings are no longer valid.
The system will then use the new counter readings for maintenance planning and scheduling purposes. You can also enter additional information about the counter replacement, such as the reason, the date, and the time3.
The other options are incorrect because:
Deactivate the current counter and create a new counter: This option is not recommended, as it will create a new counter object in the system and break the link with the previous counter object. This will result in data inconsistency and loss of historical information about the counter readings and maintenance activities3.
Create a new measurement document marked as a counter replacement: This option is incomplete, as it does not specify how to mark the measurement document as a counter replacement. You need to use the valuation code field to indicate the counter replacement3.
Assign a catalogue type for counter replacement to the measuring point category: This option is irrelevant, as it does not involve creating a new measurement document. A catalogue type is a key that defines the structure and content of a catalogue, which is a collection of codes and texts that describe the characteristics of a technical object, such as damage, cause, or activity. A measuring point category is a key that defines the attributes and functions of a measuring point, which is a physical or logical location where a measurement is taken.
References: 1: Counter (SAP Library - Glossary) 2: Measurement Document (SAP Library - Glossary) 3:
Counter Replacement - SAP Help Portal : Catalog Type (SAP Library - Glossary)