After naming challenges, the team maps remedies: distributed storage for scale limits, parallel processing for slow jobs, NoSQL for flexible structures, streaming for timely signals, and cloud elasticity for spiky demand. Which statement best captures the BDPC skill being practiced?
Select an answer to reveal the explanation.
Short Explanation
Once you name the bruise, you pick the bandage that fits—storage for "too big," parallelism for "too slow," NoSQL for "too bendy," streams for "too late," cloud stretch for "too spiky." Matching remedies to pains is the skill. Random logos or deleting metadata do not count as mapping.
Full Explanation
BDPC expects learners to relate key technological solutions to the challenges of Big Data administration. Distributed storage, parallel processing, NoSQL, streaming, and cloud elasticity each address recognizable pains such as scale, latency, flexible data models, timely insight, and variable load. Random tool selection, slogan-only mapping, or claiming elasticity erases schema-governance needs misapply that solution-mapping skill.