Correct Answer: B
The AWS Documentation gives an example of such a case.
Inline policies are useful if you want to maintain a strict one-to-one relationship between a policy and the principal entity that it`s applied to. For example, you want to be sure that the permissions in a policy are not inadvertently assigned to a principal entity other than the one they`re intended for. When you use an inline policy, the permissions in the policy cannot be inadvertently attached to the wrong principal entity. In addition, when you use the AWS Management Console to delete that principal entity, the policies embedded in the principal entity are deleted as well. That`s because they are part of the principal entity.
Option A is invalid because AWS Managed Policies are ok for a group of users. But for individual users, inline policies are better.
Options C and D are invalid because they are specifically meant for access to S3 buckets.
For more information on policies, please visit the following URL-
https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_managed-vs-inline.html