Basic of CMS IntelliCAD and GD&T

A: A is boring but safe. Large coordinates, frozen layers, or geometry 10 km from 0,0 show up weekly in supplier data. B feels proactive, but AUDIT can silently drop proxy objects when the issue is just visibility. C often works, which is why people reach for it, but you lose layer states and blocks with no evidence they were the problem. D sounds CAD-savvy, yet UCS settings rarely hide geometry by themselves.

A: A respects configuration control. Missing SHX or TTF mappings are the usual cause. B makes the drawing look right today but kills associativity and future edits. C confuses drafting standard with font support; the symbols still need a font. D is tempting under launch pressure, yet you've now created nonstandard annotations that won't survive revisions or exports.

A: A hurts, but it's the truth. Scaling model space changes geometry, not the meaning of a ±0.1 mm callout. B is the first instinct from people used to plotting, not design control. C mixes up dimension associativity with annotation objects; CMS IntelliCAD doesn't protect GD&T that way. D addresses documentation optics, not the physical requirement encoded in the tolerances.

A: A feels slow on day one but saves arguments at PPAP. B works for sketches, not controlled drawings. C is common under time pressure, yet you inherit unknown layer logic and broken standards. D sounds harmless since units match, but ISO vs ASME GD&T semantics do bite during inspection.