EX362 Red Hat Certified Specialist in Identity Management exam Free Dumps

dumps2025-09-08T09:55:51+08:00

EX362 Red Hat Certified Specialist in Identity Management exam is easy to take now. EX362 exam is a performance-based evaluation of skills and knowledge required to configure and manage Red Hat directory services. EX362 exam consists of a single section lasting three hours. Performance-based testing means that candidates must perform tasks similar to what they perform on the job. We provide Red Hat Certified Specialist in Identity Management EX362 exam dumps, which can ensure you pass the test easily. Free Red Hat Certified Specialist in Identity Management EX362 exam dumps are available below.

Page 1 of 4

1. You must deploy a brand-new IdM realm using scripts on RHEL 9. Use integrated DNS and set Google Public DNS as a forwarder. Primary server: ipa1.example.com (10.10.10.11). Realm: EXAMPLE.COM, domain: example.com. Ensure services start at boot and verify the install.

See the Explanation.

2. Install the same IdM primary using Ansible Automation Platform (AAP) and the freeipa.ansible_freeipa collection, with integrated DNS and a forwarder.

See the Explanation.

3. Install an IdM server with external DNS (no integrated DNS). Configure global DNS forwarders afterwards from IdM.

See the Explanation.

4. Perform a CA-less IdM deployment using an external corporate CA. Complete the two-stage process.

See the Explanation.

5. Enroll a RHEL client app1.example.com into the IdM realm, configure SSSD, and verify identity and sudo data retrieval.

See the Explanation.

6. Create a replica named ipa2.example.com (10.10.10.12) with CA and DNS using scripts. Ensure it forms a ring topology with the primary.

See the Explanation.

7. Install the same replica using Ansible with ipareplica role, also enabling KRA (for key escrow).

See the Explanation.

8. Configure a conditional DNS forward zone in IdM DNS so that queries for corp.local go to 10.20.20.53.

See the Explanation.

9. Create three users (alice, bob, carol) and a POSIX group webadmins with GID 30010. Add all three to the group.

See the Explanation.

10. Bulk-create users from a CSV using Ansible and the ipa_user role.

See the Explanation.

Page 2 of 4

11. Create an HBAC policy that allows only members of webadmins to SSH into hosts in hostgroup webservers.

See the Explanation.

12. Create a sudo rule permitting members of dbas group to run systemctl start postgresql and systemctl stop postgresql on hosts in dbservers.

See the Explanation.

13. Apply a password policy for group contractors: minimum length 12, lock the account after 5 failures within 5 minutes, and keep it locked for 15 minutes.

See the Explanation.

14. Automatically place any user whose departmentNumber equals WebOps into webadmins using automember and rebuild existing entries.

See the Explanation.

15. Use staged users to onboard jsmith and then activate the account into the directory.

See the Explanation.

16. Create an RBAC model so Helpdesk members can reset user passwords but cannot modify other attributes.

See the Explanation.

17. Enable OTP (2FA) for user alice and globally for the domain. Create a TOTP token and test login with password+OTP.

See the Explanation.

18. Gracefully decommission a replica ipa2.example.com (keeping the domain healthy) and remove it from topology and DNS.

See the Explanation.

19. Add a new replication segment directly between ipa1 and a third server ipa3 to form a triangle topology.

See the Explanation.

20. Using Ansible, create group secops, add existing users alice and bob, and attach an HBAC rule that allows secops to SSH to secnodes hostgroup.

See the Explanation.

Page 3 of 4

21. Create an Apache (httpd) SSO client on web1.example.com using FreeIPA/IdM as KDC. Protect /secure/ with Kerberos SSO (SPNEGO).

See the Explanation.

22. Add HTTPS to your Apache SSO client and ensure SPNEGO also works over TLS.

See the Explanation.

23. Protect only /secure/ with SSO but leave / public; confirm forced negotiate only on the secure path.

See the Explanation.

24. Add multiple SPNs for a vhost with aliases (web.example.com and web1.example.com) and load both into the same keytab.

See the Explanation.

25. Put Apache (SSO) in front of a backend app (Tomcat on 8080). Do SSO at Apache and proxy to Tomcat.

See the Explanation.

26. Configure SSH SSO (GSSAPI) from a client ws1 to server app1―no password prompts for IdM users.

See the Explanation.

27. Verify SSH SSO using Kerberos tickets only―disable password auth temporarily for an IdM group.

See the Explanation.

28. Delegate safe keytab retrieval to a non-admin “service owner” so they can (re)fetch only HTTP/web1.example.com.

See the Explanation.

29. Rotate the HTTP service key (keytab) with near-zero downtime.

See the Explanation.

30. Enable Kerberos SSO to PostgreSQL (db1.example.com) for IdM users.

See the Explanation.

Page 4 of 4

31. Verify HTTP SSO at the protocol level using SPNEGO―collect a service ticket for HTTP/web1.example.com.

See the Explanation.

32. Configure browsers for seamless SSO to *.example.com.

See the Explanation.

33. Build an SSO edge with Apache in front of NGINX app on localhost:8081―Apache performs SPNEGO, NGINX serves content.

See the Explanation.

34. Expose authenticated username to the backend app via headers (so the app knows who the user is).

See the Explanation.

35. Enable OK-AS-DELEGATE for a web service so browsers can forward delegated credentials to it (needed for KCD/S4U).

See the Explanation.

36. Configure Kerberos Constrained Delegation (KCD) so the web tier can access LDAP on behalf of users.

See the Explanation.

EX362 Red Hat Certified Specialist in Identity Management exam Free Dumps

EX362 Red Hat Certified Specialist in Identity Management exam Free Dumps

Share this post

Related Posts