That's the problem with most questions asked here...lack of context.
A person is certainly free to ask a specific question and get a specific
answer.
BUT
You can often judge the experience (I was gonna say competence. That's the
right word, but would ignite the ethernet and we don't want that.) of
the person asking the question by the form and words used.
When the big red flags go up, it can be helpful to the person to
elaborate...whether they like it or not. The side effect is that we
turn on each other, but that's just the way of the web.
In my opinion, there is NO pulse width that allows 40W of peak power
in a 1/2W device to be considered an acceptable design...none.
And it's difficult to filter the current pulses. You start adding
caps and discover that something else blows up when you crowbar the
100V supply. Are we comforted by the fact that most designers wouldn't
consider that a problem?
Without context, we're left with only common sense to guide us.
Ignoring the 10V discrepancy in the question, someone stated that
the zener could sustain 17mA if you didn't derate it. For many single
chip switchers, the duty factor is closely related to the ratio of input
and output voltages. Narrow 1A spikes seem out of place.
I would prefer a design that didn't have 'em.
Yes, it's possible for a system integrator to be in a situation where they
have to mate two bad designs. That's why you need your BEST engineers
doing the integration.
One of the jobs of a project manager is to stamp out tunnel vision.
Everybody needs to be aware of the big picture...not an expert, but aware.
Communication is key.
I used to tell engineers at the first project meeting that I was gonna
personally test the design before the second prototype phase.
The list of abuses would contain
Crowbar the power supplies.
Any connector that could be put on the wrong socket or backwards or
off-by-one on the right socket would be tried and the power turned on.
Bunch of other single-point failures that could happen in manufacturing.
You could have heard the whimpering and wailing in the next county.
Probably increased the cost a few pennies too. But the concept propagated
to other parts of the design so engineers considered more than just what
happened when everything was working right.
Yes, you can easily come up with single-point failures that can't be
protected against
and will reduce the project to a smoldering lump.
The key point is that MANY, MOST can be mitigated by paying attention.
Enough rant...
Back to the current situation.
More context would be helpful.
If we were voting based on what's been divulged, I'd bet that this is
a disaster waiting to happen. I refuse to be comforted by the fact
that most designs are faulty in ways that could have been easily
avoided by paying attention. Excuses are cheap. Field failures aren't.