All posts by : chebby

Go  to the website: https://epic.org/privacy/litigation/ which focuses on civil rights issues and privacy. Pick a case.

Using WORD, in you OWN WORDS, write an ORIGINAL brief essay   :

• Summarize the case
• Give your opinion of the decision.
• Describe how the case deals with the material in this chapter

Turnitin®This assignment will be submitted to Turnitin®.Instructions

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.

Please read the below discussion posts and provide two responses in 50 to 75 words

Post#1

DNS Failover is designed to operate at the DNS level. That is, the level before a client connects to any of your servers. DNS essentially converts your domain name (e.g.www.example.com) into the IP address of your server. By monitoring applications and altering DNS dynamically so clients are pointed to different IP addresses, you can control traffic fairly easily and expensively. However, DNS failover does have two notable limitations: a) DNS Failover does not fix an outage when a client is already connected to an application. This is because their browser may not query DNS again for quite some time. b) DNS Failover has a TTL cache issue that could take anywhere from 1 to 30 minutes or more for the IP address change to be visible around the world. This is since many ISP’s recursive DNS servers cache longer than required to reduce traffic. “Time is an important component of the Domain Name System (DNS) and the DNS Security Extensions (DNSSEC). DNS caches rely on an absolute notion of time (e.g., “August 8, 2018 at 11:59pm”) to determine how long DNS records can be cached (i.e., their Time To Live (TTL)) and to determine the validity interval of DNSSEC signatures. This is especially interesting for two reasons” (Malhotra, 2019).

DNS Failover has been around for quite some time and is reliable. As a result, the sequential mode is the most popular for e-commerce applications or where back-end databases exist and some type of synchronization step is required before falling back to the primary. The cloud network monitors all of the available servers based on the monitoring criteria you specify via the management GUI and when it detects the primary down, it automatically fails over to the secondary IP (or if the secondary is down, fails over to the tertiary, etc.). In a typical static content scenario, when the primary comes back, it updates DNS again to send traffic to the primary. However, in an application where back-end databases must be synchronized, you can easily disable auto-failback to prevent the primary server from receiving traffic again. “A passive redundancy approach with diversification has been applied to intrusion-tolerant systems (ITSs) that aim to tolerate cyberattacks on a server” (Okamoto, 2017).

The monitoring system will still alert you that it is back online, but you have to manually force it to start receiving traffic again. This allows you to perform whatever tasks are required to ensure that the primary has the latest copy of the database or whatever is required. One critical drawback to using DNS failover in a situation where back-end synchronization is critical is when the primary is only down for a very short period. The short period would be sufficient to trigger a failover, but insufficient so that existing client connections (or new connections where the TTL cache has not expired) permit some clients to still hit the primary site. In this case, both the primary and secondary sites could receive traffic and create completely different databases that are very difficult to synchronize. “A DNS Load Balancer Daemon (LBD) has been developed at CERN as a cost-effective way to balance applications accepting DNS timing dynamics and not requiring persistence” (Reguero Naredo, 2017).

Post#2

            Cloud computing efficiency and security depends on several security concerns related to networks and connectivity. Protecting information system in cloud environment, from threats can be done largely by maintaining secure data traffic. The concepts of Domain Name System failover and Cloud failover come in this context of data traffic security. These two are most popular approaches in cloud security and share some similarities and dissimilarities between each other.

Comparison

            Functionality of DNS and cloud failover depends on the authentication of IP addresses largely. Both the preventive measures in cloud service security find out necessary action to recover from failures such as downtime recovery. Both the solutions need open access to public cloud in order to become active. The monitoring mechanism used in both the systems are almost equal and works in the same way for identification of servers and detection of faults (Naredo & Pardavila, 2017). DNS and Cloud failover are equally capable of delivering fast recovery as soon as within 60 seconds and can change functions automatically based on the requirement scenario.

The differences in cloud and DNS failover starts with the process through which these functions run. DNS finds easiest solution in re-routing of traffic in cases where a particular server fails, and it makes the traffic run through other active servers. A system embedded in the process helps in detecting the active server through a technique known as ‘round-robin’ method. A fault in DNS failover is that it contains the cached data which keeps revolving till one user’s Time to Live (TTL) in the server. “A DNS Load Balancer Daemon (LBD) has been developed at CERN as a cost-effective way to balance applications accepting DNS timing dynamics and not requiring persistence” (Naredo & Pardavila, 2017).

Cloud failover is popular for its accuracy and precision of carrying out the task necessary for sustained uptime. It does not send cached data back frequently. Sessions cared by cloud have better utilization capacities as it allows remote deployment unlike DNS failover where critical applications of a server are interrupted. To sustain through the TTLs, cloud failover uses session-wise load-balancing that proves to be more efficient than round-robin of DNS. Further, DNS failover fails to offer the flexibility due to the pre-determined conditioning that makes it a rigit system. Cloud, however, includes the DNS often for offering optimized result via a permanent proxy IP address. “DNS, being open-source, is less secure and it has no uncommon method for deciding if data has been intercepted while transmission or information of a domain name originates from an approved domain owner or not” (Ansari et. Al., 2020).

Conclusion

As a result of limitations, cloud failover service is costlier than DNS. There are steady improvements identifiable in DNS in global network. Some of the services are also allowing cache-free recovery of server. In spite of the advancements, it is yet to compete equally with cloud failover. On the other hand, cloud has its challenges too. “In spite of Cloud Computing services seem to be very attractive as an alternative to traditional on-premise data centers, there is still some concern about the providers availability” (Goncalves  & Fagotto, 2018).

 Please read “R3: Putting the ‘Fin’ Back into Fintech” case study (see HBS Coursepack) and answer the following questions with substantive answers in a cohesive essay. Your paper should be at least 3 pages in length. Use proper grammar, spelling, citations, etc.

1.How does Fintech compare to regular banking? 

2. Discuss R3 and its distributed ledger technology mission.

3. What are some of the applications of cords and strategies of growing and expanding?

4. What are some of the emerging markets that Fintech has impacted?

Compose your essay in APA format, including the introduction and conclusion, and in-text citations for all sources used. In addition to your 3 page (minimum) essay, you must include an APA-style title page and reference page. Click the assignment link to compare your work to the rubric before submitting it. Click the same link to submit your assignment.

3-5 video assignment

Select one type of cryptography or encryption and explain it in detail. Include the benefits as well as the limitations of this type of encryption. Your summary should be 2-3 paragraphs in length and uploaded as a TEXT DOCUMENT. Click the link above to submit your work. There is an EXAMPLE attached to show you the format requirements.

Projects

1. Choose an operating system and submit a report on approaches to manage its virtual memory.  
2. Working in teams of four, write pseudocode for the first-in first-out (FIFO) and least-recently-used (LRU) page replacement policies.

Additional Resources

1. Virtual Memory:  http://computer.howstuffworks.com/virtual-memory.htm
2. RAM, Virtual Memory, Pagefile and all that stuff: https://support.microsoft.com/en-us/kb/2160852 
3. Page replacement policy: http://www.slideshare.net/sashi799/page-replacement-5025792
4. The LRU page replacement policy: http://www.mathcs.emory.edu/~cheung/Courses/355/Syllabus/9-virtual-mem/LRU-replace.html

Due : September,16, 2020

1. Explain Angular core concepts (forms, guards, interceptors, routing, component communication, etc.) 

2. Walkthrough the approach implementing common UI components like forms, validations, rest API invocations using Angular framework. 

3. Share your experience with reactive programming (RxJS), observables, subjects, etc. 

4. Summarize your hands-on experience with Bootstrap / CSS experience 

5. Share your experience creating reusable modules/libraries using Angular 

6. Share your experience with advanced CSS concepts like flex layout, bootstrap themes, preprocessors like SCSS, Less etc.
 

7. As a Software Frontend Engineer, you will be a key player of the development team that has complete ownership from cradle to grave for the assigned application suite.  

· Hands-on development in Client-side technologies (JavaScript, TypeScript, Angular, HTML, CSS, Open Source Java, Spring Boot, MySQL) working in a test-driven development environment 

· Partner with the development team to map technical requirements into architecture and technical design tasks, plan releases and deliver on commitments 

· Participate in design and code reviews across the team to establish best practices 

· Inspire and mentor team members  

Project Description:

You have just graduated from college and before beginning your first professional job, you would like to purchase a new smartphone. You have the option to purchase the new phone in one payment or make monthly payments by taking advantage of a 36 month flex payment plan. The payment plan charges an APR of 1.75% for the service. Prior to making your payment decision, you would like to make a worksheet to calculate the monthly payment for consumer reports top three smartphones for young professionals.