Question 47 - HPE6-A84 discussion

The Window CA issues certificates to domain computers, domain users, and servers such as domain controllers. An example of a certificate issued by the Windows CA is shown here.The company is in the process of adding Microsoft Endpoint Manager (Intune) to manage its mobile clients. The customer is maintaining the on-prem AD for now and uses Azure AD Connect to sync with Azure AD.# Requirements for issuing certificates to mobile clientsThe company wants to use ClearPass Onboard to deploy certificates automatically to mobile clients enrolled in Intune. During this process, Onboard should communicate with Azure AD to validate the clients. High availability should also be provided for this scenario; in other words, clients should be able to get certificates from Subscriber 2 if Subscriber 1 is down.The Intune admins intend to create certificate profiles that include a UPN SAN with the UPN of the user who enrolled the device.# Requirements for authenticating clientsThe customer requires all types of clients to connect and authenticate on the same corporate SSID.The company wants CPPM to use these authentication methods:EAP-TLS to authenticate users on mobile clients registered in IntuneTEAR, with EAP-TLS as the inner method to authenticate Windows domain computers and the users on themTo succeed, EAP-TLS (standalone or as a TEAP method) clients must meet these requirements:Their certificate is valid and is not revoked, as validated by OCSPThe client's username matches an account in AD# Requirements for assigning clients to rolesAfter authentication, the customer wants the CPPM to assign clients to ClearPass roles based on the following rules:Clients with certificates issued by Onboard are assigned the "mobile-onboarded" roleClients that have passed TEAP Method 1 are assigned the "domain-computer" roleClients in the AD group "Medical" are assigned the "medical-staff" roleClients in the AD group "Reception" are assigned to the "reception-staff" roleThe customer requires CPPM to assign authenticated clients to AOS firewall roles as follows:Assign medical staff on mobile-onboarded clients to the "medical-mobile" firewall roleAssign other mobile-onboarded clients to the "mobile-other" firewall roleAssign medical staff on domain computers to the "medical-domain" firewall roleAll reception staff on domain computers to the "reception-domain" firewall roleAll domain computers with no valid user logged in to the "computer-only" firewall roleDeny other clients' access# Other requirementsCommunications between ClearPass servers and on-prem AD domain controllers must be encrypted.# Network topologyFor the network infrastructure, this customer has Aruba APs and Aruba gateways, which are managed by Central. APs use tunneled WLANs, which tunnel traffic to the gateway cluster. The customer also has AOS-CX switches that are not managed by Central at this point.# ClearPass cluster IP addressing and hostnamesA customer's ClearPass cluster has these IP addresses:Publisher = 10.47.47.5Subscriber 1 = 10.47.47.6Subscriber 2 = 10.47.47.7Virtual IP with Subscriber 1 and Subscriber 2 = 10.47.47.8The customer's DNS server has these entriescp.acnsxtest.com = 10.47.47.5cps1.acnsxtest.com = 10.47.47.6cps2.acnsxtest.com = 10.47.47.7radius.acnsxtest.com = 10.47.47.8onboard.acnsxtest.com = 10.47.47.8You have created a role mapping policy as shown in the exhibits below.What is one change that you need to make to this policy?