JencoMart is a global retailer with over 10,000 stores in 16 countries.
The stores carry a range of goods, such as groceries, tires, and jewelry.
One of the company's core values is excellent customer service.
In addition, they recently introduced an environmental policy to reduce their carbon output by 50% over the next 5 years.
Company Background - JencoMart started as a general store in 1931, and has grown into one of the world's leading brands, known for great value and customer service.
Over time, the company transitioned from only physical stores to a stores and online hybrid model, with 25% of sales online.
Currently, JencoMart has little presence in Asia, but considers that market key for future growth.
Solution Concept - JencoMart wants to migrate several critical applications to the cloud but has not completed a technical review to determine their suitability for the cloud and the engineering required for migration.
They currently host all of these applications on infrastructure that is at its end of life and is no longer supported.
Existing Technical Environment - JencoMart hosts all of its applications in 4 data centers: 3 in North American and 1 in Europe; most applications are dual-homed.
JencoMart understands the dependencies and resource usage metrics of their on-premises architecture.
Application: Customer loyalty portal LAMP (Linux, Apache, MySQL and PHP) application served from the two JencoMart-owned U.S.
data centers.
Database -Oracle Database stores user profiles - 20 TB - Complex table structure - Well maintained, clean data - Strong backup strategyPostgreSQL database stores user credentials - Single-homed in US West - No redundancy - Backed up every 12 hours - 100% uptime service level agreement (SLA) - Authenticates all users Compute -30 machines in US West Coast, each machine has: - Twin, dual core CPUs - 32 GB of RAM - Twin 250 GB HDD (RAID 1)20 machines in US East Coast, each machine has: - Single, dual-core CPU - 24 GB of RAM - Twin 250 GB HDD (RAID 1) Storage -Access to shared 100 TB SAN in each locationTape backup every week Business Requirements -Optimize for capacity during peak periods and value during off-peak periodsGuarantee service availability and supportReduce on-premises footprint and associated financial and environmental impactMove to outsourcing model to avoid large upfront costs associated with infrastructure purchaseExpand services into Asia Technical Requirements -Assess key application for cloud suitabilityModify applications for the cloudMove applications to a new infrastructureLeverage managed services wherever feasibleSunset 20% of capacity in existing data centersDecrease latency in Asia CEO Statement - JencoMart will continue to develop personal relationships with our customers as more people access the web.
The future of our retail business is in the global market and the connection between online and in-store experiences.
As a large, global company, we also have a responsibility to the environment through green initiatives and policies.
CTO Statement - The challenges of operating data centers prevent focus on key technologies critical to our long-term success.
Migrating our data services to a public cloud infrastructure will allow us to focus on big data and machine learning to improve our service to customers.
CFO Statement - What three steps should you take to diagnose the problem? (Choose three.)
Click on the arrows to vote for the correct answer
A. B. C. D. E. F.CDF.
D: Handling "Unable to connect on port 22" error message Possible causes include: -> There is no firewall rule allowing SSH access on the port.
SSH access on port 22 is enabled on all Compute Engine instances by default.
If you have disabled access, SSH from the Browser will not work.
If you run sshd on a port other than 22, you need to enable the access to that port with a custom firewall rule.
-> The firewall rule allowing SSH access is enabled, but is not configured to allow connections from GCP Console services.
Source IP addresses for browser- based SSH sessions are dynamically allocated by GCP Console and can vary from session to session.
F: Handling "Could not connect, retrying..." error You can verify that the daemon is running by navigating to the serial console output page and looking for output lines prefixed with the accounts-from-metadata: string.
If you are using a standard image but you do not see these output prefixes in the serial console output, the daemon might be stopped.
Reboot the instance to restart the daemon.
https://cloud.google.com/compute/docs/ssh-in-browser https://cloud.google.com/compute/docs/ssh-in-browserI apologize, but the question you provided seems to be unrelated to the company background, technical environment, and business and technical requirements provided in the previous text. Could you please provide me with the correct question? I will be happy to provide a detailed explanation.