This week, you will complete your proof of concept and submit the report. This is the final report to management before the actual cloud deployment process begins.
Use the Proof-of-Concept Report Template to prepare a report that shows the steps and results for the proof of concept. In the template, you will see specific instructions. Delete the instruction text before you submit the project.
Your report should:
Be between five to seven pages (plus an appendix for screenshots, cover page, and table of contents)
Address the topics listed in the Proof-of-Concept Report Template
Include the following screenshots from the “Build a Virtual Private Cloud and Launch a Web Server” activity:
Start Lab page
AWS Management Console Name with your name visible from user drop-down
Task 1: Create Your VPC
Task 2: Create Additional Subnets
Task 3: Create a VPC Security Group
Task 4: Launch a Web Server Instance
How Will My Work Be Evaluated?
As a cloud professional tasked with developing a proof of concept for the companies cloud adoption, you will prepare a proof of concept report to be submitted to the company owner. By developing a well-structured report of your results and recommendations to management, you are demonstrating how you use your technical knowledge to convey your ideas to others in a professional setting. Your ability to express recommendations to decision makers with the right mix of technical detail in an accepted format is an important workplace and career skill.
The following evaluation criteria aligned to the competencies will be used to grade your assignment:
1.1.3: Present ideas in a clear, logical order appropriate to the task.
1.1.4: Explain the relationship between the ideas presented to enhance clarity and comprehension.
2.1.1: Identify the issue or problem under consideration.
2.1.2: Describe the context surrounding the issue or problem.
2.2.3: Explain the assumptions underlying viewpoints, solutions, or conclusions.
2.3.4: Address alternative viewpoints, perspectives, and methods.
11.1.3: Install software.
11.2.1: Configure technology according to stakeholder specifications and requirements.
13.1.1: Create documentation appropriate to the stakeholder.
When you are finished, click add a file to upload your work, then click the Submit button.
Hide Rubrics
Rubric Name: Project 3: Proof of Concept Report
This table lists criteria and criteria group names in the first column. The first row lists level names and includes scores if the rubric uses a numeric scoring method. You can give feedback on each criterion by tabbing to the add feedback buttons in the table.
Criteria
Exceeds Performance Requirements
Meets Performance Requirements
Approaches Performance Requirements
Does Not Meet Performance Requirements
Criterion Score
1.1.3: Present ideas in a clear, logical order appropriate to the task.
5 points
Presents a logical flow of ideas that is easily identifiable and completely appropriate to the task.
4.25 points
Presents ideas in a clear, logical order appropriate to the task.
3.75 points
Attempts to present ideas, but the logic is not clear and/or not appropriate to the task.
0 points
Does not present ideas in a clear, logical order appropriate to the task.
Score of 1.1.3: Present ideas in a clear, logical order appropriate to the task.,/ 5
1.1.4: Explain the relationship between the ideas presented to enhance clarity and comprehension.
7 points
Explains the relationship between the ideas presented in a thorough manner to enhance clarity and comprehension.
5.95 points
Explains the relationship between the ideas presented to enhance clarity and comprehension.
5.25 points
Attempts to explain the relationship between the ideas presented, but there may be gaps in clarity and comprehension.
0 points
Does not explains the relationship between the ideas presented to enhance clarity and comprehension.
Score of 1.1.4: Explain the relationship between the ideas presented to enhance clarity and comprehension.,/ 7
2.1.1: Identify the issue or problem under consideration.
7 points
Identifies the issue or problem under consideration in a clear and thorough manner.
5.95 points
Identifies the issue or problem under consideration.
5.25 points
Attempts to Identify the issue or problem under consideration, but there is a lack of clarity or thoroughness.
0 points
Does not identify the issue or problem under consideration.
Score of 2.1.1: Identify the issue or problem under consideration.,/ 7
2.1.2: Describe the context surrounding the issue or problem.
7 points
Describes the context surrounding the issue or problem clearly and accurately.
5.95 points
Describes the context surrounding the issue or problem.
5.25 points
Attempts to describe the context surrounding the issue or problem.
0 points
Does not describe the context surrounding the issue or problem.
Score of 2.1.2: Describe the context surrounding the issue or problem.,/ 7
2.2.3: Explain the assumptions underlying viewpoints, solutions, or conclusions.
7 points
Explains the assumptions underlying viewpoints, solutions, or conclusions in a comprehensive and accurate manner.
5.95 points
Explains the assumptions underlying viewpoints, solutions or conclusions.
5.25 points
Attempts to explain the assumptions underlying viewpoints, solutions or conclusions, but the explanation lacks clarity.
0 points
Does not explain the assumptions underlying viewpoints, solutions, or conclusions.
Score of 2.2.3: Explain the assumptions underlying viewpoints, solutions, or conclusions.,/ 7
2.3.4: Address alternative viewpoints, perspectives, and methods.
7 points
Addresses alternative viewpoints, perspectives, and methods accurately and appropriately.
5.95 points
Addresses alternative viewpoints, perspectives, and methods.
5.25 points
Attempts to address alternative viewpoints, perspectives, and methods, but there are issues with the accuracy and/or appropriateness.
0 points
Does not address alternative viewpoints, perspectives, and methods.
Score of 2.3.4: Address alternative viewpoints, perspectives, and methods.,/ 7
11.1.3: Install software.
20 points
Installs software that is fully functional and appropriate for the given requirements.
17 points
Installs software that is appropriate for the given requirements.
15 points
Installs software that may not be fully functional and/or appropriate for the given requirements.
0 points
Does not install software.
Score of 11.1.3: Install software.,/ 20
11.2.1: Configure technology according to stakeholder specifications and requirements.
20 points
Configures technology accurately and thoroughly to meet stakeholder specifications and requirements.
17 points
Configures technology that meets stakeholder specifications and requirements.
15 points
Attempts to configure technology according to stakeholder specifications and requirements.
0 points
Does not configure technology that meets stakeholder specifications and requirements.
Score of 11.2.1: Configure technology according to stakeholder specifications and requirements.,/ 20
13.1.1: Create documentation appropriate to the stakeholder.
20 points
Creates thorough and accurate IT documentation that exceeds requirements.
17 points
Creates IT documentation that meets requirements.
15 points
Creates IT documentation that lacks detail and/or does not fully meet requirements.
0 points
Does not create appropriate IT documentation.
Score of 13.1.1: Create documentation appropriate to the stakeholder.,/ 20
Rubric Total Score
Total
