Selected Answer: A primary keeps working, tested on my LAB in eve--ng. read the question, it says deregisters. Answer is: A Secondary Restart pls correct the answer

ANSWER IS D, the primary node keeps operating as a standalone node, handling all the necessary Cisco ISE functions, including authentication, authorization, and policy enforcement. The primary node will no longer have a failover partner or redundancy from the secondary node.

The answer is A Exam now is about version 3.1 which matches answer A, The answer C was the old ISE exam & version, The provided links from friends here regarding answer C is correct in the past but now Exam is about ver 3.0 & 3.1

Note For example, if your deployment has two nodes and you deregister the secondary node, both nodes in this primary-secondary pair are restarted. (The former primary and secondary nodes become standalone.)

So the correct answer is A. - The secondary node restarts.

Selected Answer: D The correct answer is D. The primary node becomes standalone. When a secondary node is deregistered from a Cisco ISE distributed deployment, the connection between the primary and secondary node is lost. As a result, the primary node becomes standalone and all of the configuration data that was stored on the secondary node is lost. The other answer choices are incorrect: A. The secondary node restarts. This is not correct because the secondary node is no longer part of the deployment after it is deregistered. B. The primary node restarts. This is also not correct. The primary node remains running after the secondary node is deregistered. C. Both nodes restart. This is not correct. Only the primary node remains running after the secondary node is deregistered.

Selected Answer: A Effects of Modifying Nodes in Cisco ISE When you make any of the following changes to a node in a Cisco ISE, that node restarts, which creates a delay: Register a node (Standalone to Secondary) Deregister a node (Secondary to Standalone) Change a primary node to Standalone (if no other nodes are registered with it; Primary to Standalone) Promote an Administration node (Secondary to Primary) Change the personas (when you assign or remove the Policy Service or Monitoring persona from a node) Modify the services in the Policy Service node (enable or disable the session and profiler services) Restore a backup on the primary and a sync up operation is triggered to replicate data from primary to secondary nodes Taken straight from: https://www.cisco.com/c/en/us/td/docs/security/ise/2-4/admin_guide/b_ISE_admin_guide_24/m_setup_cisco_ise.html#ID193

Selected Answer: A isco ISE Node Deregistration To remove a node from a deployment, you must deregister it. When you deregister a secondary node from the primary PAN, the status of the deregistered node changes to standalone, and the connection between the primary and the secondary node is lost. Replication updates are no longer sent to the deregistered standalone node.

Provided answer is correct. https://www.cisco.com/c/en/us/td/docs/security/ise/1-0/install_guide/ise10_deploy.html#:~:text=Note%20You%20cannot%20deregister%20a%20primary%20Administration%20ISE%20node.&text=Note%20For%20example%2C%20if%20your,and%20secondary%20nodes%20become%20standalone.)

Guys this is D! I have seen this happen and reregistered it on very many occasions. There is no restart of any kind!

ISE 3.0 and later - Youki82 is correct: Primary PAN node does NOT become standalone when Secondary is deregistered: "If the node has a Primary role, and there are no other nodes registered with it, the Make Standalone button appears next to it." - this means that you have to make it Standalone manually after deregistration of Secondary. "When you make any of the following changes to a node in a Cisco ISE, that node restarts... - Register a node (Standalone to Secondary) - DEREGISTER a node (Secondary to Standalone) - Change a primary node to Standalone (if no other nodes are registered with it; Primary to Standalone) - Promote an Administration node (Secondary to Primary) ... Note When you promote the secondary Administration node to the primary PAN position, the primary node will assume a secondary role. This causes both the primary and secondary nodes to restart, causing a delay. " https://www.cisco.com/c/en/us/td/docs/security/ise/3-0/admin_guide/b_ISE_admin_3_0/b_ISE_admin_30_deployment.html

Answer is: A

The correct answer is A. I have hands-on experience with it.

Note For example, if your deployment has two nodes and you deregister the secondary node, both nodes in this primary-secondary pair are restarted. (The former primary and secondary nodes become standalone.) https://www.cisco.com/c/en/us/td/docs/security/ise/1-0/install_guide/ise10_deploy.html#:~:text=Note%20You%20cannot%20deregister%20a%20primary%20Administration%20ISE%20node.&text=Note%20For%20example%2C%20if%20your,and%20secondary%20nodes%20become%20standalone.)

Answer: A >> When a node is registered, the primary PAN pushes configuration data to the secondary node, and the application server on the secondary node restarts. https://www.cisco.com/c/en/us/td/docs/security/ise/2-7/admin_guide/b_ise_27_admin_guide/b_ISE_admin_27_deployment.html#ID498

Selected Answer: C the cisco documentation at this link: https://www.cisco.com/c/en/us/td/docs/security/ise/1-0/install_guide/ise10_deploy.html#:~:text=Note%20For%20example%2C%20if%20your,and%20secondary%20nodes%20become%20standalone.) clearly says: if your deployment has two nodes and you deregister the secondary node, both nodes in this primary-secondary pair are restarted. (The former primary and secondary nodes become standalone.)

Selected Answer: A Whenever we deregister a node in ISE, that node restarts and creates a delay. Reference : https://www.cisco.com/c/en/us/td/docs/security/ise/3-2/admin_guide/b_ise_admin_3_2/b_ISE_admin_32_deployment.html

Selected Answer: A tested in lab: only the secondary nodes restart. the cisco documentation that mentions both nodes restarting is from 2011 and for ise 1.0, so it is no longer valid

please ignore this comment of mine since the documentation is from 2011