HPE6-A68 Exam Dumps - Aruba Certified ClearPass Professional (ACCP) 6.7

References: http://www.arubanetworks.com/techdocs/ClearPass/Aruba_DeployGd_HTML/Content/5%20Cluster%20Deployment/Design_guidelines.htm

C: Role Mappings Page - Rules Editor Page Parameters

D: Enforcement Policy Attributes tab Parameters

References:

http://www.arubanetworks.com/techdocs/ClearPass/Aruba_CPPMOnlineHelp/Content/CPPM_UserGuide/identity/RoleMappingPolicies.html

http://www.arubanetworks.com/techdocs/ClearPass/Aruba_CPPMOnlineHelp/Content/CPPM_UserGuide/PolicySim/PS_Enforcement_Policy.htm

OnGuard uses HTTPS to send posture information to the ClearPass appliance. For OnGuard to use HTTPS, it must have access to the network. If a customer requires 802.1x authentication on the wired switch, a separate 802.1x authentication must be used prior to the OnGuard posture check. In this example, an 802.1x PEAP-EAP-MSCHAPv2 authentication is completed first. A separate WebAuth service must be setup with posture checks to use the OnGuard agent.

References: MAC Authentication and OnGuard Posture Enforcement using Dell WSeries ClearPass and Dell Networking Switches (August 2013), page 21

A: Sponsored self-registration is a means to allow guests to self-register, but not give them full access until a sponsor (could even be a central help desk) has approved the request. When the registration form is completed by the guest/user, an on screen message is displayed for the guest stating the account requires approval.

Guests are disabled upon registration and need to wait on the receipt page for the confirmation until the login button gets enabled.

D. Device Mac Authentication is designed for authenticating guest devices based on their MAC address.

References: ClearPass Policy Manager 6.5 User Guide (October 2015), page 94

https://community.arubanetworks.com/aruba/attachments/aruba/SoftwareUserReferenceGuides/52/1/ClearPass%20Policy%20Manager%206.5%20User%20Guide.pdf

ClearPass Policy Manager allows you to designate one of the subscriber nodes in a cluster to be the Standby Publisher, thereby providing for that subscriber node to be automatically promoted to active Publisher status in the event that the Publisher goes out of service. This ensures that any service degradation is limited to an absolute minimum.

When a Publisher failure is detected, the designated subscriber node is promoted to active Publisher status.

References: http://www.arubanetworks.com/techdocs/ClearPass/Aruba_DeployGd_HTML/Content/5%20Cluster%20Deployment/Standby_publisher.htm

You can pre-provision with the Aruba controller firewall role of BYOD-Provision.

From the Firewall policies part of the exhibit, we see that the onboarding page is set to captive portal.

References: https://community.arubanetworks.com/t5/Security/CP-OnBoard-not-redirecting-to-portal-on-single-SSID/td-p/284506

The first rule will match, and the Remote Employee ACL will be used.

Policy Manager looks for the device or user by executing the first filter associated with the authentication source.

After the device or user is found, Policy Manager then authenticates this entity against this authentication

source. The flow is outlined below:

* On successful authentication, Policy Manager moves on to the next stage of policy evaluation, which

collects role mapping attributes from the authorization sources.

* Where no authentication source is specified (for example, for unmanageable devices), Policy Manager

passes the request to the next configured policy component for this service.

* If Policy Manager does not find the connecting entity in any of the configured authentication sources, it

rejects the request.

References: ClearPass Policy Manager 6.5 User Guide (October 2015), page 134

https://community.arubanetworks.com/aruba/attachments/aruba/SoftwareUserReferenceGuides/52/1/ClearPass%20Policy%20Manager%206.5%20User%20Guide.pdf

The Login page is the URL of the page that appears for the user logon. This can be set to any URL.

The Welcome page is the URL of the page that appears after logon and before redirection to the web URL. This can be set to any URL.

References: http://www.arubanetworks.com/techdocs/ArubaOS_63_Web_Help/Content/ArubaFrameStyles/Captive_Portal/Captive_Portal_Authentic.htm