Which ncclient manager call prevents others from modifying the device while a script runs?

The m.lock(target='running') call in ncclient acquires a lock on the running configuration, preventing other NETCONF sessions or users from making changes to the device's configuration while the script is executing. This ensures configuration consistency and avoids conflicts. m.lock(config='running') is incorrect because config is not a valid parameter for the lock method; the correct parameter is target. m.freeze() is not a standard ncclient method for locking configurations; the lock method is used for this purpose.