Agreed. This is from the page you shared...
"Cisco ISE queries the MDM servers for the necessary device attributes to create ACLs that provide network access control for those devices."
And in the section (Configuring ACLs on the Wireless LAN Controller for Mobile Device Management Interoperability)...
Step 3
Allow access to the MDM server for unregistered and noncompliant devices to download the MDM agent and proceed with compliance checks.
Step 4
Allow all inbound traffic from the client to the server to Cisco ISE for the web portal and supplicant, and certificate provisioning flows.
A. It provides compliance checks for access to the network.
The benefit of integrating Cisco ISE with a Mobile Device Management (MDM) solution is that it provides compliance checks for access to the network. This integration allows for the enforcement of security policies for mobile devices accessing the network. The MDM solution provides information about the device, such as its operating system version, security patch level, and any other security-related information. Cisco ISE can then use this information to determine if the device meets the organization's security policies, and either grant or deny access to the network based on the results of this compliance check. This integration helps to ensure that only compliant and secure devices are allowed access to the network, enhancing the overall security posture of the organization.
MDM helps is deploying company policy on BYOD mobile devices/tablets. The ISE when integrated with MDM will ensure that the mobile devices are compliant as per the company policy and ISE will permit/block based on the response received from the MDM
Guys it is D.
A is not correct because MDM should not give access to the network when the devices are non compliant.
This is only possible because of the option D:
https://cdw-prod.adobecqms.net/content/dam/cdw/on-domain-cdw/brands/cisco/ise-solution-overview.pdf
"4.Network admin access control. ISE is the only
NAC solution that includes TACACS+ for role-based
administrative access control to networking equipment"
this should be a because if you implement MDM integration wiht ISE you can check in the Policy if the Mobile device is complianted from MDM perspective and either allow or deny access based on the answer the MDM is delivering to ISE back
https://community.cisco.com/t5/security-documents/cisco-ise-integration-with-mobile-device-management-mdm/ta-p/3784691
The following are the high level use cases in this solution.
Device registration- Non registered endpoints accessing the network on-premises will be redirected to registration page on MDM server for registration based on user role, device type, etc
Remediation- Non compliant endpoints will be given restricted access based on compliance state
Periodic compliance check – Periodically check with MDM server for compliance
Ability for ISE administrators to issue remote actions on the device through the MDM server (e.g.: remote wiping of the managed device)
Ability for end user to leverage the ISE My Devices Portal to manage personal devices, e.g. Full Wipe, Corporate Wipe and PIN Lock.
This section is not available anymore. Please use the main Exam Page.350-701 Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
jaciro11
Highly Voted 2 years, 5 months agoidto
2 years, 5 months agoidto
2 years, 5 months agoCokamaniako
Most Recent 10 months agosull3y
1 year, 2 months agogetafix
1 year, 11 months agocoentror
2 years, 5 months agocoentror
2 years, 5 months agoMoII
2 years, 5 months agojccastiyo
2 years, 5 months agojaciro11
2 years, 5 months agozeroC00L
2 years, 8 months agobirdman6709
2 years, 8 months agoSarbi
2 years, 8 months agoMax95
2 years, 8 months ago