Exam-style question
Try this first
Which answer would avoid generic Business-style reasoning on Production, costs and revenue? Variation 5: Explain AQA section 3.1.4.2 Specialisation, division of labour and exchange.
- A.Use economic terminology such as demand, supply, elasticity, market failure, welfare, efficiency or policy trade-off instead of general business language.
- B.A tax shifts demand rather than affecting supply incentives and costs.
- C.Regulation is the same policy as a subsidy because both involve government.
- D.Give a definition of labour markets only, without application, chain of analysis, evaluation or judgement.
Model answer
What a good answer should say
- 3.1.4.2 Specialisation, Division of Labour and MCQ 5: The correct answer is Use economic terminology such as demand, supply, elasticity, market failure, welfare, efficiency or policy trade-off instead of general business language...
- This choice fits the microeconomic market analysis required by the learning objective.
Explanation
Why this works
3.1.4.2 Specialisation, Division of Labour and is tested here through the prompt: "Which answer would avoid generic Business-style reasoning on Production, costs and revenue? Variation 5: Explain AQA".
The correct option is "The correct answer is Use economic terminology such as demand, supply, elasticity, market failure, welfare, efficiency or policy trade-off instead of general business language.." because it keeps the answer anchored to Specialisation, Division of Labour and rather than a nearby misconception. The reasoning chain is: define the concept, apply it to Individuals, firms, markets and market failure, identify the economic mechanism, and check the consequence against consumer surplus, producer incentives, efficiency and equity.
A tempting distractor usually confuses a change in demand with quantity demanded, analysis with evaluation, or a short-run effect with a long-run judgement. For AQA Economics 7136, the best choice is the one that preserves the cause, transmission mechanism and consequence without adding an unsupported policy claim.
Common mistake
No common mistake is linked to this question yet.