Which of the following would successfully accomplish this task?
Creating multiple pipeline definition files
Defining multiple pipeline definitions in your schedule objects file and associating the desired schedule to the correct activity via its schedule field
Defining multiple schedule objects in your pipeline definition file and associating the desired schedule to the correct activity via its schedule field
Defining multiple schedule objects in the schedule field
Explanations:
AWS Data Pipeline does not support multiple pipeline definition files for different schedules within a single pipeline.
You cannot define multiple pipeline definitions in a schedule objects file; pipeline definitions and schedules must be managed within the pipeline definition file.
AWS Data Pipeline allows defining multiple schedule objects in a single pipeline definition file and associating each schedule to the desired activity via the schedule field.
The schedule field cannot contain multiple schedule objects directly. Each schedule field should reference only one schedule object per activity.
I assess that the answer is:
Defining multiple schedule objects in your pipeline definition file and associating the desired schedule to the correct activity via its schedule field
I would say the answer is:
Defining multiple schedule objects in your pipeline definition file and associating the desired schedule to the correct activity via its schedule field