The correct options are Customize attribute mappings between on-premises accounts and cloud directory objects, Add scoping filters to synchronize selected organizational units and groups, and Run on-demand provisioning tests by applying changes to a single account.

Customize attribute mappings between on-premises accounts and cloud directory objects is supported because provisioning solutions let administrators map which on-premises attributes populate which cloud attributes. This capability lets you rename attributes, transform values, and supply constants or default values so cloud accounts match your directory schema and business rules.

Add scoping filters to synchronize selected organizational units and groups is supported because administrators commonly need to limit which objects are provisioned. Scoping filters or selection rules let you target specific OUs or group memberships so only the intended user and group objects are synchronized to the cloud directory.

Run on-demand provisioning tests by applying changes to a single account is supported because most cloud sync tools provide a way to preview or test provisioning with a single account before broadly applying changes. This helps validate mapping and scoping rules and reduces the risk of unintended updates.

Automatically repair all synchronization errors without administrator intervention is incorrect because provisioning systems can report, retry, and sometimes suggest fixes for errors but they do not safely resolve every type of synchronization error automatically. Many errors require administrator review and remediation to ensure data integrity and to avoid unintended consequences.

Full AWS Practitioner Certification Question