Question:The administrator creates an S3 bucket as the backup target.

The error message explicitly references anobject-lock enabled bucketand restrictions onmodifying/deleting objects. This points directly to theWORM (Write Once Read Many)feature being enabled on the S3 bucket.

WORM (Object Lock):

Object Lock (also called WORM)prevents objects from being deleted or modifiedfor a retention period set by the bucket’s policy.

The error states:

“An object from the object-lock enabled bucket can not be modified or deleted unless the retention period is elapsed.”

This directly matches the behavior of an S3 bucket withWORM retention.

The other options:

A. Bucket name incorrect: Would result in a “NoSuchBucket” or “Not Found” error, not “Method Not Allowed.”

C. Object-Level permissions: Insufficient permissions would cause “Access Denied” or “Forbidden,” not WORM-specific errors.

D. API key misconfiguration: Would typically produce authentication errors (“SignatureDoesNotMatch,” etc.), not a WORM policy restriction.

The NUSA course discusses WORM behavior:

“If WORM is enabled on a bucket, objects cannot be deleted or modified until the retention period expires. Attempting to do so will generate ‘Method Not Allowed’ errors.”

Thus, the error here is directly caused byWORM retention(Object Lock) being active on the S3 bucket.