What considerations should an integration architect remember regarding Apex REST services?

Apex REST services are designed for creating custom RESTful web services in Salesforce, allowing developers to expose Apex methods so they can be called as web service endpoints. When considering the correct choice, it is important to understand key characteristics of these services.

The statement about requiring unit and functional testing emphasizes the importance of ensuring that any code, including Apex REST services, is thoroughly tested to guarantee that it operates correctly and meets the specified requirements. Unit tests provide developers with the confidence that their code behaves as expected, while functional testing ensures that the services work well in the context of the applications they support.

Additionally, Apex REST services are indeed built programmatically, which means they require coding and cannot be created using declarative tools available in Salesforce. This aspect highlights the need for solid development skills and code management approaches to effectively create and maintain these services.

While REST and SOAP APIs can consume API limits, this particular option inaccurately claims that Apex REST specifically consumes more limits than another option, without sufficient context. It is essential to realize that all API calls are subject to the same limits and there is no clear comparison regarding consumption just between REST and SOAP APIs.

The option about publisher actions is focused on a specific capability of Salesforce's user interface customization rather than integration architecture.