Cisco Exam 300-715 Topic 11 Question 65 Discussion

Actual exam question for Cisco's 300-715 exam

Question #: 65
Topic #: 11

An engineer is configuring Cisco ISE policies to support MAB for devices that do not have 802.1X capabilities. The engineer is configuring new endpoint identity groups as conditions to be used in the AuthZ policies, but noticed that the endpoints are not hitting the correct policies. What must be done in order to get the devices into the right policies?

AManually add the MAC addresses of the devices to endpoint ID groups in the context visibility database.

BCreate an AuthZ policy to identify Unknown devices and provide partial network access prior to profiling.

CAdd an identity policy to dynamically add the IP address of the devices to their endpoint identity groups.

DIdentify the non 802.1X supported device types and create custom profiles for them to profile into.

Show Suggested Answer

Suggested Answer: D, E

by Johnna at Feb 03, 2023, 07:48 PM

Limited Time Offer

25%

Off

Get Premium 300-715 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Horace

2 months ago

I'm just gonna go with D and hope I don't get any of those 'non-802.1X' devices in my network. That's like trying to configure a VCR these days.

upvoted 0 times

Dusti

14 days ago

User3: Agreed, custom profiles will definitely help with those devices.

upvoted 0 times

...

Fletcher

18 days ago

User2: Yeah, that sounds like the best option to avoid any issues.

upvoted 0 times

...

Rhea

22 days ago

User1: I think D is the way to go, custom profiles for non-802.1X devices.

upvoted 0 times

...

Gladis

2 months ago

Dynamically adding IP addresses to endpoint groups? That's straight out of the 90s, man. This is Cisco ISE, we're all about that MAB now!

upvoted 0 times

Miss

5 days ago

D) Identify the non 802.1X supported device types and create custom profiles for them to profile into.

upvoted 0 times

...

Abel

7 days ago

B) Create an AuthZ policy to identify Unknown devices and provide partial network access prior to profiling.

upvoted 0 times

...

Twana

8 days ago

A) Manually add the MAC addresses of the devices to endpoint ID groups in the context visibility database.

upvoted 0 times

...

Florinda

12 days ago

D) Identify the non 802.1X supported device types and create custom profiles for them to profile into.

upvoted 0 times

...

Veronique

19 days ago

B) Create an AuthZ policy to identify Unknown devices and provide partial network access prior to profiling.

upvoted 0 times

...

Leigha

1 months ago

A) Manually add the MAC addresses of the devices to endpoint ID groups in the context visibility database.

upvoted 0 times

...

Vi

2 months ago

Wait, what? Unknown devices get partial network access? That sounds like a security nightmare! I'm gonna go with option D, it's the safest bet.

upvoted 0 times

Louvenia

29 days ago

I agree, it's important to properly identify and profile those devices to ensure network security.

upvoted 0 times

...

Lillian

2 months ago

Option D is a good choice, creating custom profiles for non 802.1X supported devices is a secure approach.

upvoted 0 times

...

Dana

2 months ago

Is this a trick question? I mean, why not just manually add the MAC addresses to the endpoint ID groups? Seems like the easiest solution.

upvoted 0 times

Lottie

1 months ago

D) Identify the non 802.1X supported device types and create custom profiles for them to profile into.

upvoted 0 times

...

Mariko

1 months ago

C) Add an identity policy to dynamically add the IP address of the devices to their endpoint identity groups.

upvoted 0 times

...

Danica

2 months ago

B) Create an AuthZ policy to identify Unknown devices and provide partial network access prior to profiling.

upvoted 0 times

...

Cheryll

2 months ago

A) Manually add the MAC addresses of the devices to endpoint ID groups in the context visibility database.

upvoted 0 times

...

Carissa

2 months ago

Ah, finally a MAB-related question! I've been preparing for this. I think option D is the way to go - identifying the non-802.1X devices and creating custom profiles for them. That way, they'll get the right policies applied.

upvoted 0 times

...