The typical Cobra SDK workflow is: 1) log in (`login`), 2) build/modify the managed object (MO) tree locally (`setAttr`, creating child objects, etc.), 3) wrap the modified objects into a
`ConfigRequest`, and 4) call `moDir.commit()` - only this actually pushes the configuration to APIC. Calling `setAttr()` alone only sets a local "dirty flag" on the in-memory object tree and produces no network traffic; `query()` reads rather than writes. This tests understanding of Cobra's local-object-tree-plus-explicit-commit programming model, a finer point of Network Element Programmability.