I am little worry about whether it does hold enough detail.
For example, in Deployment diagram, because max 200 concurrent users at peak times, I only have 7 node with 2 hardware profiles as total. 1 web app ser and 1 standby, 1 db and 1 standby, 3 external system node...
Is it too "simple" to get enough pass point in Deployment diagram(Minimum Pass/ Points : 17/24) ?
I think it would be quite ridiculous if we had to add unnecessary hardware just to make the deployment diagram more complicated ;). I bet though it would be a good idea to add some explanation showing why do you believe such configuration is sufficient.
To provide you a bit more detail on the potential points of interest related to your deployment diagram.
Here is a list you could use while sketching your own diagram :
* Provide a decent guesstimate of hardware configuration and explain :
Resources: CPU, memory, network and disk
why I need such RAID here and another there and
why here is to be more memory than there.
* Resilience, fail-over, redundancy characteristics can also be planned and designed for.
* Upgrading Applications Without Loss of Availability
* Consider inter-tier security
* Consider using a firewall
* Describe network protocols used
* Describe network connectivity expected
* Define hardware profiles A, B and C in English text
* For database-centric applications (all!), describe appropriate RAID / storage configuration
* Consider virtualization
* Consider and provide other environments (QA, UAT, pre production)
* Continually review the SLAs for this section
Probably there are far more potential points of interest you can use if you use the search functionality of this forum
My point of view of the deployment diagram provided by the study guide is that they are oversimplified.
Whether they are sufficient to pass is already mentioned in a previous post.