A serverless app in one Region publishes URLs via an Amazon SNS topic to an Amazon SQS queue. An AWS Lambda function uses that SQS queue as an event source, fetches each URL, extracts metadata, and writes results to an Amazon S3 bucket in the same Region. The company wants to run the same URL processing in additional Regions (to compare localized site differences), but all URLs must be published from the existing Region and all output must be written to the original S3 bucket in the current Region. Which combination of changes will create a multi-Region deployment that satisfies these requirements? (Choose two.)

To process URLs in additional Regions while publishing from the existing Region and writing output to the original S3 bucket, you need to extend the processing pipeline. First, "Deploy an SQS queue and the Lambda function into the other Regions so processing can run there" is correct because each new Region needs its own SQS queue to receive messages and a Lambda function to process them. This allows for localized processing. Second, "In each additional Region, create an SQS queue and subscribe that regional SQS queue to the existing SNS topic" is correct. The existing SNS topic in the original Region can publish messages to SQS queues in other Regions. This ensures all URLs are published from the existing Region and distributed to the new processing Regions. "Subscribe the SNS topic (in each Region) to the SQS queue" is incorrect because the SNS topic is the publisher, not the subscriber. "Configure the SQS queue to publish URLs to SNS topics in each Region" is incorrect; the SQS queue is a consumer of messages from SNS. "Deploy the SNS topic and the Lambda function into the other Regions" is incorrect because the SNS topic should remain centralized in the original Region to publish all URLs from there.