Correct syntax to use where clause is WHERE city = :city AND state = :state This question validates knowledge on using dynamic queries in DB select operation.
Configure Dynamic Queries in the Select Operation
When you need to parameterize not only the WHERE clause but also parts of the query itself (for example, queries that compare tables that depend on a condition, or complex queries for which the project table columns need to vary), you can configure dynamic queries.
In the following example, you configure a dynamic query by using a full expression with a string in which the table depends on a variable $(vars.table). Although some of the query text is dynamic ("SELECT * FROM $(vars.table)), the WHERE clause still defines the WHERE condition using input parameters: in this case, WHERE name = :name.
In your Studio flow, select the Select operation.
In the operation configuration screen, set the SQL Query Text field to SELECT * FROM $(vars.table) WHERE name = :name.
Set the Input Parameters field to {'name' : payload}.
The following screenshot shows the configuration in Studio:

Figure 3. Dynamic query configuration
In the XML editor, the <db:sql> configuration looks like this:
<set-variable variableName="table" value="PLANET"/>
<db:select config-ref="dbConfig">
<db:sql>#["SELECT * FROM $(vars.table) WHERE name = :name"]</db:sql>
<db:input-parameters>
#[{'name' : payload}]
</db:input-parameters>
</db:select>
You can apply input parameters only to parameters in a WHERE clause. To modify any other part of the query, use the DataWeave interpolation operator.
Mule Ref Doc: Query a Database Examples - Mule 4 | MuleSoft Documentation

In this case as outbound call is made using HTTP: POST /child , all attributes will be replaced by this invocation. Hence query parameter will not be accessible at logger.

Correct answer is MAJOR
MAJOR version when you make incompatible API changes, MINOR version when you add functionality in a backwards compatible manner, and PATCH version when you make backwards compatible bug fixes.
For details refer to this documentation : https://semver.org/

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