Add Tags to Identify Owners of Compute Instances
Question
You have multiple IAM users who launch different types of compute instances and block volumes every day.
As a result, your Oracle Cloud Infrastructure (OCI) tenancy quickly hit the service limit and you can no longer create any new instances.
As you are cleaning up the environment, you notice that the majority of the instances and block volumes are untagged.
Therefore, it is difficult to pinpoint the owner of these resources and verify if they are safe to terminate.
Because of this, your company has issued a new mandate, which requires adding a predefined set of tags to identify owners before launching compute instances.
Which option is the simplest way to implement this new requirement? (Choose the best answer.)
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D. E.E.
https://docs.cloud.oracle.com/en-us/iaas/Content/Tagging/Tasks/managingtagdefaults.htmThe simplest way to implement the new requirement of adding predefined set of tags to identify owners before launching compute instances would be to create a policy using IAM requiring users to tag specific resources. This will allow a user to launch compute instances only if certain tags were defined.
Option A suggests creating tag variables to automatically tag a resource with the user name. While this may seem like a good solution, it would not necessarily ensure that the correct owner is identified for each resource. Additionally, it would require updating the tag variable every time a new user is added to the system, which could be time-consuming and error-prone.
Option B suggests creating a policy to automatically tag a resource with the user name. However, this option is not possible because policies cannot add tags to resources.
Option C is the best choice because it requires users to tag specific resources, such as compute instances, before they can be launched. This ensures that each resource has an owner identified and makes it easier to clean up resources that are no longer needed.
Option D suggests creating tag variables for each compartment to automatically tag a resource with the user name. While this may be useful in identifying the owner of resources, it would still require manually assigning tags to each resource, which is not the simplest solution.
Option E suggests creating a default tag for each compartment, which ensures that appropriate tags are applied at resource creation. However, this option does not guarantee that the correct owner is identified for each resource, and it would still require manually assigning tags to each resource.
In summary, option C is the simplest way to implement the new requirement of adding predefined set of tags to identify owners before launching compute instances. This option requires users to tag specific resources, such as compute instances, before they can be launched, making it easier to clean up resources that are no longer needed and ensuring that each resource has an identified owner.
