1Z0-997 Question #89: Real Exam Question with Answer & Explanation

Question

Options

• AYou are exceeding your volume group backup quota configured.
• BYou have the same block volume attached to multiple compute instances; if these compute instances are in different compartments then all concerned
• CCompute instance with multiple block volumes attached cannot move when a compartment is moved.
• DThe Identity and Access Management policy allowing backup failed to move when the compartment was moved.

Explanation

Explanation/Reference: VCN, it must first be empty and have no related resources or attached gateways To delete a VCN's subnets, they must first be empty. Note: When you create one of the preceding resources, you specify a VCN and subnet for it. The relevant service creates at least one VNIC in the subnet and attaches the VNIC to the resource. The service manages the VNICs on your behalf, so they are not readily apparent to you in the Console. The VNIC enables the resource to communicate with other resources over the network. Although this documentation commonly talks about the resource itself being in the subnet, it's actually the resource's attached VNIC. If the subnet is not empty, you instead get an error indicating that there are still resources that you must delete first. The error includes the OCID of a VNIC that is in the subnet (there could be more, but the error returns only a single VNIC's OCID). You can use the Oracle Cloud Infrastructure command line interface (CLI) or another SDK or client to call the GetVnic operation with the VNIC OCID. The response includes the VNIC's display name. Depending on the type of parent resource, the display name can indicate which parent resource the VNIC belongs to. You can then delete that parent resource, or you can contact your administrator to determine who owns the resource. When the VNIC's parent resource is deleted, the attached VNIC is also deleted from the subnet. If there are remaining VNICs in the subnet, repeat the process of determining and deleting each parent resource until the subnet is empty. Then you can delete the subnet. For example, if you're using the CLI, use this command to get information about the VNIC. oci network vnic get --vnic-id <VNIC_OCID are moved under different parent compartments, and you notice that sometimes volume group backup fails. What could be the cause? compartments must be moved at the same time. Explanation/Reference: You can move a compartment to a different parent compartment within the same tenancy. When you move a compartment, all its contents (subcompartments and resources) are moved with it. Moving a compartment has implications for the contents. After you move a compartment to a new parent compartment, the access policies of the new parent take effect and the policies of the previous parent no longer apply. Before you move a compartment, ensure that: You are aware of the policies that govern access to the compartment in its current position. You are aware of the polices in the new parent compartment that will take effect when you move the compartment. In some cases, when moving nested compartments with policies that specify the hierarchy, the polices are automatically updated to ensure consistency.

No community discussion yet for this question.