ITS SM-CDT common mistakes
ITS SM-CDT · Understand the traps and how to avoid them.
Treating 'social media concepts' as vocabulary recall only - memorising terms like reach, impression, engagement rate, and algorithm without being able to say how a platform's feed-ranking logic changes what a creator should post.
The concepts domain reads like a glossary, so candidates skim it and drill definitions. Exam items then ask for applied judgement (e.g. why a post with high impressions can have low engagement, or why chronological vs algorithmic feeds reward different posting cadences), and the definitions alone don't answer them.
What to do instead
For each core concept, write a one-line 'so what' next to the definition: what it measures, what it does not measure, and one decision it should change. Practise explaining each term with a concrete scenario from a platform you actually use.
Assuming all platforms behave the same - applying one platform's norms (posting frequency, ideal aspect ratio, hashtag use, tone) to every platform in a scenario question.
Candidates usually have deep familiarity with one or two platforms and generalise from that experience. Exam scenarios often hinge on platform-specific constraints such as character limits, native content formats, or how discovery works on that platform.
What to do instead
Build a comparison table with one column per major platform type (feed-based, short-video, professional network, messaging-first) covering format, discovery mechanism, typical audience intent, and content lifespan. Review it before practising scenario questions.
Answering content-production questions on creative preference rather than on the stated objective, audience, and channel constraints.
Candidates with creative backgrounds instinctively pick the option that looks most polished or original, but the correct answer is usually the one that fits the brief - correct format, length, accessibility, and platform specification.
What to do instead
Before choosing, restate the brief in the question: objective, audience, platform, and any hard constraint. Eliminate options that violate a stated constraint first, then judge the remainder against the objective.
Ignoring technical delivery specifications - aspect ratio, resolution, safe zones, caption and subtitle practice, file format, and loudness - when evaluating a production plan.
These details feel like production trivia, so candidates focus on storytelling and messaging. Exam items frequently test whether a deliverable will actually render correctly and be consumable on the target platform, especially for video and vertical formats.
What to do instead
Memorise a short spec sheet: common aspect ratios and where each is used, why text near edges gets cropped by interface overlays, why captions matter for silent viewing, and standard delivery formats. Tie each spec to the consequence of getting it wrong.
Treating community management as reactive moderation only, and missing proactive elements - onboarding, community guidelines, response-time expectations, escalation paths, and recognising positive contributions.
Day-to-day community work is often experienced as answering comments and removing bad posts, so candidates underweight the structural side. Scenario questions reward the answer that prevents problems through norms and process rather than only cleaning up afterwards.
What to do instead
Map the community lifecycle (recruit, welcome, engage, escalate, retain) and list one concrete tactic per stage. When a question describes a problem, ask which lifecycle stage failed before choosing a remedy.
Choosing the most severe response to a negative or hostile interaction - deleting, blocking, or public confrontation - without first weighing proportionality, transparency, and documented policy.
Confrontation feels decisive and candidates want to show they act on harassment. Exam items usually favour responses that follow published guidelines, de-escalate, preserve evidence where relevant, and escalate internally before acting publicly.
What to do instead
Learn a graduated response ladder (acknowledge, clarify, private follow-up, hide or remove per policy, restrict, escalate to legal or safety). For each scenario, identify the least intrusive step that resolves the issue and cite the policy basis.
Describing tools by brand name without knowing what job each tool performs in the workflow, so tool-selection questions are answered by familiarity rather than fit.
Candidates learn the tools they use daily and assume the exam asks which tool they like. Items instead test workflow fit: scheduling, asset management, approval routing, collaboration, automation, and how tools hand off to one another.
What to do instead
Draw your own content pipeline end to end and label each stage with the category of tool needed and the handoff artefact (brief, asset, approval, scheduled post, report). Practise choosing a tool category from a described bottleneck.
Confusing vanity metrics with outcome metrics when interpreting a performance report or recommending next steps.
Follower counts, likes, and raw impressions are visible and rewarding, so candidates anchor on them. Exam items test whether you can connect a metric to the objective - awareness, consideration, conversion, retention - and spot when a metric cannot support the conclusion drawn.
What to do instead
For every metric you review, write what decision it can and cannot justify. Practise reading a described result and stating the metric definition, the comparison baseline, and one alternative explanation before recommending action.
Skipping the measurement setup question - objective, KPI, baseline, timeframe, and tracking method - and jumping straight to interpreting numbers.
Analytics questions often present data, which invites immediate interpretation. But many items test whether a measurement plan is valid at all, and a result without a baseline or defined metric cannot support the claimed conclusion.
What to do instead
Use a fixed checklist on every analytics item: what was the objective, what was the KPI definition, what was the baseline, over what period, and how was it tracked. If any element is missing, treat the conclusion as unsupported.
Handling ethics and digital citizenship as obvious 'be a good person' answers, missing disclosure, consent, privacy, intellectual property, accessibility, and platform-policy specifics.
The ethical choice often seems self-evident, so candidates pick the warmest-sounding option. Exam items test precise obligations: when a paid partnership must be disclosed and how, when consent is needed to repost someone's content, how personal data may be used, and what attribution actually requires.
What to do instead
Build a short rules card for each area - disclosure, consent, copyright and licensing, privacy and data minimisation, accessibility, and crisis communication - with the trigger condition and the required action. Apply the trigger test to each scenario before selecting.