APMA common mistakes
APMA · Understand the traps and how to avoid them.
Computing a time-weighted return by chaining sub-period returns without first geometrically linking them, or reporting a money-weighted (IRR) figure when the question asks for the manager's return.
Candidates conflate the two return concepts because both are called 'return'; the IRR is easier to compute from a cash-flow table, so it gets used by default even when the manager's investment skill is the subject.
What to do instead
Before computing, decide whether cash flows were controlled by the manager. If yes, use TWR (link sub-period HPRs geometrically). If the client controlled flows, use MWR/IRR. Write the chosen method's name at the top of your scratch work so the rest of the calculation stays anchored to it.
Comparing a portfolio's raw return to a benchmark without adjusting for risk, or using the wrong risk measure (e.g., Treynor when the portfolio is not fully diversified).
Candidates memorize the ratio formulas but not their assumptions; beta-based measures look interchangeable with sigma-based ones, so the first formula recalled gets applied.
What to do instead
Build a one-line decision rule: Sharpe uses total risk (sigma) and suits undiversified/whole portfolios; Treynor and Jensen use systematic risk (beta) and require a well-diversified portfolio; information ratio uses tracking error versus a benchmark. Match the denominator to the question's description of the portfolio before computing.
Treating the IPS as boilerplate and jumping straight to allocations, ignoring stated constraints such as liquidity needs, time horizon, tax status, legal/regulatory limits, or unique circumstances.
The quantitative allocation work feels like 'the real question,' and the qualitative constraints read as filler; under time pressure candidates skip the narrative and lose the constraint-driven answer choices.
What to do instead
Read the IPS scenario and write out the five constraints (return, risk, liquidity, time horizon, tax/legal/unique) as a checklist before touching numbers. Eliminate any allocation that violates a stated constraint, then optimize among survivors.
Applying a single risk-tolerance label as if it were the whole IPS, and recommending the highest-return asset mix regardless of the client's ability versus willingness to bear risk.
Candidates collapse 'risk tolerance' into one dimension and forget that ability (financial capacity) and willingness (psychological) can conflict and must be reconciled, usually to the lower of the two.
What to do instead
Separate ability to take risk (balance sheet, horizon, liquidity) from willingness (attitude, past behavior). Where they conflict, default to the more conservative constraint and state that reconciliation explicitly in the answer.
Rebalancing or strategic-allocation questions answered with tactical or momentum logic - e.g., recommending drifting with winners because 'the trend is up' when the policy calls for disciplined rebalancing to target weights.
Real-world headlines and momentum intuition contaminate the policy framework; candidates forget that strategic asset allocation is a policy decision, not a forecast.
What to do instead
Tag each question as strategic (policy weights, long horizon, rebalancing discipline) or tactical (short-horizon deviations from policy based on valuation/cycle views). Answer within the tagged frame; if rebalancing is asked, describe the rule (calendar vs. threshold) and its effect on risk, not on return-chasing.
Describing a style (value, growth, momentum, quality) by its recent performance rather than by its defining construction rule, and misclassifying a manager whose holdings straddle categories.
Style labels are learned through examples and market lore; without the explicit sorting/weighting rule, candidates default to 'cheap = value, expensive = growth' and miss blended or size-tilted cases.
What to do instead
For each style, state the construction rule (e.g., value = low price-to-fundamentals with periodic rebalancing; momentum = recent relative-return ranking; quality = profitability/leverage screens). Classify a manager by applying the rule to the described holdings, and note style drift if holdings no longer match the stated mandate.
Ignoring transaction costs, taxes, and implementation shortfall when evaluating whether an active strategy adds value, or crediting gross alpha where net alpha is what the client earns.
Textbook alphas are gross; candidates carry the gross number into the recommendation because costs are described in a separate sentence of the scenario.
What to do instead
Always convert to net: subtract management fee, trading costs, and tax drag from gross return before comparing to the benchmark or computing the information ratio. If the question gives a cost figure, it is there to be used - treat an unused cost input as a red flag.
Assuming diversification benefits are constant and additive, ignoring correlation shifts and the fact that correlations rise in stress, so a portfolio's realized risk exceeds the naive weighted-average estimate.
Mean-variance intuition treats correlation as stable and low; candidates compute portfolio sigma from weights and individual volatilities without checking the correlation input or its regime dependence.
What to do instead
When computing portfolio risk, use the full variance formula with the correlation/covariance term and sanity-check the result against the weighted-average volatility (portfolio sigma should be below it only if correlation < 1). In stress scenarios, raise assumed correlations toward 1 and re-evaluate the diversification claim.
Confusing alpha with excess return and beta with total risk when decomposing performance - e.g., labeling a high-beta portfolio's bull-market outperformance as manager skill.
The CAPM decomposition (return = risk-free + beta × market premium + alpha) is memorized as a formula but not as an attribution logic, so systematic return gets attributed to the manager.
What to do instead
Decompose explicitly: compute the return explained by beta exposure first, then the residual as alpha. Only the residual, after costs, counts as skill. If the question describes a rising market and a high-beta fund, expect the answer to attribute the gain to beta, not alpha.
Building a portfolio by ranking assets on expected return alone, without checking that the resulting weights satisfy the investor's risk budget, liquidity profile, and concentration limits.
Optimization is treated as 'pick the highest-return mix'; constraints and the risk objective are handled as afterthoughts, so the recommended portfolio is efficient on paper but infeasible for the client.
What to do instead
State the objective (maximize return for a given risk, or minimize risk for a given return) and the binding constraints first, then select weights. After constructing, run a feasibility check: does the mix meet the risk budget, liquidity needs, and any single-asset caps? If not, the answer is wrong regardless of its expected return.