Which configurations will block the creation of a global table or the creation of a replica in the new Region?
(Choose two.)
A global secondary index with the same partition key but a different sort key exists in the new Region where replication is desired.
An empty table with the same name exists in the Region where replication is desired.
No role with the dynamodb:CreateGlobalTable permission exists in the account.
DynamoDB Streams is enabled for the table.
The table is encrypted using a KMS customer managed key.
Explanations:
The global secondary index with a different sort key does not block the creation of a global table. Global tables can have different indexes in each region.
The existence of an empty table with the same name in the new region will block the creation of a global table. The global table creation process requires that the table in the new region be empty.
A missing role with thedynamodb:CreateGlobalTablepermission will block the creation of a global table, as this permission is necessary to create global tables.
DynamoDB Streams being enabled does not block the creation of global tables. Global tables rely on DynamoDB Streams to replicate changes.
The table being encrypted with a KMS customer managed key does not block the creation of a global table. However, proper KMS permissions are needed to allow replication.
I sort that the answer is:
An empty table with the same name exists in the Region where replication is desired.