An Order Management System (OMS) handles orders from multiple brandspecific sites, as part of the processing, the OMS sends the processing detail to be added at notes to the orders in B2C Commerce. These processing details are captured temporarily in custom objects, and are later processed by a batch Job that:
* Processes the custom object to extract the orderid and note data.
* Tries to load the order.
* If the order is not found, it deletes the custom object and moves on.
* If the order is found, it updates notes In the Order, upon successful update of this order, it deletes the custom object.
There is an Issue reported that the job is constantly failing and custom objects are growing in number. On investigating the production look the message below is being logged on each failure:

What are three solution The Architect can take to fix this issue without losing meaningful data?
Choose 3 answers
Correct Answer: C,D,E
When facing an issue with a growing number of custom objects due to the exceeded quota limit for order notes, effective solutions include:
* Option C (Take the backup of the custom object and delete the custom object): This ensures that the data is preserved while freeing up space for new processes and reducing the load, allowing the job to continue running without the impediment of quota limits.
* Option D (Engage B2C Commerce Support Team to soften the quota limit for 'object.OrderPO.
relation.notes'): Increasing the quota limit can resolve the root cause of the issue by accommodating the actual business needs without compromising the integrity of order processing and note addition.
* Option E (Take the backup of the Order as XML and delete the notes from Order): This allows the job to process the custom objects as intended in subsequent runs by clearing out space while ensuring the order data remains intact for business needs.
These steps address the quota limit issue effectively without losing valuable order or note data, ensuring continuity and integrity of business operations.