MENU
You are using JDBC source connector to copy data from a table to Kafka topic. There is one connector created with max.tasks equal to 2 deployed on a cluster of 3 workers. How many tasks are launched?
Suggested Answer: C
Get Premium CCDAK Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
JDBC connector allows one task per table.
14 comments · newest first
MA
Maybelle
11 months ago
I thought it would scale with workers, but I guess not!
WA
Wayne
11 months ago
Yup, definitely 2 tasks.
JO
Joaquin
12 months ago
Wait, why not 3? That seems odd.
CY
Cyril
12 months ago
Totally agree, max.tasks limits it!
DU
Dulce
12 months ago
Only 2 tasks will be launched.
OD
Odette
1 year ago
Wait, does the number of workers affect how many tasks are launched? I might be mixing that up with something else.
GE
Gearldine
1 year ago
I practiced a similar question, and I believe the answer is 2 because that's what max.tasks specifies.
LA
Lavonne
1 year ago
I’m not entirely sure, but I remember something about tasks being limited by the max.tasks value, not the number of workers.
AL
Allene
1 year ago
I think the max.tasks setting determines how many tasks can run, so it should be 2, right?
RE
Rex
1 year ago
Okay, let's see. The question is asking about objects that support the connection between PPM and PS. I'm guessing the PS profile and PS network are the two correct answers.
MO
Mozell
1 year ago
Hmm, this one looks tricky. The iRule is checking the local port, but the question says the user is connecting to port 22. I'll need to think this through carefully.
UL
Ula
1 year ago
Hmm, I'm a bit unsure about the correct order here. I'll need to carefully review the steps and think through the logical sequence.
JO
Joesph
1 year ago
I think I've seen this operation before, but I'm not totally sure which one is the correct answer. I'll need to review my notes to refresh my memory.
VI
Vicky
1 year ago
I'm not entirely sure, but I think I/O throttling might be the best answer here. That's when the system intentionally limits the I/O rate to prevent overloading, which could explain the high number of writes.