What is the correct sequence of steps involved in scheduling a threat intelligence program?
1. Review the project charter
2. Identify all deliverables
3. Identify the sequence of activities
4. Identify task dependencies
5. Develop the final schedule
6. Estimate duration of each activity
7. Identify and estimate resources for all activities
8. Define all activities
9. Build a work breakdown structure (WBS)
Suggested Answer: A
Get Premium 312-85 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
11 comments · newest first
EV
Evangelina
12 months ago
Are we sure about the sequence? Seems complicated!
TI
Tiara
12 months ago
Totally agree with D, it's the logical flow.
GW
Gwenn
12 months ago
Wait, why is WBS last? That seems off.
EU
Eun
1 year ago
I think option D makes the most sense.
CA
Cassie
1 year ago
Gotta start with the project charter!
CO
Corrinne
1 year ago
I’m a bit confused about the sequence. I thought defining activities was crucial before building the schedule, but I can't recall the exact order.
SH
Sharee
1 year ago
I remember practicing a similar question where we had to build a work breakdown structure early on. I feel like that might come before estimating resources.
FE
Felicidad
1 year ago
I think we start with reviewing the project charter, but I'm not sure if that comes before identifying deliverables or after.
KA
Kaitlyn
1 year ago
I believe the correct order is to first identify all deliverables and then define activities, but I’m not completely confident about that.
SH
Shalon
1 year ago
Ah, I see what they're getting at here. East-west traffic within a private cloud is critical to protect because that's where the majority of the sensitive data and application communication is happening. Gotta make sure that's locked down.
GL
Glenn
1 year ago
I'm leaning towards the 15-digit contact ID, but I'm not 100% confident. I'll make a note to review the Salesforce and Marketing Cloud integration documentation before answering.