Flow Reference Component
Flow Reference routes the Mule event to another flow or subflow, executes all processors in the referenced flow, and then routes the event back within the same Mule application. The following diagram shows the order of processing when one flow references another:

When the main flow is triggered, the Mule event travels through and executes the flow until the event reaches the Flow Reference. The event then travels through and executes the referenced flow from beginning to end, and then returns to the main flow.
This process enables you to treat the entire referenced flow like a single component in your current flow.
Mule Ref Doc : https://docs.mulesoft.com/mule-runtime/4.3/flowref-about Correct answer is
* payload
* quantity var
* color query param

An object store is a facility for storing objects in or across Mule applications. Mule runtime engine (Mule) uses object stores to persist data for eventual retrieval. Internally, Mule uses object stores in various filters, routers, and other message processors that need to store states between messages.
Object stores are available in all deployment targets. If you deploy your application to CloudHub, you can also use Object Store V2.
Correct answer is Key/value pair in Object store
MuleSoft Documentation reference :
https://docs.mulesoft.com/mule-runtime/4.3/mule-object-stores#use-cases

Correct answer is Select only Attach Project Sources only
You must keep the Attach Project Sources option selected to be able to import the packaged JAR file back into a Studio workspace.
Deselect the Include project modules and dependencies option.
This option skips bundling the actual modules and external dependencies required to run the Mule application in a Mule runtime engine, creating a lightweight JAR file package that does not include any dependencies specified in the Mule application's pom.xml file.
The generated JAR file is not a functional deployable archive and cannot be deployed to a Mule runtime engine, but instead offers a way to archive only the source files that make up the Mule application. This is the same as using the -lightWeightPackage flag when packaging using the Mule Maven Plugin and is useful if you want to distribute your project to other Studio installations because it only keeps a reference to all its dependencies. When you import a lightweight package into Studio, all your dependencies are automatically downloaded MuleSoft Doc Ref : https://docs.mulesoft.com/studio/7.8/import-export-packages