New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Eccouncil 712-50 Exam - Topic 6 Question 91 Discussion

Actual exam question for Eccouncil's 712-50 exam
Question #: 91
Topic #: 6
[All 712-50 Questions]

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?

Show Suggested Answer Hide Answer
Suggested Answer: D

Contribute your Thoughts:

0/2000 characters
Gail
3 months ago
Wait, I can't believe the product isn't scalable! How did that happen?
upvoted 0 times
...
Cherry
3 months ago
D sounds extreme, but maybe necessary if it's not compliant.
upvoted 0 times
...
Winfred
3 months ago
C seems risky, why wait for validation?
upvoted 0 times
...
Kirk
4 months ago
I disagree, B could work if the vendor is reliable.
upvoted 0 times
...
Queen
4 months ago
A is definitely the way to go, better to reassess now.
upvoted 0 times
...
Yong
4 months 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?
upvoted 0 times
...
Chun
4 months 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.
upvoted 0 times
...
Torie
4 months 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.
upvoted 0 times
...
Joye
5 months 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.
upvoted 0 times
...
Lai
5 months 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.
upvoted 0 times
...
Curtis
5 months 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.
upvoted 0 times
...
Floyd
5 months 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.
upvoted 0 times
...
Oren
5 months 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.
upvoted 0 times
...
Heike
5 months ago
Widget seems like the most logical choice, but I want to double-check the course materials just to be sure.
upvoted 0 times
...
Micheline
5 months ago
Hmm, I'm not totally sure about this one. I'll have to think it through carefully.
upvoted 0 times
...
Lashaunda
9 months 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?
upvoted 0 times
Glory
8 months ago
D) Cancel the project if the business need was based on internal requirements versus regulatory compliance requirements
upvoted 0 times
...
Paulina
8 months ago
C) Continue with the project until the scalability issue is validated by others, such as an auditor or third party assessor
upvoted 0 times
...
Tamekia
9 months ago
B) Continue with the implementation and submit change requests to the vendor in order to ensure required functionality will be provided when needed
upvoted 0 times
...
Ilona
9 months ago
A) Review the original solution set to determine if another system would fit the organization's risk appetite and budget regulatory compliance requirements
upvoted 0 times
...
...
Kati
10 months 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.'
upvoted 0 times
Tonja
9 months ago
Nu: Agreed. Let's make sure we cover all our bases before moving forward with the implementation.
upvoted 0 times
...
Nu
9 months ago
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.
upvoted 0 times
...
Nicholle
9 months ago
User 3: I agree. Let's bring in an auditor to validate the scalability before making any decisions.
upvoted 0 times
...
Janine
9 months ago
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.
upvoted 0 times
...
Norah
9 months ago
User 1: Option C sounds like a good idea. Let's get a third party to confirm the scalability issue.
upvoted 0 times
...
Adrianna
9 months ago
User 1: Option C sounds like a good idea. Let's get a third party to confirm the scalability issue.
upvoted 0 times
...
...
Staci
10 months 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.)
upvoted 0 times
...
Dick
10 months ago
But what if the implementation is already underway? Shouldn't they continue with the project and make necessary changes?
upvoted 0 times
...
Cornell
10 months ago
I agree with Jackie. It's important to ensure the solution meets the organization's needs.
upvoted 0 times
...
Clay
11 months 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?
upvoted 0 times
Trina
9 months ago
User 4: Definitely, cancelling the project if it doesn't meet our needs is the best course of action.
upvoted 0 times
...
Dean
9 months ago
User 3: I agree, let's not rush into implementation without considering all options.
upvoted 0 times
...
Mirta
9 months ago
User 2: Yeah, that makes sense. It's important to consider our risk appetite and budget.
upvoted 0 times
...
Madalyn
10 months ago
User 2: Definitely, it's important to reassess and make the best decision for the organization.
upvoted 0 times
...
Lina
10 months ago
User 1: I agree, cutting losses early is better than wasting resources.
upvoted 0 times
...
Lon
10 months ago
User 1: I think we should review the original solution set to find a better fit.
upvoted 0 times
...
...
Sina
11 months 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.
upvoted 0 times
...
Jackie
11 months ago
I think the CISO should review the original solution set to find a better fit.
upvoted 0 times
...

Save Cancel