Correct answer is A. If you set up a node group and one PSN goes down, the other will send a CoA and take over.

Correction! Correct answer is D

CORRECT IS A https://www.ciscopress.com/articles/article.asp?p=2812072&seqNum=2 If a PSN goes down and orphans a URL-redirected session, one of the other PSNs in the node group sends a Change of Authorization (CoA) to the NAD so the endpoint can restart session establishment with a new PSN.

Selected Answer: D D is the correct answer. Node groups are optional and they mainly enhance the profiler service. The redundancy of PSN availability is determined by the Radius Server list order on the NAD. also see this https://community.cisco.com/t5/network-access-control/ise-node-groups/td-p/3514849

Selected Answer: A A is correct. The question asks for redundancy in "deployment" not in configuration so D is not the right choice. Additionally, using the RADIUS server list on NAD makes redundancy for authentication, the attributes are also shared between group nodes. When a member of a node group learns endpoint attributes (through profiling), it is able to send the information directly to the other members of the node group.

Selected Answer: A See 300-715 Official Cert Guide, pg 748 ISE has a concept of Node Goup. A Node Group is made up of PSN, where the PSNs maintain a heartbeat with each other.... when a member of a node group leaens endpoint attributes (through profiling) , it is able to send the information directly to the other members of the node group.

Selected Answer: D A, B, C are inputs and D is the result

Selected Answer: D NAD will decide which PSN node to use based on the radius server list configured on it.

Selected Answer: D STUPID Question. It's D A is not the answer because it talks about redundancy and not e.g. CoA. I can still have redundancy whether it's "statefull" or "stateless". If i have a nodegroup and the Switch only points to 1 PSN node, i have ZERO redundancy. Therefor i need the reduncance configured on the NAD to utilize ALL the PSN nodes.

Selected Answer: A Answer is A. Since the question is about ISE PSN deployment redundancy, the answer is A. If the question is from the End user side, then redundancy can be achieved by using the Radius server list on the NAD device.

Node group doesnt give redundancy for dot1x or mab sessions. However, it is necessary to configure all PSN servers in the NAD list to make sure all sessions have redundancy in terms of authentication My answer is D

D If there is a failure of the Policy Services persona (and, therefore, RADIUS processing) or a failure of a single appliance, the NAD detects the failure of the RADIUS service on one of the PSNs and directs 100% of future RADIUS queries from that NAD to the remaining PSN. The availability, failover, and recovery detection criteria of the RADIUS service are configured on the NAD. Official Guide

The correct one is D. When you configure a switch for example, you configure the radius server list that the switch is going to use. Those radius servers are the PSNs nodes; when a node goes down the NAD device will use the other nodes configured on the server list.

Ok, onestly i was thinking about it, the answer could be A instead, here they are talking about the PSNs not about the NAD devices, so the redudancy that the question is mentioning is between the PSNs nodes. An ISE node group can be done when you have more PSNs in your building and both of them are in the same group.

Selected Answer: A Node Groups When two or more Policy Service Nodes (PSNs) are connected in an ISE deployment, it is recommended that they be placed in a node group. This design improves replication of endpoint profiling data by keeping less significant attributes local to the group and reducing the information that is replicated to the remote nodes in the network.

Selected Answer: A STOP Saying D!!! You are not looking at it from a NAD perspective but from a Server perspective. So it dosn't matter if NAD can have multiple servers.

Selected Answer: D PSN availability/failover is handled by configuring the NAD (switch/WLC) with multiple ISE PSNs as RADIUS servers or a load balancer VIP. Node Groups exist to share session/profiler data and to reset orphaned URL-redirected sessions via CoA, but they don’t provide client auth redundancy on their own—the NAD’s RADIUS list does.

Selected Answer: D I've configured several cisco switches for this. Unless you're using a third party load balancer, switches need the individual PSN's configured directly on the switch as radius servers.

Selected Answer: D High availability for PSNs is delivered by the NAD. The NAD is set up with a list of RADIUS servers. If the first server in the list is unreachable, the NAD moves to the next server in the list.