After assigning a new policy initiative that uses Append to add a tag on resource creation, you notice some recently created resources are missing the tag. What explains this behavior?
A. Append only adds or modifies properties during resource write operations, so resources created before or outside of that write path may not receive the tag until updated.
B. Append applies retroactively to all existing resources immediately, so missing tags indicate the policy assignment failed entirely across the initiative.
C. Append runs as a scheduled background job that takes several days to propagate tags to new resources, so wait for the compliance job to finish.
D. Append removes existing tags and replaces them with default values, so resources missing tags likely had a naming conflict with another policy.
Append acts during resource write operations and won't add tags to resources created previously or by paths that bypass the write; it isn't retroactive or delayed by days.