Final answer:
The 'Audit' and 'AuditIfNotExists' Policy Effects are used to monitor compliance in cloud services. 'Audit' scrutinizes resources for compliance and logs the status, while 'AuditIfNotExists' ensures specific configurations exist; it logs and can initiate compliance actions.
Step-by-step explanation:
The 'Audit', 'AuditIfNotExists' Policy Effect in the context of cloud services, such as Microsoft Azure, is used to evaluate and monitor compliance with the organization's standards and regulations. When an 'Audit' policy is applied, it inspects resources to check if they comply with the policy rules. It does not change the state of the resource but logs the compliance status. On the other hand, 'AuditIfNotExists' checks if a specific resource configuration exists, and if it does not, it will log this as a non-compliant resource. However, unlike the 'Audit' effect, 'AuditIfNotExists' also provides the option to deploy the necessary changes to make the resource compliant, typically through a remediation task or the deployment of a related resource that will allow the policy to be fulfilled.