Q: 7
Refer to the exhibit.
Which ncclient method is used to collect the running configuration of a Cisco IOS XE device that uses
NETCONF?
Which ncclient method is used to collect the running configuration of a Cisco IOS XE device that uses
NETCONF?Options
Discussion
C or D? Leaning toward D since get_config() is what ncclient uses for grabbing configuration data specifically, like "running" config. C isn’t a real method though, right? Not 100 percent sure if anyone’s seen get() used for configs here.
D is the typical method here. In ncclient,
get_config() is meant to retrieve config data, specifically when you want something like the running config from IOS XE. get() is for general operational/state info, not just config. Pretty sure that’s the distinction Cisco expects. Open to being corrected if someone has seen a different real-world behavior.D
B not D. Saw similar syntax in some practice labs and the official guide, both showed m.get for getting config too.
Its D for this one, but it’s a bit tricky. Only
get_config() is the NETCONF operation specifically meant to pull config data (like running config) from IOS XE using ncclient. get() grabs operational/state data instead, not strictly config. So even though the others look close, only D fits exactly per NETCONF/RFC standards. Pretty sure, unless Cisco customized something.Option B makes sense to me since m.get seems like a straightforward way to retrieve data, and 'source=running' points to the running config. I haven’t seen get_config always required for this in some Python scripts. I think this is right, but if anyone knows why this wouldn't work over NETCONF, let me know?
Be respectful. No spam.
