A city automation DELETE of an FDM network object returns 4xx. The object shows isSystemDefined or is still referenced by an access rule. What should the client do first?
Select an answer to reveal the explanation.
Short Explanation
System objects and in-use objects are locked doors—retrying the same DELETE just rattles the handle. Unlink the access-rule references first, or leave system-defined objects alone.
Full Explanation
A 4xx on DELETE is expected when the FDM object is isSystemDefined or still referenced by an access rule. The constructed client must unlink those references first, or skip system objects entirely. Retrying the same DELETE does not fix the constraint. Packet-trace and IPS-signature workflows are unrelated to why the object delete was rejected.