Halloween Special 2026! Get Up to 25% OFF Practice Questions! Limited Time - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

EC-Council 712-50 Exam - Topic 6 Question 91 Discussion

Posted by Truman on Sep 11, 2024 at 01:59 AM

SCENARIO: A CISO has several two-factor authentication systems under review and selects the one that is most sufficient and least costly. The implementation project planning is completed and the teams are ready to implement the solution. The CISO then discovers that the product it is not as scalable as originally thought and will not fit the organization's needs.

What is the MOST logical course of action the CISO should take?

Suggested Answer: D

Get Premium 712-50 Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test
39 comments · newest first
GA
Gail 11 months ago
Wait, I can't believe the product isn't scalable! How did that happen?
CH
Cherry 11 months ago
D sounds extreme, but maybe necessary if it's not compliant.
WI
Winfred 11 months ago
C seems risky, why wait for validation?
KI
Kirk 12 months ago
I disagree, B could work if the vendor is reliable.
QU
Queen 12 months ago
A is definitely the way to go, better to reassess now.
YO
Yong 1 year ago
Option D seems a bit extreme. I mean, if the internal requirements are valid, shouldn't we still explore other options before canceling the project?
CH
Chun 1 year ago
I feel like we practiced a similar question where we had to weigh immediate implementation against long-term viability. I think option C might be too cautious, but I'm not completely confident.
TO
Torie 1 year ago
I'm not entirely sure, but I think option B could be risky. If the vendor can't deliver on scalability, we might end up with a solution that doesn't work for us.
JO
Joye 1 year ago
I remember discussing the importance of scalability in our last class. I think option A makes the most sense since we need a solution that fits our long-term needs.
LA
Lai 1 year ago
Cancelling the project if it's not required for regulatory compliance is an interesting option. Might be worth exploring if the business need isn't critical.
CU
Curtis 1 year ago
I'm not sure I'd want to wait for an auditor or third party to validate the scalability issue. That could take a while and delay the project further.
FL
Floyd 1 year ago
Hmm, continuing with the implementation and trying to get the vendor to fix the scalability issue seems risky. I'd be worried about delays and additional costs.
OR
Oren 1 year ago
This seems like a tricky situation. I'd want to carefully review the original solution set to see if there's a better fit for the organization's needs and budget.
HE
Heike 1 year ago
Widget seems like the most logical choice, but I want to double-check the course materials just to be sure.
MI
Micheline 1 year ago
Hmm, I'm not totally sure about this one. I'll have to think it through carefully.
LA
Lashaunda 1 year ago
Option E: Throw a dart at the options and see what happens. After all, who needs scalability when you can have the thrill of uncertainty? Just remember, when in doubt, blame the vendor. They're always happy to take the heat, right?
GL
Glory 1 year ago
↳ replying to Lashaunda
D) Cancel the project if the business need was based on internal requirements versus regulatory compliance requirements
PA
Paulina 1 year ago
↳ replying to Lashaunda
C) Continue with the project until the scalability issue is validated by others, such as an auditor or third party assessor
TA
Tamekia 1 year ago
↳ replying to Lashaunda
B) Continue with the implementation and submit change requests to the vendor in order to ensure required functionality will be provided when needed
IL
Ilona 1 year ago
↳ replying to Lashaunda
A) Review the original solution set to determine if another system would fit the organization's risk appetite and budget regulatory compliance requirements
KA
Kati 1 year ago
Option C is the safest bet. Why not let someone else validate the scalability issue? That way, the CISO can avoid making a hasty decision and potentially wasting time and resources. Just don't forget to factor in the cost of the auditor or third-party assessor. 'Cause you know what they say, 'Penny wise, pound foolish.'
TO
Tonja 1 year ago
↳ replying to Kati
Nu: Agreed. Let's make sure we cover all our bases before moving forward with the implementation.
NU
Nu 1 year ago
↳ replying to Kati
User 2: Yeah, it's better to be safe than sorry. We don't want to waste resources on a solution that won't work for us.
NI
Nicholle 1 year ago
↳ replying to Kati
User 3: I agree. Let's bring in an auditor to validate the scalability before making any decisions.
JA
Janine 1 year ago
↳ replying to Kati
User 2: Janine is right. It's better to be safe than sorry. We don't want to waste resources on a solution that won't work.
NO
Norah 1 year ago
↳ replying to Kati
User 1: Option C sounds like a good idea. Let's get a third party to confirm the scalability issue.
AD
Adrianna 1 year ago
↳ replying to Kati
User 1: Option C sounds like a good idea. Let's get a third party to confirm the scalability issue.
ST
Staci 2 years ago
Option B is the way to go! Submitting change requests to the vendor is a great way to make the solution work. I'm sure they'll be happy to accommodate the organization's needs. What could go wrong, right? (Spoiler alert: a lot.)
DI
Dick 2 years ago
But what if the implementation is already underway? Shouldn't they continue with the project and make necessary changes?
CO
Cornell 2 years ago
I agree with Jackie. It's important to ensure the solution meets the organization's needs.
CL
Clay 2 years ago
I'd go with Option D. If the business need was just an internal requirement, then it's better to cancel the project than waste resources on a solution that won't scale. Gotta know when to cut your losses, you know?
TR
Trina 1 year ago
↳ replying to Clay
User 4: Definitely, cancelling the project if it doesn't meet our needs is the best course of action.
DE
Dean 1 year ago
↳ replying to Clay
User 3: I agree, let's not rush into implementation without considering all options.
MI
Mirta 1 year ago
↳ replying to Clay
User 2: Yeah, that makes sense. It's important to consider our risk appetite and budget.
MA
Madalyn 1 year ago
↳ replying to Clay
User 2: Definitely, it's important to reassess and make the best decision for the organization.
LI
Lina 1 year ago
↳ replying to Clay
User 1: I agree, cutting losses early is better than wasting resources.
LO
Lon 2 years ago
↳ replying to Clay
User 1: I think we should review the original solution set to find a better fit.
SI
Sina 2 years ago
Option A seems like the most prudent choice. The CISO should re-evaluate the original solutions to find one that aligns with the organization's requirements. Rushing into an implementation that doesn't fit the needs would be a costly mistake.
JA
Jackie 2 years ago
I think the CISO should review the original solution set to find a better fit.
0/2000 characters

Save Cancel