F5CTSLTM2-B
BIG-IP LTM Specialist Virtual Server and Local Traffic Configuration Objects
Parte de F5 Certified Technology Specialist, BIG-IP LTM
Material de estudo independente, construído a partir do blueprint público da prova. Sem afiliação, autorização ou endosso da F5. Os objetivos são transcritos e mapeados à mão, então esta página pode conter erros ou estar defasada em relação ao material atual do fabricante: objetivos, versões, numeração e disponibilidade mudam sem aviso. Trate o portal de certificação da própria F5 como a fonte da verdade e confira nele antes de agendar qualquer coisa.
Exam F5CTSLTM2-B: BIG-IP LTM Specialist Virtual Server and Local Traffic Configuration Objects
F5CTSLTM2.01 Determine which configuration objects are necessary to deploy an application
O que saber:- Determine least amount of configuration objects needed to deploy application
- Understand dependencies of configuration objects
- Understand needed LTM profiles to deploy an application
- Identify unnecessary configurations objects
- Understand the differences between virtual servers and virtual addresses
F5CTSLTM2.02 Choose correct profiles and settings to fit application requirements
O que saber:- Identify LTM profile settings to deploy OneConnect
- Determine which profiles are needed to deploy an application
- Compare and contrast different communication protocols (TCP, UDP, FastL4)
- Compare performance impact of LTM profile settings
F5CTSLTM2.03 Choose virtual server type and load balancing type to fit application requirements
O que saber:- Determine the difference between L2-L3 virtual servers
- Compare and contrast standard and fastL4 virtual server types
- Compare and contrast different load balancing methods
- Identify different load balancing method use cases
Neste site: Tipos de virtual server do BIG-IP, e o que cada um realmente faz, Métodos de balanceamento do BIG-IP, e o que cada um ponderaFerramentas: bigip-ltm-lb-simulatorF5CTSLTM2.04 Determine how to architect and deploy multi-tier applications using LTM
O que saber:- Understand connection-based architecture and when/how to apply SNAT/persistence/SSL settings in a multi-tiered environment
- Identify which device handles specific configuration objects in a multi-tiered deployment
F5CTSLTM2.05 Distinguish between packet-based versus connection-based load balancing
O que saber:- Demonstrate when to use packet-based load balancing
- Demonstrate when to use connection-based load balancing
F5CTSLTM2.06 Determine which configuration objects are necessary for applications that need the original client IP address
O que saber:- Determine when SNAT is required
- Determine the required SNAT type
- Identify functions of X-forwarded-for
- Outline the steps needed to return the traffic to LTM without SNAT
Neste site: SNAT e o problema do tráfego de retornoF5CTSLTM2.07 Identify the matching order of multiple virtual servers
O que saber:- Identify which virtual server would process particular traffic
- Identify why the virtual server fails to receive traffic
F5CTSLTM2.08 Determine how to secure virtual servers
O que saber:- Determine how to limit access to virtual servers
- Compare and contrast different virtual server types
- Identify LTM profiles setting to limit access to virtual server resources
F5CTSLTM2.09 Determine how configuration changes affect existing and new connections
O que saber:- Predict persistence for existing connections
- Calculate when changes will affect the connections
- Predict load balancing and persistence for new connections
- Determine the impact of virtual server configuration change on traffic
F5CTSLTM2.10 Given a scenario, determine the appropriate profile setting modifications
O que saber:- Given a scenario determine when an application would benefit from HTTP Compression and/or Web Acceleration profile depending on HTTP version
- Given a scenario of client or server-side buffer issues, packet loss, or congestion, select the appropriate TCP or UDP profile to correct the issue
F5CTSLTM2.11 Given a sub-set of an LTM configuration, determine which objects to remove or consolidate to simplify the LTM configuration
O que saber:- Evaluate which iRules can be replaced with a profile or policy setting
- Evaluate which host virtual servers would be better consolidated into a network virtual server or traffic
F5CTSLTM2.12 Given a set of LTM device statistics, determine which objects to remove or consolidate to simplify the LTM configuration
O que saber:- Identify redundant and/or unused objects
- Identify unnecessary monitoring
- Interpret configuration and performance statistics
- Describe the outcome of removing functions from the LTM device configuration
Ferramentas: f5-tmsh-config-explainerF5CTSLTM2.13 Given a packet capture, identify monitor issues
O que saber:- Explain how to capture and interpret monitor traffic using protocol analyzer
- Explain how to obtain needed input and output data to create the monitors
Neste site: Como os Monitores de Saúde do LTM Decidem Ativo ou Inativo, tcpdump no BIG-IP: como ele difere do tcpdump padrãoFerramentas: f5-bigip-tcpdump-builderF5CTSLTM2.14 Given a monitor issue, determine an appropriate solution
O que saber:- Determine appropriate monitor and monitor timing based on application and server limitations
- Describe how to modify monitor settings to resolve monitor problems
- Describe when In-TMM monitoring should be applied
Fontes públicas, usadas de boa-fé
Estes guias são materiais de estudo independentes, montados a partir de conteúdo publicamente disponível: blueprints de exame publicados, documentação oficial de produto e catálogos de treinamento dos fabricantes. Nomes de produtos, códigos de exame e marcas pertencem a seus titulares e são usados apenas para identificar o assunto ensinado. Este site não é afiliado a nenhum fabricante aqui citado nem endossado por ele. Se você detém direitos sobre material publicado nesta página e entende que ele deve ser removido ou corrigido, envie a URL exata e uma breve nota sobre o problema pela página de contato; os pedidos são analisados com rapidez e boa-fé. Ler o aviso legal completo →