WHY A IS False? |
CONCEPT: S3 object access |
This is distractor statement. By default, an S3 object is owned by the AWS account that uploaded it. So the S3 bucket owner will not implicitly have access to the objects written by the Redshift cluster
|
WHY B IS True? |
CONCEPT: S3 object access |
By default, an S3 object is owned by the AWS account that uploaded it.
This is true even when the bucket is owned by another account. Because the Amazon Redshift data files from the UNLOAD command were put into your bucket by another account, you (the bucket owner) don't have default permission to access those files. So the S3 bucket owner will not implicitly have access to the objects written by the Redshift cluster.
To get access to the data files, an AWS Identity and Access Management (IAM) role with cross-account permissions must run the UNLOAD command again. |
WHY C IS False? |
CONCEPT: S3 object access |
This is distractor statement. By default, an S3 object is owned by the AWS account that uploaded it. So the S3 bucket owner will not implicitly have access to the objects written by the Redshift cluster
|
WHY D IS False? |
CONCEPT: S3 object access |
This is distractor statement. By default, an S3 object is owned by the AWS account that uploaded it. So the S3 bucket owner will not implicitly have access to the objects written by the Redshift cluster
|
Short Trick |
As it is "UNLOAD command from the Redshift cluster " & "Amazon Redshift cluster provisioned in AWS account B"- so by default, you will not access to those files as By default, an S3 object is owned by the AWS account that uploaded it.
|
References: |
REFERNCED
DOCS
|