* Why @TestSetup?
* The @TestSetup annotation creates a baseline set of test data once per test class.
* Test methods reuse this data, avoiding the need to recreate it repeatedly, which improves efficiency.
* Why Not Other Options?
* A: HttpCalloutMock is used for mocking callouts, not for creating test data.
* C: Using seeAllData=true is discouraged because it relies on org data, violating test isolation principles.
* D: While creating data in Test.startTest() works, it is less efficient than @TestSetup for shared data.
* Test Setup Methods: https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode
/apex_testing_testsetup.htm
References:

Option C implements a before insert trigger to prevent the creation of Request__c records when specific conditions exist. It uses the addError method to display an error to users.
Example of correct logic:
trigger RequestTrigger on Request__c (before insert) {
for (Request__c req : Trigger.new) {
if (!RequestLogic.isValid(req)) {
req.addError('Your request cannot be created at this time.');
}
}
}

A Global Picklist Value Set allows the same set of picklist values to be shared across multiple objects, making maintenance easier and ensuring consistency.
Why not other options?
B: Alphabetical ordering does not ensure consistent value maintenance across objects.
C: Validation rules do not streamline picklist value maintenance.
D: Restricting picklist values helps ensure data integrity but does not streamline maintenance across objects.
Global Picklists Documentation