Universal Containers CUC) is an enterprise financial company that operates in EMEA, AMER, and APAC. Because of regulatory requirements, UC has a separate Salesforce org for each region. Each org has its own customizations that fit for the region needs, but there are also standard processes that apply to all regions requirements.
As the deployment architect, what should be considered for the multi-org deployment strategy?

Universal Containers is about to begin Development work on a new project in their Salesforce org that will take many months to complete. UC is concerned about how critical bugs will be addressed for existing live functionality. What is the recommended release management strategy to address this concern?

Universal Containers has decided on a single-org strategy, despite having to deal with the complexity of having multiple lines of business (LOBs) inside a single org.
What are two common challenges in single-org strategy for multiple LOBs?
Choose 2 answers

Universal Containers are concerned that after each release, reports and dashboards seem to roll back to previous versions. Executives spend many hours crafting these dashboards to perfectly meet their needs, and are now questioning the Salesforce platform's ability to save things, even data records.
What can the Salesforce architect advise to stop the rollbacks from happening?

A developer on the Universal Containers team has written a test class to test a method that involves a web service callout. Within the test class, the developer is supposed to load test data, create an instance of the Mock object, set the Test.setMock() to that Mock object, call startTest(), execute the code that makes the callout, call stopTest(), and compare the result with expectations. Unfortunately, the Developer forgot to use the Test.setMock() method step.
What would happen when the developer runs this test class?