Which two statements apply when a user has entered private configuration mode by typing configure private?

Entering configuration mode using the configure private command allows multiple users to edit the configuration while
committing only their private changes. (You must issue a commit command from the [edit] hierarchy.) If private users issue
a rollback 0 command, the software discards only their changes.
When a user is in private mode, other users must enter private mode or use configure exclusive to become the master,
or they cannot modify the candidate configuration. Exiting private configuration without committing changes results in the loss
of any modifications made to the private candidate configuration.
JNCIA-Junos Study Guide—Part 1
© 2012 Juniper Networks, Inc. All rights reserved. User Interface Options • Chapter 2–11
If two users are in private mode and both make the same change (For example, User 1 changes the system hostname to
apples while User 2 sets the hostname to oranges), the second commit will fail with an error message to avoid
configuration conflicts. The software places the second user’s changes into effect if User 2 issues a second commit command.
When chassis clustering is in effect, the configure private command is automated. In some other environments, you
might want to require users to use only configure private. When creating user accounts, it is possible to limit the
commands available to users through the assigned properties. We discuss user accounts and their assigned properties later in
this course.
If a user is in configuration mode and has altered the candidate configuration, other users cannot enter configuration mode
using the exclusive or private options. The changes made by the first user must be committed or cancelled prior to any
other users entering configuration mode with the exclusive or private options.