Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Cisco Exam 300-535 Topic 15 Question 58 Discussion

Actual exam question for Cisco's 300-535 exam
Question #: 58
Topic #: 15
[All 300-535 Questions]

Which NETCONF datastore is locked while the network device configuration is edited?

Show Suggested Answer Hide Answer
Suggested Answer: A

Contribute your Thoughts:

Hubert
6 months ago
Candidate 2: Me too. It makes sense based on how NETCONF works.
upvoted 0 times
...
Andree
6 months ago
Candidate 1: I'm sticking with C) startup as the answer.
upvoted 0 times
...
Octavio
7 months ago
Candidate 4: No, the running configuration can still be read and applied, so it's not locked.
upvoted 0 times
...
Aleta
7 months ago
Candidate 3: But wouldn't the running datastore also be locked?
upvoted 0 times
...
Soledad
7 months ago
Candidate 2: Yeah, I agree. The startup datastore is locked during configuration edits.
upvoted 0 times
...
Shizue
7 months ago
Candidate 1: I think the answer is C) startup.
upvoted 0 times
...
Glory
7 months ago
Hmm, I see where you're coming from, Emmanuel. That could also be a valid answer.
upvoted 0 times
...
Emmanuel
7 months ago
I see your point, Emerson, but I still think A) running makes more sense for the locked datastore.
upvoted 0 times
...
Emerson
7 months ago
I disagree, I believe the correct answer is C) startup, as that datastore holds the initial configuration.
upvoted 0 times
...
Glory
7 months ago
I think the answer is A) running because that's the datastore that is being changed.
upvoted 0 times
...
Breana
8 months ago
Haha, good one! But seriously, I'm pretty confident it's the 'running' datastore that gets locked. Let's go with that as our answer.
upvoted 0 times
...
Lemuel
8 months ago
Yeah, that sounds about right. The 'running' datastore is the one we typically edit when making changes to the device configuration.
upvoted 0 times
...
Flo
8 months ago
Nice try, but the 'working' datastore is not even a real thing in NETCONF. I think you've been spending too much time in the 'working' datastore of the local pub!
upvoted 0 times
Virgie
7 months ago
C) startup
upvoted 0 times
...
Doug
8 months ago
No, the common datastore doesn't exist in NETCONF.
upvoted 0 times
...
Glenn
8 months ago
B) common
upvoted 0 times
...
Jesusita
8 months ago
Yes! The running datastore is locked while the network device configuration is edited.
upvoted 0 times
...
Aimee
8 months ago
A) running
upvoted 0 times
...
Melissa
8 months ago
Nope, it's not the startup datastore. Try again!
upvoted 0 times
...
Johna
8 months ago
C) startup
upvoted 0 times
...
...
Casie
8 months ago
Hmm, this is a tricky one. I know that NETCONF is used for managing network device configurations, but I'm not sure about the specifics of the datastores.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77