Which three AMQP configurations should be considered to meet these requirements?

An Architect is working to implement Adobe Commerce into a pre-built ecosystem in a company.

Communication between different company domains uses event-driven design and is driven via AMQP protocol with usingRabbitMQ.

The Architect needs to establish the data flow between the ERP system and Adobe Commerce.

The ERP system stores only customer data excluding customer addresses.

The role of Adobe Commerce is to provide Customer Address data to the enterprise ecosystem.

Primary Customer data should not be changed from Adobe Commerce side; it should only be updated by messages data from ERP.

Which three AMQP configurations should be considered to meet these requirements? (Choose three.)
A . Create a queue_consumer.xml and communction.xml configuration files for Customer data messages
B. Create a queue_publisher.xml configuration file for Customer data messages
C. Create a nueue_publisher.xml configuration file for Customer Address messages
D. Create a queue_topology.xml configuration file for Customer Address messages
E. Create a queue_topology.xmlconfiguration file for Customerdata messages
F. Create a queue_customer.xml and communication.xml configuration files for Customer Address messages

View Answer

Answer: C,D,F

Explanation:

Based on web searches, it seems that Adobe Commerce uses different XML configuration files to define various aspects of message queues, such as consumers, publishers, and topology123.

According to the documentation3, queue_consumer.xml defines the relationship between an existing queue and its consumer, which is a class that processes messages from a queue. queue_publisher.xml defines the exchange where a topic is published, which is a name that identifies a message for routing. queue_topology.xml defines the message routing rules and declares queues and exchanges.

Based on these definitions, I would say that three possible AMQP configurations that should be considered to meet the requirements are:

✑ C. Create a queue_publisher.xml configuration file for Customer Address messages

✑ D. Create a queue_topology.xml configuration file for Customer Address messages

✑ F. Create a queue_consumer.xml and communication.xml configuration files for Customer Address messages