Its a known issue of AEM Archetype and its mentioned in document as well. To give the background, Archetype initially creates all sub modules(react, dispatcher) in a project and based on the input arguments it does clean up.Probably at that time it needs higher permissions to do clean up. Refer this...

Please refer same query answered earlier : https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-6-5-ad0-e126-certification-exam-study-material/td-p/461073 Exam Guide : https://express.adobe.com/page/DEXF9MMfGc74P/ On top of this you can do practice test for similar exam AD4-...

  Sample code   @ExtendWith({ AemContextExtension.class, MockitoExtension.class }) public class SampleTest { private final AemContext aemContext = new AemContext(ResourceResolverType.JCR_MOCK); @Mock private Resource resource; @Mock private SlingHttpServletRequest request; @Mock priva...

@fionas76543059 : Yes, please.

If old acs-commons is still available inside /apps then the client libraries present in it will still be getting applied. So /apps/acs-commons-old should be removed.

Can you please share the error of pipeline failure ?

Did you rename the old /apps/acs-commons to /apps/acs-commons-old before installing package?

Please check this App : Dynamic Media Classic Desktop App. It will give you more information about images from Scene7 perspective. Link : https://experienceleague.adobe.com/docs/dynamic-media-classic/using/intro/dynamic-media-classic-desktop-app.html?lang=en  

Please confirm whether you want to do connection of AEM with scene7 on your local or you want to see the images/renditions created in Scene7 locally?

In that case you should always make isEmpty to pass true.  isEmpty: function(props) { return true; }