Red Hat EX362 Dumps (V8.02) to Pass Red Hat Certified Specialist in Identity Management Exam Quickly: Check EX362 Free Dumps (Part 1, Q1-Q40) Online

1. Automate creating an HTTP SSO client with Ansible using the freeipa.ansible_freeipa collection, then drop an httpd conf.

2. Re-enroll a previously enrolled but broken client cleanly.

3. Enroll a client using a pre-provisioned host keytab (no admin password on the client).

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

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

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

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

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

9. Configure the client to prefer a specific IdM server and fallback to replica if needed.

10. Configure SSH authorized keys from IdM (not strictly Kerberos, but client-side IdM integration).

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

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

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

14. 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.

15. Make an IdM Web UI SSO test: access https://ipa1.example.com/ipa/ui/ with SPNEGO instead of form login.

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

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

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

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

20. Protect Apache on the client with Kerberos SSO for /secure/ using mod_auth_gssapi.

21. Configure IdM automount maps on the client to auto-mount /home via IdM.

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

23. Enroll a client using a one-time host password (OTP) pre-created in IdM.

24. 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.

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

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

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

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

29. Create a service keytab for a custom daemon on app1 that needs Kerberos to call an HTTP backend.

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

31. Tune SSSD on the client to enable sudo and SSH responders and add SSSD to sudoers resolution.

32. Create a lightweight SSO health-check that fails if SPNEGO isn’t working.

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

34. Enroll a fresh RHEL 9 host app1.example.com as an IdM client with home-dir auto-creation and chrony time sync.

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

36. Set up Kerberized curl health check from the client to verify a web service protected by SPNEGO.

37. Troubleshoot SSO failure due to SELinux keytab access.

38. Enroll a client without DNS discovery (no SRV records reachable). Force server/realm explicitly.

39. 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.

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