You created a formal proposal and quote for a customer's data center network refresh. What is some other support information that you should include? (Select two)

Question

Options

• AA list of IP addresses that you plan to configure on the switches
• BNo need to include any of these as the proposal is not the place to educate the customer on them
• CHPE Aruba networking recommends including a block diagram with proposals
• DA list of VLANs that you plan to configure on the switches

• A
  3% (1)
• B
  3% (1)
• C
  93% (27)

Explanation

When preparing a formal network proposal, supporting visuals and configuration planning documents give the customer confidence and clarity about what they're getting - C and D are both correct because a block diagram (C) shows the logical/physical topology so stakeholders can visualize the solution, while a VLAN list (D) demonstrates that you've thought through network segmentation, which is critical for data center designs.

Why A is wrong: IP addresses are low-level operational details that belong in a post-sale implementation document, not a proposal - they can change and clutter a customer-facing document unnecessarily.

Why B is wrong: Supporting documentation absolutely belongs in a proposal; it builds credibility, reduces ambiguity, and helps the customer justify the purchase internally.

Memory tip: Think "picture + plan" - a proposal should always include a picture of the network (block diagram) and a plan for segmentation (VLANs). IP addresses and other granular config details come later during implementation.

No community discussion yet for this question.