PCF Exam Dumps
PCF Architecture & Components
-
Q. Which component in the Diego Brain Maintains
DesiredLRP
?-
Rep Cell
-
Nsync
-
Auctioneer
-
BBS
-
-
Q. _ Streams STDOUT and STDERR to the Metron agent running on the Cell?
-
Executor
-
Doppler
-
Firehose
-
Nozzle
-
-
Q. Metron Agent will forward _ to the Doppler component
-
Logs
-
Errors
-
Application & Diego Metrics
-
All above
-
-
Q. Which Component respond to
cf apps
command?-
CloudController
-
TrafficController
-
GoRouter
-
TPS Watcher
-
-
Q. Who will Monitors
ActualLRP
activity for crashes and reports them the Cloud Controller-
Rep Cell
-
TrafficController
-
GoRouter
-
TPS Watcher
-
-
Q. _ Sends a response to the Cloud Controller when a Task completes
-
Stager
-
TrafficController
-
GoRouter
-
Loggregator
-
-
Q. Monitors DesiredLRP and ActualLRP states, emitting route registration and unregistration messages to the Cloud Foundry Gorouter when it detects changes
-
Route-Emitter
-
TrafficController
-
GoRouter
-
Loggregator
-
-
Q. Which Component respond to
cf logs
command?-
CloudController
-
TrafficController
-
GoRouter
-
Loggregator
-
-
Q. Which component responsible for monitoring, failure recovery, and software updates with zero-to-minimal downtime.
-
Loggregator
-
Diego
-
BOSH
-
CloudController
-
-
Q. Which component responsible for deployment, and lifecycle management of small and large-scale cloud software.
-
BOSH
-
Loggregator
-
Diego
-
CloudController
-
-
Q. Which of the following Iaas provides that BOSH Supports
-
VMWare vSphere
-
Google Cloud Platform
-
Amazon Web Services EC2
-
OpenStack
-
-
Q. __ Enables users to extend BOSH to support additional IaaS providers such as Apache CloudStack and VirtualBox
-
BOSH Interface
-
Cloud Provider Interface
-
IaaS Interface
-
Cloud Connector Interface
-
-
Q. Which component in the Diego Brain Maintains
ActualLRP
?-
Rep Cell
-
Nsync
-
Auctioneer
-
BBS
-
Metrics
-
Q. PCF can gathers metrics from the following components (Select all that apply)
-
Garden
-
Cell
-
Container
-
Network
-
-
Q. Which of the following statements true
-
Container metrics
: CPU, memory, and disk percentages (updated every 30 seconds) -
Network metrics
: requests per second, HTTP errors per second, and request latency (updated every second) -
App events
: create, update, start, stop, and crash (updated as they happen)
-
Blue-Green Deployment
-
Q.Blue Green deployment is a technique that reduces downtime and risk by doing following practice
-
It runs One Production and One Staging Application at a time
-
It runs two productions environments at a time
-
It Runs Two Production Environment called Blue and One staging Environment called Green
-
One Active Environment called Blue and other Idle environment called Green
-
-
Q. It is recommended to use One Relation database for Both Blue& Green Applications
-
TRUE
-
FALSE
-
-
Q. My REST APIs (v1.0-Blue) were deployed at
api.tvajjala.in
. How do you send traffic to new app deployed as Green(v1.1 API)-
cf map-route Green tvajjala.in -n api
-
cf route-traffic Green tvajjala.in -n api
-
cf map-route Green -n green.temp
-
cf route-traffic Green -n green.temp
-
Application Security Groups
-
Q. Types of ASG
-
Platform-wide staging ASG set, also called “default-staging”
-
Platform-wide running ASG set, also called “default-running”
-
Space-scoped staging ASG set
-
Space-scoped running ASG set
-
-
Q. Application Security Groups applied for _ Traffic
-
Ingress (Inbound)
-
Egress (Outbound)
-
Both
-
None
-
-
Q. ASG Applied for _
-
Buildpack based applications
-
Docker Based Applications.
-
Tasks
-
All of the above
-
-
Q. ASG Can be defines for _
-
Staging
andRunning
Applications -
Platform wide Applications
-
Space-Scoped Applications
-
All of the above
-
-
Q. ASG are executed in the following order
-
In the same order they defined
-
In the Ascending order of rule Ids like, 100, 101
-
Order is not important for ASGs
-
Only most recent ASG gets executed as high priority
-
Domains and Routers
-
Q. If your application deployed using TCP Router, which port the application should run in the container
-
8080
-
443
-
80
-
22
-
-
Q. How do you create a HTTP route in the
dev
space for with domain nametvajjala.io
(choose multiple)-
cf create-route dev tvajjala.io -n demo-time
-
cf create-route dev tvajjala.io
-
cf create-route dev tvajjala.io -n demo-time --path home
-
cf create-route dev demo-time.tvajjala.io/home
-
-
Q. How do you create TCP Route in the
dev
space-
cf create-route dev tvajjala.io --port 60010
-
cf create-route dev tvajjala.io --random-route
-
all of the above
-
-
Q. Which of the following statements are true w.r.t domains
-
There two types of domains available PCF called
HTTP
domains andTCP
domains -
HTTP
domains indicate to a developer that only requests using the HTTP protocol will be routed to applications mapped to routes created from the domain. -
Routing for HTTP domains is layer 7 and offers features like custom hostnames, sticky sessions, and TLS termination.
-
TCP domains indicate to a developer that requests over any TCP protocol, including HTTP, will be routed to applications mapped to routes created from the domain.
-
-
Q. Which of the following statements true for TCP Domains
-
TCP domains indicate to a developer that requests over any TCP protocol, including HTTP.
-
Routing for TCP domains is layer 4 and protocol agnostic
-
Features available to HTTP routing are not available for TCP routing.
-
All of the above
-
-
Q. Which of the following statement is true for
TCP Router Group
-
TCP domains are defined as being associated with the TCP Router Group.
-
The TCP Router Group defines the range of ports available to be reserved with TCP Routes.
-
Note
|
Currently, only Shared Domains can be TCP. |
Tip
|
By default, Cloud Foundry only supports routing of HTTP requests to applications. |
-
Q. How do you create domain
-
cf create-domain MYORG tvajjala.io
-
cf create-domain tvajjala.io MYORG MYSPACE
-
`cf create-domain tvajjala.io MYORG `
-
-
Q. Which of following statements are true for shared-domains
-
Admin managed shared domains
-
Developer can also managed shared domains
-
Shared domains available to users in all ORGs of a Cloud Foundry
-
Shared domains are HTTP domains by default, but can be configured to be TCP when associated with the TCP Router Group.
-
-
Q. A developer pushed application to CF without domain name, which of the statements true
-
Route will be created for it from the first shared domain created in the system
-
There are not technically a default domains in the system
-
App will through error if
host
name is already used by other org
-
-
Q. Which of the following command used to create shared-domain ….
cf create-shared-domain DOMAIN
is HTTP shared domain ….`cf create-shared-domain DOMAIN [--router-group ROUTER_GROUP]`is TCP shared domain-
A & C are correct
-
-
Q. Which of the following statement are true
-
Routes are bound to
SPACE
-
Domains are bound to
ORG
-
Shared domains are bound to across PCF deployment
-
A , B, C are correct
-
-
Q. Which of the statements TRUE for PRIVATE domains
-
Private domains can be created by
ORG MANAGERS
-
Private domains can be HTTP or HTTPS only.
-
TCP Routing is supported for Shared Domains only
-
Private domains can be shared with other ORGs, enabling users of those ORGs to create routes from the domain.
-
-
Q. How do you create private domain
-
cf create-domain MYORG myprivate.domain.com
-
cf create-private-domain MYORG myprivate.domain.com
-
-
Q. How do you share/un-share private domains*
-
$ cf share-private-domain test-org private-domain.example.com
-
$ cf unshare-private-domain test-org private-domain.example.com
-
Note
|
there only two ways you create domain create-domain / create-shared-domain .
When you create domain with create-domain this is by default private to your ORG . and you can shared with other ORGS
with share-private-domain
|
-
Q. How do you check the route exists for the domain, before you create
-
cf check-route demo cfapps.io
-
cf check-route demo cfapps.io --path home
-
there is no way to check
-
Manifest
-
If your manifest.yml declares route element in it , which of the following arguments not allowed from command-line
-
-d
-
--hostname
-
-n
-
--no-hostname
-
--route-path
-
All of the above arguments not allowed
-
-
Which of following attributes are NOT deprecated in the manifest.yml
-
domain
-
domains
-
host
-
hosts
-
no-hostname
-
route
-
Container-to-Container Routing
-
Cloud Foundry container networking is currently supported only on Linux
-
TRUE
-
FALSE
-
-
Traffic to app containers from Go-Router or from app containers to external services uses cell IP addresses and NAT, not the overlay network.
-
TRUE
-
FALSE
-
-
The overlay network IP address range must not conflict with any other IP addresses in the network If a conflict exists, Diego cells cannot reach any endpoint that has a conflicting IP address.
-
TRUE
-
-
What is the default overlay network range
-
10.255.0.0/16
-
-
How many container that each Diego Cell can support
-
By default, each cell is allocated a /24 CIDR range that supports 254 containers per cell
-
-
Container-to-Container Networking supports UDP and TCP, and you can configure policies for multiple ports
-
TRUE
-
-
What is the difference between Application Security Group(ASG) and Container-to-Container network policies
- | ASG | C2C |
---|---|---|
Policy Granularity |
From SPACE to CIDR address range |
App to App |
Scope |
Can apply at Space, Org, Deployment level |
App to App |
Traffic Direction |
egress traffic |
App to App only |
Policy effective time |
After App restart |
Immediately |
-
What is
Upgrade
header will do-
To form a WebSocket connection, the client sends an HTTP request that contains an Upgrade header and other headers required to complete the WebSocket handshake.
-
You must configure your load Balancer to not upgrade the HTTP request, but rather to pass the Upgrade header through to the CF router.
Comments
Post a Comment